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#8023: Why can't one run more than one dired-do-async-shell-command at once? Date: Sat, 12 Feb 2011 18:12:29 +0200 Organization: JURTA Message-ID: <87mxm16xle.fsf@mail.jurta.org> References: <87mxm1sd77.fsf@jidanni.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: dough.gmane.org 1297528667 16905 80.91.229.12 (12 Feb 2011 16:37:47 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Sat, 12 Feb 2011 16:37:47 +0000 (UTC) Cc: 8023@debbugs.gnu.org To: jidanni@jidanni.org Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Sat Feb 12 17:37:43 2011 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1PoITd-0004qz-L9 for geb-bug-gnu-emacs@m.gmane.org; Sat, 12 Feb 2011 17:37:42 +0100 Original-Received: from localhost ([127.0.0.1]:46997 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PoITc-0005Qc-HF for geb-bug-gnu-emacs@m.gmane.org; Sat, 12 Feb 2011 11:37:40 -0500 Original-Received: from [140.186.70.92] (port=34876 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PoISN-0005HZ-J5 for bug-gnu-emacs@gnu.org; Sat, 12 Feb 2011 11:37:33 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PoISL-0001Dg-8A for bug-gnu-emacs@gnu.org; Sat, 12 Feb 2011 11:36:21 -0500 Original-Received: from debbugs.gnu.org ([140.186.70.43]:37467) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PoISL-0001Dc-6j for bug-gnu-emacs@gnu.org; Sat, 12 Feb 2011 11:36:21 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.69) (envelope-from ) id 1PoI0w-0004UU-Ur; Sat, 12 Feb 2011 11:08:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Juri Linkov Original-Sender: debbugs-submit-bounces@debbugs.gnu.org Resent-To: owner@debbugs.gnu.org Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sat, 12 Feb 2011 16:08:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 8023 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 8023-submit@debbugs.gnu.org id=B8023.129752687017239 (code B ref 8023); Sat, 12 Feb 2011 16:08:02 +0000 Original-Received: (at 8023) by debbugs.gnu.org; 12 Feb 2011 16:07:50 +0000 Original-Received: from localhost ([127.0.0.1] helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1PoI0j-0004U0-T1 for submit@debbugs.gnu.org; Sat, 12 Feb 2011 11:07:50 -0500 Original-Received: from smarty.dreamhost.com ([208.113.175.8]) by debbugs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1PoI0i-0004Tc-Al for 8023@debbugs.gnu.org; Sat, 12 Feb 2011 11:07:48 -0500 Original-Received: from ps18281.dreamhostps.com (ps18281.dreamhost.com [69.163.218.105]) by smarty.dreamhost.com (Postfix) with ESMTP id B4C8C6E805E; Sat, 12 Feb 2011 08:16:40 -0800 (PST) Original-Received: from localhost (ps18281.dreamhostps.com [69.163.218.105]) by ps18281.dreamhostps.com (Postfix) with ESMTP id B7872451C16C; Sat, 12 Feb 2011 08:16:39 -0800 (PST) In-Reply-To: <87mxm1sd77.fsf@jidanni.org> (jidanni@jidanni.org's message of "Sat, 12 Feb 2011 19:29:48 +0800") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (x86_64-pc-linux-gnu) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.11 Precedence: list Resent-Date: Sat, 12 Feb 2011 11:08:02 -0500 X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3) 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: , Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:44066 Archived-At: > Why can't one run more than one dired-do-async-shell-command at the same > time? > > Why not allow more than one? > > shell-command: Shell command in progress > > What if bash was also that way? > > If it is a matter of what buffers it is writing to, then append their > names with <2> etc. or a process ID. We have planned to add an option to control the creation of multiple output buffers for `async-shell-command'. The question is in its default value. Maybe it should ask a question: "Create a new buffer?" Or better would be to ask for a new buffer name: Async shell buffer (default *Async shell*<2>): like `C-u M-x shell RET' already does: Shell buffer (default *shell*<2>):