GNU bug report logs - #45063
compilation-bell

Previous Next

Package: emacs;

Reported by: 積丹尼 Dan Jacobson <jidanni <at> jidanni.org>

Date: Sun, 6 Dec 2020 05:11:02 UTC

Severity: normal

Done: Eli Zaretskii <eliz <at> gnu.org>

Bug is archived. No further changes may be made.

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 45063 in the body.
You can then email your comments to 45063 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox

Report forwarded to bug-gnu-emacs <at> gnu.org:
bug#45063; Package emacs. (Sun, 06 Dec 2020 05:11:02 GMT) Full text and rfc822 format available.
Acknowledgement sent to 積丹尼 Dan Jacobson <jidanni <at> jidanni.org>:
New bug report received and forwarded. Copy sent to bug-gnu-emacs <at> gnu.org. (Sun, 06 Dec 2020 05:11:02 GMT) Full text and rfc822 format available.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: 積丹尼 Dan Jacobson <jidanni <at> jidanni.org>
To: bug-gnu-emacs <at> gnu.org
Subject: compilation-bell
Date: Sun, 06 Dec 2020 13:09:55 +0800

https://www.quora.com/Why-do-typewriters-have-a-bell
Well compilers should too!
Sure, at the end of a Makefile we could just put
      beep
but a new compilation-bell variable,
'always: ring after every compilation finishes
'long: ring only after compilations finish that took a "long time", that
   you probably forgot are still running.

And ring differently for failed compilations.

(setq compilation-bell-command "beep"); i.e.,:
(setq compilation-bell-command "/usr/bin/beep")

> How '1960's!

Correct.
Reply sent to Eli Zaretskii <eliz <at> gnu.org>:
You have taken responsibility. (Sun, 06 Dec 2020 05:58:02 GMT) Full text and rfc822 format available.
Notification sent to 積丹尼 Dan Jacobson <jidanni <at> jidanni.org>:
bug acknowledged by developer. (Sun, 06 Dec 2020 05:58:02 GMT) Full text and rfc822 format available.

Message #10 received at 45063-done <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: 積丹尼 Dan Jacobson <jidanni <at> jidanni.org>
Cc: 45063-done <at> debbugs.gnu.org
Subject: Re: bug#45063: compilation-bell
Date: Sun, 06 Dec 2020 07:56:36 +0200

> From: 積丹尼 Dan Jacobson
>  <jidanni <at> jidanni.org>
> Date: Sun, 06 Dec 2020 13:09:55 +0800
> 
> https://www.quora.com/Why-do-typewriters-have-a-bell
> Well compilers should too!
> Sure, at the end of a Makefile we could just put
>       beep
> but a new compilation-bell variable,
> 'always: ring after every compilation finishes
> 'long: ring only after compilations finish that took a "long time", that
>    you probably forgot are still running.

See compilation-finish-functions hook, you can put there anything you
want.

> And ring differently for failed compilations.

The functions on the above hook are called with the description of how
the compilation ended, so you can vary the result as you see fit.

Closing.
bug archived. Request was from Debbugs Internal Request <help-debbugs <at> gnu.org> to internal_control <at> debbugs.gnu.org. (Sun, 03 Jan 2021 12:24:06 GMT) Full text and rfc822 format available.
This bug report was last modified 4 years and 162 days ago.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.