From: Leon Breedt <ljb@devco.net>
To: "Albert D. Cahalan" <acahalan@cs.uml.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [patch] nonblinking VGA block cursor
Date: Fri, 15 Jun 2001 22:22:14 +0200 [thread overview]
Message-ID: <20010615222214.A3772@rinoa.prv.dev.itouchnet.net> (raw)
In-Reply-To: <20010615162249.A1328@rinoa.rinoa> <200106151921.f5FJLsc03635@saturn.cs.uml.edu>
In-Reply-To: <200106151921.f5FJLsc03635@saturn.cs.uml.edu>; from acahalan@cs.uml.edu on Fri, Jun 15, 2001 at 03:21:54PM -0400
On Fri, Jun 15, 2001 at 03:21:54PM -0400, 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.
I don't want them to, because I prefer non-blinking. It feels more
solid, kind of like driving a tank instead of a little dune buggy ;)
> The blinking cursor is implemented in your video hardware.
> IBM knew what was right for you.
Uh, said hardware lets you disable the blinking. Maybe in a slightly
non-standard way, who cares?
> Of course FreeBSD has a block cursor. It was easy to program,
> and it seems nice to the pot-smoking hippies out in Berkeley.
> FreeBSD doesn't define standards. FreeBSD breaks standards.
> (zombie creation, "ps -ef", partition tables, pty allocation...)
It's all about choice, man. I want the choice to have certain
behaviour if I wish.
--
lj breedt
coder
next prev parent reply other threads:[~2001-06-15 20:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-15 14:22 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 [this message]
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=20010615222214.A3772@rinoa.prv.dev.itouchnet.net \
--to=ljb@devco.net \
--cc=acahalan@cs.uml.edu \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®