[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#13649: boobytrapped dired-do-async-shell-command question
From: |
Juri Linkov |
Subject: |
bug#13649: boobytrapped dired-do-async-shell-command question |
Date: |
Sat, 09 Feb 2013 02:46:17 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (x86_64-pc-linux-gnu) |
>> > 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.
bug#13649: boobytrapped dired-do-async-shell-command question, Stefan Monnier, 2013/02/08
bug#13649: boobytrapped dired-do-async-shell-command question, jidanni, 2013/02/08
bug#13649: boobytrapped dired-do-async-shell-command question, jidanni, 2013/02/10
bug#13649: boobytrapped dired-do-async-shell-command question, jidanni, 2013/02/10