From: Loyd Fueston <l.fueston@att.net>
Subject: Re: INFORMAL SURVEY: blinking cursor
Date: Tue, 08 Mar 2005 09:07:46 -0500 [thread overview]
Message-ID: <10487.7038430006$1110309514@news.gmane.org> (raw)
Thien-Thi Nguyen <ttn@glug.org> writes:
> * have you tried using emacs w/ the blinking box cursor?
yes
> * do you find it uncomfortable?
> (if "no", you can skip the next question.)
distracting and potentially uncomfortable
> * do you think it is an imposition to put:
> (blink-cursor-mode 0)
> in ~/.emacs to turn it off?
No. That's what I do. Been using emacs for 5 years and got most of
those basic issues settled in first year or so.
> * do you use another shape cursor (such as vertical bar)?
no, just the box and hollowed-box in window not in focus
> * is cursor blinking a feature you would be inclined to
> change during an editing session? if so, how often?
no. I just leave it off.
I find customization to be a little confusing because of all the
options, except when I already know the name of a specific group. Has
anyone ever thought about providing a documented template dot-emacs
suitable for inexperienced users, maybe putting up a message on the
initial splash-screen? Once someone sees a few customizations that
actually affect his sessions, and learns a little bit about emacs
docs, it isn't that hard to deal with those customizations. It's just
those initial changes that are confusing.
I would be willing to help produce and document such a dot-emacs after
April. (Besides basic text-editing, I use auctex, gnus, and org-mode
extensively -- but not always in a sophisticated manner. slime and
other CL packages sometimes.)
next reply other threads:[~2005-03-08 14:07 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-08 14:07 Loyd Fueston [this message]
-- strict thread matches above, loose matches on Subject: below --
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
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
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='10487.7038430006$1110309514@news.gmane.org' \
--to=l.fueston@att.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 read-only IMAP folder(s) and NNTP newsgroup(s).