From: Miles Bader <snogglethorpe@gmail.com>
Cc: Juri Linkov <juri@jurta.org>,
emacs-devel@gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>,
miles@gnu.org
Subject: Re: Type Ahead Find
Date: Sun, 20 Mar 2005 08:33:58 +0900 [thread overview]
Message-ID: <fc339e4a050319153356b2aee@mail.gmail.com> (raw)
In-Reply-To: <x53bur5lva.fsf@lola.goethe.zz>
On Sat, 19 Mar 2005 23:09:13 +0100, David Kastrup <dak@gnu.org> wrote:
> > I-search (in node File Variables): local variables
> >
> > That's also more similar to other "informational messages" used by
> > search, e.g., "overwrapped" or whatever.
>
> Please not. Tags like that make the search text jump left and right
> as they change, which makes it harder to keep track of it. For a
> basic error condition once per search, this is tolerable. As a
> regular part of the operation (as when going through several files),
> it isn't.
Yeah; the node-name info is gratuitous anyway - - the node name is
already right there in the modeline about .5 cm above the i-search
prompt.
Something like:
Global info I-search: foo
[Maybe "Cross-node" would be better than "Global"?]
or whatever would be even more similar to the existing "Wrapped", get
the point across well, and address your concern about the prompt size
bouncing around excessively.
-Miles
--
Do not taunt Happy Fun Ball.
next prev parent reply other threads:[~2005-03-19 23:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-18 19:45 Type Ahead Find Juri Linkov
2005-03-18 20:21 ` Drew Adams
2005-03-18 21:53 ` Stefan Monnier
2005-03-19 12:29 ` Juri Linkov
2005-03-19 21:19 ` Miles Bader
2005-03-19 22:09 ` David Kastrup
2005-03-19 23:33 ` Miles Bader [this message]
2005-03-20 20:17 ` Juri Linkov
2005-03-20 21:46 ` David Kastrup
2005-03-20 22:04 ` Miles Bader
2005-03-21 19:28 ` Juri Linkov
2005-03-20 20:14 ` Juri Linkov
2005-03-20 20:22 ` Juri Linkov
2005-03-20 0:22 ` Richard Stallman
2005-03-20 20:19 ` Juri Linkov
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fc339e4a050319153356b2aee@mail.gmail.com \
--to=snogglethorpe@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=juri@jurta.org \
--cc=miles@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.