linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Albert D. Cahalan" <acahalan@cs.uml.edu>
To: 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: Fri, 15 Jun 2001 15:38:18 -0400 (EDT)	[thread overview]
Message-ID: <200106151938.f5FJcIJ288693@saturn.cs.uml.edu> (raw)
In-Reply-To: <0106152134050C.00879@starship> from "Daniel Phillips" at Jun 15, 2001 09:34:05 PM

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

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.

  reply	other threads:[~2001-06-15 19:38 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 [this message]
2001-06-15 23:44       ` Daniel Phillips
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
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=200106151938.f5FJcIJ288693@saturn.cs.uml.edu \
    --to=acahalan@cs.uml.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ljb@devco.net \
    --cc=phillips@bonn-fries.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;
as well as URLs for NNTP newsgroup(s).