bug-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#13649: boobytrapped dired-do-async-shell-command question


From: Eli Zaretskii
Subject: bug#13649: boobytrapped dired-do-async-shell-command question
Date: Fri, 08 Feb 2013 15:44:08 +0200

> From: Juri Linkov <address@hidden>
> Date: Fri, 08 Feb 2013 10:25:01 +0200
> Cc: address@hidden
> 
> > 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)?

> 77 characters long, but I have no idea how to make it shorter
> without much loss of meaning.

I think we should try making it crystal clear and not worry too much
about its length.  The minibuffer is perfectly capable of displaying
multi-line prompts.





reply via email to

[Prev in Thread] Current Thread [Next in Thread]