GNU bug report logs - #45063
compilation-bell

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#45063: closed (compilation-bell)
Date: Sun, 06 Dec 2020 05:58:02 +0000

[Message part 1 (text/plain, inline)]

Your message dated Sun, 06 Dec 2020 07:56:36 +0200
with message-id <83h7ozbhpn.fsf <at> gnu.org>
and subject line Re: bug#45063: compilation-bell
has caused the debbugs.gnu.org bug report #45063,
regarding compilation-bell
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
45063: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=45063
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

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.

[Message part 3 (message/rfc822, inline)]

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.

Previous Next

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