From: kai.grossjohann@uni-duisburg.de (Kai Großjohann)
Subject: Re: Gnus "beeping" constantly
Date: Wed, 26 Mar 2003 17:42:10 +0100 [thread overview]
Message-ID: <8465q65bbx.fsf@lucy.is.informatik.uni-duisburg.de> (raw)
In-Reply-To: <m3adfu141l.fsf@quimbies.gnus.org>
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> Chris L <chrisl_ak@hotmail.com> writes:
>
>> Any idea why Gnus would constantly be causing system beeps? For some
>> reason, every time I enter a newsgroup, or move from message to
>> message, I get a system beep.
>
> [...]
>
>> I have visible bell set to true (and it is working, generally), but
>> there is no flashing to accompany the beep.
>
> Weird. Unfortunately, `ding' is a built-in function, so you can't
> `debug-on-entry' it, which makes it difficult to track down the
> problem.
Maybe it works to set ring-bell-function to `debug'? Just a stab in
the dark.
--
A preposition is not a good thing to end a sentence with.
prev parent reply other threads:[~2003-03-26 16:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87smtrckyl.fsf@hotmail.com>
2003-03-13 17:15 ` Kai Großjohann
[not found] ` <m3adfu141l.fsf@quimbies.gnus.org>
2003-03-26 16:42 ` Kai Großjohann [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8465q65bbx.fsf@lucy.is.informatik.uni-duisburg.de \
--to=kai.grossjohann@uni-duisburg.de \
/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.
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 NNTP newsgroup(s).