unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: "Jason Spiro" <jasonspiro4@gmail.com>
Cc: Tim Connors <tim.w.connors@gmail.com>,
	bug-gnu-emacs@gnu.org, bug-submit-list@donarmstrong.com,
	1305@emacsbugs.donarmstrong.com, rms@gnu.org
Subject: bug#1305: All code that currently beeps should use visual bellinstead
Date: Mon, 17 Nov 2008 09:52:25 -0500	[thread overview]
Message-ID: <jwvvdumv23d.fsf-monnier+emacsbugreports@gnu.org> (raw)
In-Reply-To: <c241693f0811162337rbc6295dp8637fa0afe4ce038@mail.gmail.com> (Jason Spiro's message of "Mon, 17 Nov 2008 02:37:59 -0500")

> 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?

I don't think it addresses Tim's problem that he simply doesn't see
(aka. look at) the echo area at all.

The bell is more noticeable (both the visual and the auditory one).


        Stefan







  parent reply	other threads:[~2008-11-17 14:52 UTC|newest]

Thread overview: 21+ 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     ` bug#1305: All code that currently beeps should use visualbellinstead Drew Adams
2008-11-17 14:52   ` Stefan Monnier [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-11-09  1:50 bug#1305: All code that currently beeps should use visual bell instead Jason Spiro
2008-11-09  3:57 ` bug#1305: All code that currently beeps should use visual bellinstead Drew Adams
2008-11-09  4:08   ` Jason Spiro
2008-11-09 19:17     ` Eli Zaretskii
2008-11-09 19:04   ` Eli Zaretskii
2008-11-09 19:19     ` Drew Adams
2008-11-09 20:00       ` Eli Zaretskii
2008-11-10  2:07         ` Stefan Monnier
2008-11-10  6:28           ` Drew Adams
2008-11-10  8:34           ` Lennart Borgman
2008-11-10 15:22             ` Stefan Monnier
2008-11-10 16:58               ` Lennart Borgman
2008-11-11 18:38                 ` Jason A. Spiro
2008-11-10 22:17           ` Richard M. Stallman
2008-11-11 18:50             ` Jason Spiro
2008-11-12  3:33               ` Richard M. Stallman
2008-11-13  7:41                 ` Jason Spiro

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=jwvvdumv23d.fsf-monnier+emacsbugreports@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=1305@emacsbugs.donarmstrong.com \
    --cc=bug-gnu-emacs@gnu.org \
    --cc=bug-submit-list@donarmstrong.com \
    --cc=jasonspiro4@gmail.com \
    --cc=rms@gnu.org \
    --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).