From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Juri Linkov Newsgroups: gmane.emacs.bugs Subject: bug#13649: boobytrapped dired-do-async-shell-command question Date: Sat, 09 Feb 2013 02:46:17 +0200 Organization: JURTA Message-ID: <878v6ycnv0.fsf@mail.jurta.org> References: <871ucsjdl1.fsf@jidanni.org> <87liazyzz6.fsf@mail.jurta.org> <83a9re9azb.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1360372200 24611 80.91.229.3 (9 Feb 2013 01:10:00 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 9 Feb 2013 01:10:00 +0000 (UTC) Cc: 13649@debbugs.gnu.org, jidanni@jidanni.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Sat Feb 09 02:10:21 2013 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1U3yxQ-0000qE-4L for geb-bug-gnu-emacs@m.gmane.org; Sat, 09 Feb 2013 02:10:20 +0100 Original-Received: from localhost ([::1]:36139 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1U3yx6-0007mE-OS for geb-bug-gnu-emacs@m.gmane.org; Fri, 08 Feb 2013 20:10:00 -0500 Original-Received: from eggs.gnu.org ([208.118.235.92]:59362) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1U3yx3-0007m0-MV for bug-gnu-emacs@gnu.org; Fri, 08 Feb 2013 20:09:58 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1U3yx2-0004vd-Ad for bug-gnu-emacs@gnu.org; Fri, 08 Feb 2013 20:09:57 -0500 Original-Received: from debbugs.gnu.org ([140.186.70.43]:39551) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1U3yx2-0004vW-6x for bug-gnu-emacs@gnu.org; Fri, 08 Feb 2013 20:09:56 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.72) (envelope-from ) id 1U3yx7-0002Vj-Hd for bug-gnu-emacs@gnu.org; Fri, 08 Feb 2013 20:10:01 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Juri Linkov Original-Sender: debbugs-submit-bounces@debbugs.gnu.org Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sat, 09 Feb 2013 01:10:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 13649 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 13649-submit@debbugs.gnu.org id=B13649.13603721559583 (code B ref 13649); Sat, 09 Feb 2013 01:10:01 +0000 Original-Received: (at 13649) by debbugs.gnu.org; 9 Feb 2013 01:09:15 +0000 Original-Received: from localhost ([127.0.0.1]:45013 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.72) (envelope-from ) id 1U3ywM-0002UV-39 for submit@debbugs.gnu.org; Fri, 08 Feb 2013 20:09:14 -0500 Original-Received: from ps18281.dreamhost.com ([69.163.218.105]:40901 helo=ps18281.dreamhostps.com) by debbugs.gnu.org with esmtp (Exim 4.72) (envelope-from ) id 1U3ywJ-0002UH-7A for 13649@debbugs.gnu.org; Fri, 08 Feb 2013 20:09:12 -0500 Original-Received: from localhost (ps18281.dreamhostps.com [69.163.218.105]) by ps18281.dreamhostps.com (Postfix) with ESMTP id 60F16201D3F820; Fri, 8 Feb 2013 17:09:03 -0800 (PST) In-Reply-To: <83a9re9azb.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 08 Feb 2013 15:44:08 +0200") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (x86_64-pc-linux-gnu) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.13 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x X-Received-From: 140.186.70.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:70921 Archived-At: >> > 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.