unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Miles Bader <snogglethorpe@gmail.com>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>, emacs-devel@gnu.org
Subject: Re: Type Ahead Find
Date: Sun, 20 Mar 2005 06:19:50 +0900	[thread overview]
Message-ID: <fc339e4a050319131952be9d5f@mail.gmail.com> (raw)
In-Reply-To: <87psxvq11d.fsf@jurta.org>

On Sat, 19 Mar 2005 14:29:29 +0200, Juri Linkov <juri@jurta.org> wrote:
> There is the text under point only in my first example.  It would be
> very useful to display hidden text like when Info-hide-note-references
> hides the reference node names, so for example, when isearch reaches
> the reference `*Note Local Variables in Files: (emacs)File variables',
> it would display the hidden node name in square brackets:
> 
> I-search: local variables [(emacs)File variables]

I disagree strongly -- I've been seeing this sort of usage in the
latest info-mode isearch, and I find it very confusing to see random
information put into square-brackets after the input, because that
area is used normally for error messages or very temporary feedback on
the user's input.  [The use in info-isearch that I'm complaining about
is " [initial node]" --- which BTW is also confusingly worded, it took
me a while to realize what that was trying to say...]

Maybe there should be an area for "interesting information", but it
shouldn't be the same area used for error messages.

Ideally it'd  be some area not so noticeable, e.g., at the far-right
edge of the mini-buffer; but since that would require new redisplay
hacking, how about just something like:

   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.

[It seems a good idea for space reasons to omit the info-file name;
AFAIK, isearch won't cross info file boundaries.]

-Miles
-- 
Do not taunt Happy Fun Ball.

  reply	other threads:[~2005-03-19 21:19 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 [this message]
2005-03-19 22:09       ` David Kastrup
2005-03-19 23:33         ` Miles Bader
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

  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=fc339e4a050319131952be9d5f@mail.gmail.com \
    --to=snogglethorpe@gmail.com \
    --cc=emacs-devel@gnu.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 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).