From: Nick Roberts <nickrob@snap.net.nz>
Cc: storm@cua.dk, Luc Teirlinck <teirllm@dms.auburn.edu>,
emacs-devel@gnu.org
Subject: Re: Blinking Cursor
Date: Sun, 27 Mar 2005 00:58:26 +1200 [thread overview]
Message-ID: <16965.23666.165121.188107@farnswood.snap.net.nz> (raw)
In-Reply-To: <x5br96hea9.fsf@lola.goethe.zz>
> > What does it interfere with now?
>
> I think this is one of the cases that does not warrant extended
> traffic on the list, simply because it has no chance of getting
> supported by more than one person.
I was just brainstorming, perhaps I was worn down by the much more extended
traffic about the Options menu. I don't mind you if you think its a crap idea
but please don't others what to think also.
> If anybody except Nick considers clicking on the cursor as an
> interface for stopping it from blinking a good idea, please speak up.
> Other than that, let us call this case closed.
Yes, thats generally how threads proceed, but without usually without a
master of ceremonies.
Nick
next prev parent reply other threads:[~2005-03-26 12:58 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 [this message]
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
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=16965.23666.165121.188107@farnswood.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=emacs-devel@gnu.org \
--cc=storm@cua.dk \
--cc=teirllm@dms.auburn.edu \
/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).