From: "Drew Adams" <drew.adams@oracle.com>
To: "'Sven Joachim'" <svenjoac@gmx.de>,
<1305@emacsbugs.donarmstrong.com>,
"'Jason Spiro'" <jasonspiro4@gmail.com>
Cc: rms@gnu.org, 'Tim Connors' <tim.w.connors@gmail.com>
Subject: bug#1305: All code that currently beeps should use visualbellinstead
Date: Mon, 17 Nov 2008 00:19:10 -0800 [thread overview]
Message-ID: <002e01c9488d$2b55c640$0200a8c0@us.oracle.com> (raw)
In-Reply-To: <8763mmsrw3.fsf@gmx.de>
> > Firefox's incremental search feature does it much better than Emacs.
> > When an incremental search is failing, it doesn't just add the word
> > "Failing" onscreen. It also changes the search text entry field to
> > have a bright red background. This attracts the eye to see that the
> > search is failing. Should I file a bug to request that Emacs do the
> > same?
>
> Emacs does it another way, one that in my opinion is even better: it
> highlights just the part of the search that failed. This is quite
> convenient if you have already typed several extra characters before
> noticing the search failure.
>
> Note that this is not available in Emacs 22, but has been in the trunk
> for about a year.
It's not only better in general, it's more appropriate for incremental search.
The increment of your search that is successful (matches) is not highlighted;
only the increment that is a mismatch is highlighted. The highlighting is added
and removed incrementally, as you type and delete characters.
next prev parent reply other threads:[~2008-11-17 8:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-17 7:32 bug#1305: All code that currently beeps should use visual bellinstead Tim Connors
2008-11-17 7:37 ` Jason Spiro
2008-11-17 8:01 ` Sven Joachim
2008-11-17 8:19 ` Drew Adams [this message]
2008-11-17 14:52 ` Stefan Monnier
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='002e01c9488d$2b55c640$0200a8c0@us.oracle.com' \
--to=drew.adams@oracle.com \
--cc=1305@emacsbugs.donarmstrong.com \
--cc=jasonspiro4@gmail.com \
--cc=rms@gnu.org \
--cc=svenjoac@gmx.de \
--cc=tim.w.connors@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).