From: Marcin Borkowski <mbork@wmi.amu.edu.pl>
To: help-gnu-emacs@gnu.org
Subject: Re: Ding doing nothing
Date: Fri, 09 Jan 2015 20:45:19 +0100 [thread overview]
Message-ID: <87lhlbyc0a.fsf@wmi.amu.edu.pl> (raw)
In-Reply-To: <87mw5r3gd3.fsf@turtle.gmx.de>
On 2015-01-09, at 20:26, Sven Joachim <svenjoac@gmx.de> wrote:
> On 2015-01-09 19:38 +0100, Marcin Borkowski wrote:
>
>> M-: (ding) does not make any sound (I use Ubuntu Linux and did not mess
>> around with sound setting). I can hear no sound in the graphical Emacs
>> interface as well as in the terminal (both a terminal program under
>> X and the text mode). What might be the cause? Visible bell works just
>> right (if I turn it on, that is.) Of course, I did my checks with
>> emacs -Q.
>
> Probably that's because (ding) uses the PC speaker, and Ubuntu disables
> it by default. If you run "sudo modprobe pcspkr", does the bell work?
Nope. Stupid Ubuntu. It's making me more and more angry. I though it
is me (the owner of the machine) who should decide what is turned on and
what is turned off. Of course, in the "system settings" dialog there
was no suitable option. Why bother using Ubuntu over, say, Arch, if
I have to hunt for text config files in /etc anyway?
> To enable the PC speaker permanently, comment out the line with
> "blacklist pcspkr" in /etc/modprobe.d/blacklist.conf.
Thanks a lot! I guess I'll restart my computer /only/ to check whether
this works.
> Cheers,
> Sven
Best,
--
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Faculty of Mathematics and Computer Science
Adam Mickiewicz University
next prev parent reply other threads:[~2015-01-09 19:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.17554.1420828751.1147.help-gnu-emacs@gnu.org>
2015-01-09 19:26 ` Ding doing nothing Sven Joachim
2015-01-09 19:45 ` Marcin Borkowski [this message]
2015-01-09 21:08 ` Marcin Borkowski
2015-01-09 21:47 ` Bob Proulx
2015-01-11 13:27 ` Marcin Borkowski
2015-01-12 21:31 ` Michael Heerdegen
2015-01-09 18:38 Marcin Borkowski
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=87lhlbyc0a.fsf@wmi.amu.edu.pl \
--to=mbork@wmi.amu.edu.pl \
--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.