From: Daniel Phillips <phillips@bonn-fries.net>
To: "Albert D. Cahalan" <acahalan@cs.uml.edu>,
phillips@bonn-fries.net (Daniel Phillips)
Cc: acahalan@cs.uml.edu (Albert D. Cahalan),
ljb@devco.net (Leon Breedt),
linux-kernel@vger.kernel.org
Subject: Re: [patch] nonblinking VGA block cursor
Date: Sat, 16 Jun 2001 01:44:40 +0200 [thread overview]
Message-ID: <0106160144400D.00879@starship> (raw)
In-Reply-To: <200106151938.f5FJcIJ288693@saturn.cs.uml.edu>
In-Reply-To: <200106151938.f5FJcIJ288693@saturn.cs.uml.edu>
On Friday 15 June 2001 21:38, Albert D. Cahalan wrote:
> Daniel Phillips writes:
> > On Friday 15 June 2001 21:21, Albert D. Cahalan wrote:
> >> Non-blinking cursors are just wrong. You need to patch your brain.
> >> You really fucked up, because now apps can't restore your cursor
> >> to proper behavior as defined by IBM.
> >
> > Just one question Albert: why doesn't my mouse cursor blink? ;-)
>
> 1. confusion with the text cursor, which should blink
> 2. need for continuous pixel-to-pixel accuracy with the mouse
> 3. you can wiggle your mouse as needed to find the mouse cursor
4. It would be bloody annoying.
Some people find the blinking text cursor equally annoying, you appear to be
trying to dictate what their options should be.
> Apps do funny things when you try to wiggle the text cursor
> with the arrow keys, and movement tends to be harshly constrained.
> So the blinking is important.
Ask the original poster if he's willing to take the risk of going with an xor
cursor. We are talking text mode, right? No way to get rid of that blinking
text cursor, ever. Tell me, do you like having the colon blink on your alarm
clock too? Personally, I opened the thing up and put a piece of tape over it.
As I recall, one of the popular projects when the IBM PC first came out was
trying to get the cursor to stop blinking. No luck, IBM had hardwired in a
special trace to make sure you couldn't. You could or two blink patterns
together, but never get it to stop. Since we are now in a position to
dictate, why don't we continue that grand tradition.
IBM had lots of ideas about how computers should work. Remember the keyboard
keys that when CLACK CLACK CLACK. Thank god they turned out to be too
expensive to clone - nobody misses them now.
When people ask for such options it's not because they want to make *your*
cursor stop blinking, it's because they want *theirs* to stop.
--
Daniel
next prev parent reply other threads:[~2001-06-15 23:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-15 14:22 [patch] nonblinking VGA block cursor Leon Breedt
2001-06-15 19:21 ` Albert D. Cahalan
2001-06-15 19:34 ` Daniel Phillips
2001-06-15 19:38 ` Albert D. Cahalan
2001-06-15 23:44 ` Daniel Phillips [this message]
2001-06-16 0:03 ` Josh Myer
2001-06-16 0:14 ` Daniel Phillips
2001-06-16 7:22 ` Erik Mouw
2001-06-15 20:22 ` Leon Breedt
2001-06-16 3:52 ` Mike Galbraith
2001-06-16 4:17 ` John R Lenton
2001-06-17 16:34 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2001-06-15 21:43 Petr Vandrovec
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0106160144400D.00879@starship \
--to=phillips@bonn-fries.net \
--cc=acahalan@cs.uml.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=ljb@devco.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox