unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
* bug#52484: Don't beep/flash as part of a response to a question
@ 2021-12-14 16:54 積丹尼 Dan Jacobson
  2021-12-17  4:23 ` Richard Stallman
  2021-12-19 12:58 ` Lars Ingebrigtsen
  0 siblings, 2 replies; 6+ messages in thread
From: 積丹尼 Dan Jacobson @ 2021-12-14 16:54 UTC (permalink / raw)
  To: 52484

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"?





^ permalink raw reply	[flat|nested] 6+ messages in thread

* bug#52484: Don't beep/flash as part of a response to a question
  2021-12-14 16:54 bug#52484: Don't beep/flash as part of a response to a question 積丹尼 Dan Jacobson
@ 2021-12-17  4:23 ` Richard Stallman
  2021-12-17  6:16   ` 積丹尼 Dan Jacobson
  2021-12-19 12:58 ` Lars Ingebrigtsen
  1 sibling, 1 reply; 6+ messages in thread
From: Richard Stallman @ 2021-12-17  4:23 UTC (permalink / raw)
  To: 積丹尼 Dan Jacobson; +Cc: 52484

[[[ 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)







^ permalink raw reply	[flat|nested] 6+ messages in thread

* bug#52484: Don't beep/flash as part of a response to a question
  2021-12-17  4:23 ` Richard Stallman
@ 2021-12-17  6:16   ` 積丹尼 Dan Jacobson
  0 siblings, 0 replies; 6+ messages in thread
From: 積丹尼 Dan Jacobson @ 2021-12-17  6:16 UTC (permalink / raw)
  To: Richard Stallman; +Cc: 52484

>>>>> "RMS" == Richard Stallman <rms@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.





^ permalink raw reply	[flat|nested] 6+ messages in thread

* bug#52484: Don't beep/flash as part of a response to a question
  2021-12-14 16:54 bug#52484: Don't beep/flash as part of a response to a question 積丹尼 Dan Jacobson
  2021-12-17  4:23 ` Richard Stallman
@ 2021-12-19 12:58 ` Lars Ingebrigtsen
  2021-12-19 21:58   ` 積丹尼 Dan Jacobson
  2021-12-20  0:22   ` 積丹尼 Dan Jacobson
  1 sibling, 2 replies; 6+ messages in thread
From: Lars Ingebrigtsen @ 2021-12-19 12:58 UTC (permalink / raw)
  To: 積丹尼 Dan Jacobson; +Cc: 52484

積丹尼 Dan Jacobson <jidanni@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





^ permalink raw reply	[flat|nested] 6+ messages in thread

* bug#52484: Don't beep/flash as part of a response to a question
  2021-12-19 12:58 ` Lars Ingebrigtsen
@ 2021-12-19 21:58   ` 積丹尼 Dan Jacobson
  2021-12-20  0:22   ` 積丹尼 Dan Jacobson
  1 sibling, 0 replies; 6+ messages in thread
From: 積丹尼 Dan Jacobson @ 2021-12-19 21:58 UTC (permalink / raw)
  To: Lars Ingebrigtsen; +Cc: 52484

>>>>> "LI" == Lars Ingebrigtsen <larsi@gnus.org> writes:
LI> 積丹尼 Dan Jacobson <jidanni@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.





^ permalink raw reply	[flat|nested] 6+ messages in thread

* bug#52484: Don't beep/flash as part of a response to a question
  2021-12-19 12:58 ` Lars Ingebrigtsen
  2021-12-19 21:58   ` 積丹尼 Dan Jacobson
@ 2021-12-20  0:22   ` 積丹尼 Dan Jacobson
  1 sibling, 0 replies; 6+ messages in thread
From: 積丹尼 Dan Jacobson @ 2021-12-20  0:22 UTC (permalink / raw)
  To: Lars Ingebrigtsen; +Cc: 52484

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.





^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2021-12-20  0:22 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2021-12-14 16:54 bug#52484: Don't beep/flash as part of a response to a question 積丹尼 Dan Jacobson
2021-12-17  4:23 ` Richard Stallman
2021-12-17  6:16   ` 積丹尼 Dan Jacobson
2021-12-19 12:58 ` Lars Ingebrigtsen
2021-12-19 21:58   ` 積丹尼 Dan Jacobson
2021-12-20  0:22   ` 積丹尼 Dan Jacobson

Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).