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

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

From: Juri Linkov <juri <at> jurta.org>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 13649 <at> debbugs.gnu.org, jidanni <at> jidanni.org
Subject: Re: bug#13649: boobytrapped dired-do-async-shell-command question
Date: Sat, 09 Feb 2013 02:46:17 +0200

>> > 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)
>
> Still not clear, IMO (what "default buffer"? run what?).  How about
>
>   Shell output buffer is used by another command; run this command in a new buffer (yes or no)?

I'd rather make the prompt short and add a "help" option
(e.g. "yes/no/help" or "y/n/h") that will display the full
explanation of all options with a link to their customization.
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.