From: Josh Myer <jbm@joshisanerd.com>
To: Daniel Phillips <phillips@bonn-fries.net>
Cc: "Albert D. Cahalan" <acahalan@cs.uml.edu>,
Leon Breedt <ljb@devco.net>,
linux-kernel@vger.kernel.org
Subject: Re: [patch] nonblinking VGA block cursor
Date: Fri, 15 Jun 2001 19:03:56 -0500 (CDT) [thread overview]
Message-ID: <Pine.LNX.4.21.0106151854070.1755-100000@dignity.joshisanerd.com> (raw)
In-Reply-To: <0106160144400D.00879@starship>
On Sat, 16 Jun 2001, Daniel Phillips wrote:
> 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.
>
Aha! A software weenie! A real hardware hacker would have snipped and
soldered it to VCC to get a constant (or add a switch for solid/blink =).
In any case, this strikes me as a matter of policy. I don't care one way
or the other, but if people want a solid cursor, it's not something that
we can really deny them that (unless it's a binary-only driver for the
cursor, of course).
Anyway, this is a silly discusson in general, i figured i would throw in
my $0.02 (strong US cents!)
> 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.
>
*CLACK CLACK CLACK*
(posted with a Model M)
--
/jbm, but you can call me Josh. Really, you can.
"When lasers are outlawed, only outlaws will have lasers"
-- from http://www.altair.org/CO2laser.htm
next prev parent reply other threads:[~2001-06-16 0:04 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
2001-06-16 0:03 ` Josh Myer [this message]
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=Pine.LNX.4.21.0106151854070.1755-100000@dignity.joshisanerd.com \
--to=jbm@joshisanerd.com \
--cc=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).