GNU bug report logs - #52484
Don't beep/flash as part of a response to a question

Previous Next

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

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

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: Don't beep/flash as part of a response to a question
Date: Wed, 15 Dec 2021 00:54:14 +0800

When prompted:
  A compilation process is running; kill it? (yes or no)
if we say "no",
our screen flashes, like we were a bad boy,
and we see
"Cannot have two processes in ‘*compilation*’ at once"
OK, but why the beep/flash "spanking"?

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

From: Richard Stallman <rms <at> gnu.org>
To: 積丹尼 Dan Jacobson
 <jidanni <at> jidanni.org>
Cc: 52484 <at> debbugs.gnu.org
Subject: Re: bug#52484: Don't beep/flash as part of a response to a question
Date: Thu, 16 Dec 2021 23:23:58 -0500

[[[ To any NSA and FBI agents reading my email: please consider    ]]]
[[[ whether defending the US Constitution against all enemies,     ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

  > OK, but why the beep/flash "spanking"?

It isn't meant as a rebuke.  It just means that the command could not
proceed.

-- 
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)

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

From: 積丹尼 Dan Jacobson <jidanni <at> jidanni.org>
To: Richard Stallman <rms <at> gnu.org>
Cc: 52484 <at> debbugs.gnu.org
Subject: Re: bug#52484: Don't beep/flash as part of a response to a question
Date: Fri, 17 Dec 2021 14:16:20 +0800

>>>>> "RMS" == Richard Stallman <rms <at> gnu.org> writes:

>> OK, but why the beep/flash "spanking"?

RMS> It isn't meant as a rebuke.  It just means that the command could not
RMS> proceed.

Yeah, but the fire trucks are already at the scene. No need to turn the
siren back on.

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

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: 積丹尼 Dan Jacobson <jidanni <at> jidanni.org>
Cc: 52484 <at> debbugs.gnu.org
Subject: Re: bug#52484: Don't beep/flash as part of a response to a question
Date: Sun, 19 Dec 2021 13:58:25 +0100

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

> When prompted:
>   A compilation process is running; kill it? (yes or no)
> if we say "no",
> our screen flashes, like we were a bad boy,
> and we see
> "Cannot have two processes in ‘*compilation*’ at once"
> OK, but why the beep/flash "spanking"?

When you type "no" it proceeds, and then errors out.  The error will
beep at you, so everything here seems to be working as designed, and I'm
closing this bug report.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

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

From: 積丹尼 Dan Jacobson <jidanni <at> jidanni.org>
To: Lars Ingebrigtsen <larsi <at> gnus.org>
Cc: 52484 <at> debbugs.gnu.org
Subject: Re: bug#52484: Don't beep/flash as part of a response to a question
Date: Mon, 20 Dec 2021 05:58:15 +0800

>>>>> "LI" == Lars Ingebrigtsen <larsi <at> gnus.org> writes:
LI> 積丹尼 Dan Jacobson <jidanni <at> jidanni.org> writes:

>> When prompted:
>> A compilation process is running; kill it? (yes or no)
>> if we say "no",
>> our screen flashes, like we were a bad boy,
>> and we see
>> "Cannot have two processes in ‘*compilation*’ at once"
>> OK, but why the beep/flash "spanking"?

LI> When you type "no" it proceeds, and then errors out.  The error will
LI> beep at you, so everything here seems to be working as designed, and I'm
LI> closing this bug report.

"You can't have two cars on the same one lane road.
Proceed? (yes, no)."
No.
(And then you redirect him over the cliff instead of just pressing the
brake.) OK, never mind.

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

From: 積丹尼 Dan Jacobson <jidanni <at> jidanni.org>
To: Lars Ingebrigtsen <larsi <at> gnus.org>
Cc: 52484 <at> debbugs.gnu.org
Subject: Re: bug#52484: Don't beep/flash as part of a response to a question
Date: Mon, 20 Dec 2021 08:22:44 +0800

Same broken behavior in Dired:
File V_20211207_080008_vHDR_On.mp4 is large (27.7 MiB), really open? (y)es or (n)o or (l)iterally

If we say "n" we get a flash or beep, and
user-error: Aborted

OK, but no need for the flash/beep.

P.S., if we say y,
then it assumes we want to see the bytes.
But it should know we probably want to watch
it as a movie.

Sure we might not even have a movie player installed,
but that's what most people want to do with mp4's.

Previous Next

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