From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: Daniel Phillips <phillips@bonn-fries.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [patch] nonblinking VGA block cursor
Date: Fri, 15 Jun 2001 21:43:31 MET-1 [thread overview]
Message-ID: <5E9F5DB4FCA@vcnet.vc.cvut.cz> (raw)
On 15 Jun 01 at 21:34, Daniel Phillips wrote:
> 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? ;-)
Because of you can move mouse cursor - moving mouse usually does not
have serious side effect. Normal cursor cannot be moved without
sideeffects, so you cannot find it so easy.
If you want, just plug matrox into your laptop and use matroxfb. It
restarts cursor blinking cycle on each character printed to screen,
so while you are typing, you still see cursor, but if you stop typing,
cursor starts blinking...
Just my 0.02Kc.
Best regards,
Petr Vandrovec
vandrove@vc.cvut.cz
[matroxfb has also noblink option because HPA wanted it. But it is
another story]
next reply other threads:[~2001-06-15 19:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-15 21:43 Petr Vandrovec [this message]
-- strict thread matches above, loose matches on Subject: below --
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
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
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=5E9F5DB4FCA@vcnet.vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=linux-kernel@vger.kernel.org \
--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).