From: Jason Rumney <jasonr@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Putting blink-cursor-mode in Options menu.
Date: Tue, 01 Mar 2005 18:47:52 +0000 [thread overview]
Message-ID: <uoee35hk7.fsf@jasonrumney.net> (raw)
In-Reply-To: <200503011726.j21HQxZ17274@raven.dms.auburn.edu> (Luc Teirlinck's message of "Tue, 1 Mar 2005 11:26:59 -0600 (CST)")
Luc Teirlinck <teirllm@dms.auburn.edu> writes:
> This is unbelievable. We are talking about adding an option to a
> menu, not about changing a default.
If we added everyone's pet option to the Options menu, we'd end up
with hundreds of options that would just be confusing to users.
I don't see any need to do anything here. New users will be used to
blinking cursors from the other apps they use, only a few experienced
Emacs users who use nothing else will be offended by the blinking, and
they can easily figure out how to disable it.
next prev parent reply other threads:[~2005-03-01 18:47 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-01 0:34 Putting blink-cursor-mode in Options menu Luc Teirlinck
2005-03-01 8:24 ` Kim F. Storm
2005-03-01 12:18 ` Robert J. Chassell
2005-03-01 14:11 ` Chong Yidong
2005-03-01 14:27 ` David Kastrup
2005-03-01 16:46 ` Luc Teirlinck
2005-03-01 13:28 ` David Kastrup
2005-03-01 16:08 ` Luc Teirlinck
2005-03-01 16:58 ` David Kastrup
2005-03-01 17:26 ` Luc Teirlinck
2005-03-01 18:47 ` Jason Rumney [this message]
2005-03-01 19:02 ` Luc Teirlinck
2005-03-01 19:24 ` Robert J. Chassell
2005-03-01 20:16 ` Jason Rumney
2005-03-02 13:32 ` Robert J. Chassell
2005-03-02 18:41 ` Eli Zaretskii
2005-03-01 19:44 ` David Kastrup
2005-03-02 0:21 ` Luc Teirlinck
2005-03-02 1:10 ` David Kastrup
2005-03-01 20:48 ` Eli Zaretskii
2005-03-03 4:10 ` Luc Teirlinck
2005-03-03 8:57 ` Jason Rumney
2005-03-03 20:57 ` Richard Stallman
2005-03-03 21:35 ` David Kastrup
2005-03-03 22:42 ` Lennart Borgman
2005-03-01 19:27 ` David Kastrup
2005-03-01 21:26 ` Kim F. Storm
2005-03-02 0:29 ` Luc Teirlinck
2005-03-02 13:44 ` Robert J. Chassell
2005-03-02 17:56 ` David Kastrup
2005-03-03 1:38 ` Miles Bader
2005-03-03 4:32 ` Luc Teirlinck
2005-03-03 2:27 ` Richard Stallman
2005-03-03 12:26 ` Andreas Schwab
2005-03-01 16:16 ` Luc Teirlinck
2005-03-02 11:22 ` Richard Stallman
2005-03-02 13:04 ` David Kastrup
2005-03-02 14:30 ` Kim F. Storm
2005-03-02 16:23 ` Robert J. Chassell
2005-03-02 17:53 ` David Kastrup
2005-03-02 22:19 ` Kim F. Storm
2005-03-03 3:34 ` Luc Teirlinck
2005-03-03 20:57 ` Richard Stallman
2005-03-02 13:35 ` Jason Rumney
2005-03-03 20:57 ` Richard Stallman
2005-03-02 23:34 ` Juri Linkov
2005-03-03 20:57 ` Richard Stallman
2005-03-03 19:45 ` Per Abrahamsen
2005-03-04 23:44 ` Richard Stallman
2005-03-05 1:20 ` Luc Teirlinck
2005-03-06 21:11 ` Kim F. Storm
2005-03-06 22:44 ` Andreas Schwab
2005-03-06 23:00 ` Miles Bader
2005-03-08 2:51 ` Richard Stallman
2005-03-08 3:32 ` Luc Teirlinck
2005-03-08 8:21 ` Kim F. Storm
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=uoee35hk7.fsf@jasonrumney.net \
--to=jasonr@gnu.org \
--cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).