GNU bug report logs - #13649
boobytrapped dired-do-async-shell-command question

Previous Next

Package: emacs;

Reported by: jidanni <at> jidanni.org

Date: Thu, 7 Feb 2013 16:28:02 UTC

Severity: minor

Fixed in version 29.1

Done: Lars Ingebrigtsen <larsi <at> gnus.org>

Bug is archived. No further changes may be made.

Full log

View this message in rfc822 format

From: Stefan Monnier <monnier <at> iro.umontreal.ca>
To: Juri Linkov <juri <at> jurta.org>
Cc: 13649 <at> debbugs.gnu.org, jidanni <at> jidanni.org
Subject: bug#13649: boobytrapped dired-do-async-shell-command question
Date: Fri, 08 Feb 2013 10:11:38 -0500

>> A command is running in the default buffer.  Use a new buffer? (yes or no)
>> Which is a boobytrapped question, as picking "no" will always end up
>> in failure...
> Ah, to you "no" means "don't use a new buffer"?  Yes, this is too ambiguous.
> A better question would be:

>   A command is running in the default buffer.  Run in a new buffer?
>     (yes or no)

I think it's got the same problem.  I think the question should be more
something like:

  A command is running in the default buffer.  Kill it or use a new buffer?

with C-g being the answer for "don't use a new buffer and don't kill it".


        Stefan
This bug report was last modified 3 years and 88 days ago.

Previous Next

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