From: storm@cua.dk (Kim F. Storm)
Cc: emacs-devel@gnu.org
Subject: Re: Menu again.
Date: Fri, 25 Mar 2005 23:44:20 +0100 [thread overview]
Message-ID: <m3ll8b9whn.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <200503241555.j2OFtgu28133@raven.dms.auburn.edu> (Luc Teirlinck's message of "Thu, 24 Mar 2005 09:55:42 -0600 (CST)")
Luc Teirlinck <teirllm@dms.auburn.edu> writes:
>> That is why Richard asked to commit it at top level.
>
>>From Richard's message of March 4:
>
> That is persuasive evidence; I am convinced.
That "evidence" was clearly hoaxed as I showed in a subsequent mail.
Without that evidence, maybe Richard wouldn't have agreed to adding
the "blinking cursor" to Options in the first place...
> Since this does not
> fit in the Show/Hide menu, let's add it at top level.
>
> Would someone please do that?
>
> This was after you already presented the arguments you just repeated
> once more.
But it was before we added --no-blinking-cursor.
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
next prev parent reply other threads:[~2005-03-25 22:44 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-24 14:11 Menu again David Kastrup
2005-03-24 14:37 ` Jason Rumney
2005-03-24 15:21 ` David Kastrup
2005-03-24 15:00 ` Luc Teirlinck
2005-03-24 15:32 ` David Kastrup
2005-03-24 15:55 ` Luc Teirlinck
2005-03-25 22:42 ` Kim F. Storm
2005-03-25 23:28 ` David Kastrup
2005-03-26 1:45 ` Nick Roberts
2005-03-26 1:28 ` David Kastrup
2005-03-26 2:15 ` Luc Teirlinck
2005-03-26 3:40 ` Blinking Cursor (was Re: Menu again.) Nick Roberts
2005-03-26 10:50 ` Blinking Cursor David Kastrup
2005-03-26 12:58 ` Nick Roberts
2005-03-27 3:53 ` Blinking Cursor (was Re: Menu again.) Richard Stallman
2005-03-26 2:56 ` Menu again Luc Teirlinck
2005-03-26 8:16 ` Jan D.
2005-03-27 3:53 ` Richard Stallman
2005-03-25 22:44 ` Kim F. Storm [this message]
2005-03-26 2:18 ` Richard Stallman
2005-03-26 10:57 ` David Kastrup
2005-03-28 21:52 ` Kim F. Storm
2005-05-31 4:18 ` Richard Stallman
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=m3ll8b9whn.fsf@kfs-l.imdomain.dk \
--to=storm@cua.dk \
--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).