From: David Kastrup <dak@gnu.org>
Cc: storm@cua.dk, emacs-devel@gnu.org, rms@gnu.org, monnier@iro.umontreal.ca
Subject: Re: font-lock and shell scripts: Raises redisplay errors in highlight pattern:
Date: Fri, 14 Jul 2006 15:04:50 +0200 [thread overview]
Message-ID: <85wtage3rh.fsf@lola.goethe.zz> (raw)
In-Reply-To: <17591.38274.352202.751899@localhost.localdomain> (T. V. Raman's message of "Fri, 14 Jul 2006 06:00:50 -0700")
"T. V. Raman" <raman@users.sf.net> writes:
> Unhandled errors do make a beep which is correct.
>
> But that is not sufficient for the user who is not looking at
> the display --- I need to say "why" it beeped.
>
> Also, very often I dont sit at my PC -- I sit somewhere outside
> with a wireless keyboard and speakers, and sadly the PC speaker
> beep only beeps at the PC -- not over the sound card.
Could be a matter of mixer control.
> The latter is a bit esoteric I admit -- but for something like
> the vm mail reader signalling end of folder I really need more
> feedback than a beep.
visible-bell is a variable defined in `C source code'.
Its value is t
Documentation:
*Non-nil means try to flash the frame to represent a bell.
See also `ring-bell-function'.
You can customize this variable.
[back]
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
next prev parent reply other threads:[~2006-07-14 13:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-06 3:38 font-lock and shell scripts: Raises redisplay errors in highlight pattern: T. V. Raman
2006-07-06 8:29 ` Romain Francoise
2006-07-06 10:01 ` Kim F. Storm
2006-07-07 4:01 ` T. V. Raman
2006-07-07 14:18 ` Stefan Monnier
2006-07-13 4:08 ` T. V. Raman
2006-07-13 15:30 ` Stefan Monnier
2006-07-14 1:28 ` T. V. Raman
2006-07-14 4:06 ` Richard Stallman
2006-07-14 13:00 ` T. V. Raman
2006-07-14 13:04 ` David Kastrup [this message]
2006-07-14 13:09 ` Chong Yidong
2006-07-15 1:43 ` T. V. Raman
2006-07-15 13:37 ` Richard Stallman
2006-07-15 14:27 ` T. V. Raman
2006-07-16 6:25 ` Richard Stallman
2006-07-16 17:18 ` T. V. Raman
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=85wtage3rh.fsf@lola.goethe.zz \
--to=dak@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=rms@gnu.org \
--cc=storm@cua.dk \
/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).