From: Marcin Borkowski <mbork@mbork.pl>
To: Eli Zaretskii <eliz@gnu.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Is it only me or is your ding also silent?
Date: Fri, 21 Jul 2017 09:58:29 +0200 [thread overview]
Message-ID: <87k2326x22.fsf@jane> (raw)
In-Reply-To: <83vamm9v8s.fsf@gnu.org>
On 2017-07-21, at 08:09, Eli Zaretskii <eliz@gnu.org> wrote:
>> From: Marcin Borkowski <mbork@mbork.pl>
>> Date: Fri, 21 Jul 2017 06:42:52 +0200
>>
>> as in the subject. I defined
>>
>> (defun system-beep ()
>> (call-process "beep"))
>>
>> which beeps, but M-: (ding) does not produce any sound here.
>
> It does here.
>
>> I have fresh Emacs compiled from sources on fresh Arch GNU/Linux.
>
> Could be some system-level setting, unrelated to Emacs, perhaps?
I doubt it; the command line "beep" program does indeed beep.
Also, I checked with emacs -Q, just to be sure. Still silence.
>> Is it because ring-bell-function is nil?
>
> No, ring-bell-function is for when you want to customize how to rin
> the bell, then you need to write a function to do that and bind
> ring-bell-function to it. By default, ring-bell-function always was
> nil, because Emacs is using its own code to beep.
That's what I would think, but I wanted to make sure.
>> In the old days, C-g or M-: (ding) used to beep!
>
> It still does here.
Strange...
--
Marcin Borkowski
next prev parent reply other threads:[~2017-07-21 7:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-21 4:42 Is it only me or is your ding also silent? Marcin Borkowski
2017-07-21 6:09 ` Eli Zaretskii
2017-07-21 7:58 ` Marcin Borkowski [this message]
2017-07-21 7:50 ` Héctor Lahoz
2017-07-21 10:25 ` Héctor Lahoz
2017-07-21 16:03 ` Emanuel Berg
2017-07-22 8:39 ` Héctor Lahoz
2017-07-22 16:48 ` Emanuel Berg
2017-07-22 9:17 ` tomas
2017-07-22 12:53 ` Héctor Lahoz
2017-07-22 14:23 ` tomas
2017-07-23 5:58 ` Marcin Borkowski
2017-07-23 8:37 ` tomas
2017-07-23 11:11 ` Emanuel Berg
2017-07-26 19:41 ` Marcin Borkowski
2017-07-26 20:00 ` Emanuel Berg
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=87k2326x22.fsf@jane \
--to=mbork@mbork.pl \
--cc=eliz@gnu.org \
--cc=help-gnu-emacs@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.