unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@jurta.org>
Cc: snogglethorpe@gmail.com, emacs-devel@gnu.org,
	monnier@iro.umontreal.ca, miles@gnu.org
Subject: Re: Type Ahead Find
Date: Mon, 21 Mar 2005 21:28:14 +0200	[thread overview]
Message-ID: <878y4golg1.fsf@jurta.org> (raw)
In-Reply-To: <x5oede7zy5.fsf@lola.goethe.zz> (David Kastrup's message of "Sun, 20 Mar 2005 22:46:42 +0100")

David Kastrup <dak@gnu.org> writes:
> Again: I don't like the left-right jump of the minibuffer caused by
> that.  If there really is a need for that kind of information, can't
> we put this in the mode-line lighter of Isearch mode?
>
> Like Isearch/Wrapped, Isearch/X-Node...
>
> Then the information is available in case of need, but does not take
> up room and concentration in the minibuffer.

As I see in isearch.el there is the following line in `isearch-mode'
function with the comment indicating that someone already considered
this idea:

  (setq	isearch-mode " Isearch")  ;; forward? regexp?

This suggests to put the search type in the mode-line.  But I think
its biggest drawback is that the search state might be not visible
in the mode-line when the mode-line is too wide.  For example,
in the current buffer when I activate the search I see the text
"Isearch" truncated in the mode-line:

-=:**  *wide reply to David Kastrup*   All (32,42)    (Message MML Abbrev Fill Isea

Any additional information in the mode-line will not be visible at all.

So the only place for this information is the minibuffer.
Instead of putting it in the message prefix we could put
it in the suffix in square brackets:

I-search: foo [Failing]
I-search: foo [Wrapped]
I-search: foo [Failing wrapped]

But this doesn't look good either when after wrapping the suffix [Wrapped]
remains for the wrapped search.

-- 
Juri Linkov
http://www.jurta.org/emacs/

  parent reply	other threads:[~2005-03-21 19:28 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
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 [this message]
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=878y4golg1.fsf@jurta.org \
    --to=juri@jurta.org \
    --cc=emacs-devel@gnu.org \
    --cc=miles@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=snogglethorpe@gmail.com \
    /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).