unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@jurta.org>
To: Dani Moncayo <dmoncayo@gmail.com>
Cc: 12078@debbugs.gnu.org
Subject: bug#12078: 24.1; Improve the I-search prompt
Date: Wed, 08 Aug 2012 11:06:19 +0300	[thread overview]
Message-ID: <87mx25g64k.fsf@mail.jurta.org> (raw)
In-Reply-To: <CAH8Pv0gc_z-aQY2xKKkQcaetH=NBvVL+df7uefgSfbH6GEhdgw@mail.gmail.com> (Dani Moncayo's message of "Mon, 30 Jul 2012 02:45:42 +0200")

> However, on second thought, I think that the "failing" message is
> actually unnecessary.  Looking at the echo area, it is obvious whether
> the current search is failing or not (if it's failing, the unmatched
> text will be on a different face).

After trying this I think the "[failing]" message doesn't look too nice.
As you mentioned, it is unnecessary due to the `isearch-fail' face.
But then this message still should be displayed in environments that don't
support the `isearch-fail' face.

The "[pending]" message should be changed too to address complaints
that it's unclear what does it mean.  Maybe something like
"[Search type changed]"

The "[wrapped]" message could be displayed only once after wrapping,
like e.g. in Firefox that displays the message
"Reached top of page, continued from bottom" or
"Reached end of page, continued from top".





  parent reply	other threads:[~2012-08-08  8:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-28 17:56 bug#12078: 24.1; Improve the I-search prompt Dani Moncayo
2012-07-29  0:35 ` Juri Linkov
2012-07-29 18:04   ` Juri Linkov
2012-07-30  0:45     ` Dani Moncayo
2012-07-30  9:25       ` Stefan Monnier
2012-07-30  9:30         ` Dani Moncayo
2012-07-30 23:03           ` Stefan Monnier
2012-07-30 23:50             ` Dani Moncayo
2012-08-01 23:29               ` Stefan Monnier
2012-08-08  8:06       ` Juri Linkov [this message]
2012-08-08  8:30         ` Dani Moncayo
2020-09-18 15:05 ` Lars Ingebrigtsen

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=87mx25g64k.fsf@mail.jurta.org \
    --to=juri@jurta.org \
    --cc=12078@debbugs.gnu.org \
    --cc=dmoncayo@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).