From: ascott@sedona.intel.com (Andrew M. Scott)
Subject: Re: INFORMAL SURVEY: blinking cursor
Date: Tue, 08 Mar 2005 14:37:43 -0700 [thread overview]
Message-ID: <gfby8cx95ug.fsf@chlr4920.ch.intel.com> (raw)
In-Reply-To: 7ebr9u35ri.fsf@ada2.unipv.it
>> * have you tried using emacs w/ the blinking box
>> cursor?
Yes, it's always on.
>> * do you find it uncomfortable?
>> (if "no", you can skip the next question.)
No
>> * do you use another shape cursor (such as vertical
>> bar)? if so, which?
No.
>> * how do the shape and the blinking affect your
>> (dis)comfort? (i'm looking for correlation info, such as:
>> shape: box, blinking: on, i-find-it: unbearable shape: vertical
>> bar, blinking: on, i-find-it: no-worries in the response.)
I have found a (setq blink-cursor-interval 0.8) setting as more
comfortable than the default 0.5
>> * is cursor blinking a feature you would be inclined to
>> change during an editing session? if so, how often?
No
>> * how do the number of frames visible and the blinking
>> affect your (dis)comfort? (again, looking for correlation
>> info.)
I typically have 3+ frames running, but they overlap like stacked
pieces of paper with slight offsets of the top-left corner coordinate;
therefore mostly the top frame is visible.
To be honest, I don't notice the blinking that much (but blinking is nice
to locate a cursor on a large, cluttered monitor), as I'm usually
cycling between frames, buffers, or typing vs. staring at a static
buffer.
next prev parent reply other threads:[~2005-03-08 21:37 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-08 8:23 INFORMAL SURVEY: blinking cursor Thien-Thi Nguyen
2005-03-08 13:56 ` Chong Yidong
2005-03-08 14:30 ` Ulrich Hobelmann
2005-03-08 15:38 ` August Karlstrom
2005-03-08 17:48 ` Pascal Bourguignon
2005-03-08 18:31 ` Alan Mackenzie
2005-03-08 21:19 ` Ulrich Hobelmann
2005-03-08 18:44 ` roodwriter
2005-03-08 21:20 ` Radomir Hejl
2005-03-08 21:37 ` Andrew M. Scott [this message]
2005-03-08 21:46 ` Mark Plaksin
2005-03-08 21:53 ` Alex Schroeder
2005-03-08 22:37 ` rgb
2005-03-09 1:18 ` Thomas A. Horsley
2005-03-09 3:33 ` Dhruva Krishnamurthy
2005-03-09 7:50 ` Klaus Zeitler
2005-03-09 10:12 ` Daniel Wright
2005-03-09 12:02 ` Slawomir Nowaczyk
2005-03-09 14:28 ` Joe Fineman
2005-03-09 19:19 ` Peter Lee
2005-03-10 22:47 ` Miles Bader
2005-03-13 17:58 ` INFORMAL SUMMARY OF " Alan Mackenzie
2005-03-13 18:59 ` Ulrich Hobelmann
2005-03-14 19:44 ` Jochen Küpper
2005-03-14 20:42 ` Thien-Thi Nguyen
-- strict thread matches above, loose matches on Subject: below --
2005-03-08 14:07 Loyd Fueston
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=gfby8cx95ug.fsf@chlr4920.ch.intel.com \
--to=ascott@sedona.intel.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).