From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Tassilo Horn Newsgroups: gmane.emacs.devel Subject: Starting multiple async processes from inside dired using & Date: Sun, 18 Oct 2009 18:15:52 +0200 Message-ID: <87skdgd6fb.fsf@thinkpad.tsdh.de> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1255882579 20428 80.91.229.12 (18 Oct 2009 16:16:19 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 18 Oct 2009 16:16:19 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Oct 18 18:16:11 2009 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1MzYQS-0000tN-Kg for ged-emacs-devel@m.gmane.org; Sun, 18 Oct 2009 18:16:08 +0200 Original-Received: from localhost ([127.0.0.1]:47183 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MzYQR-0003C6-QO for ged-emacs-devel@m.gmane.org; Sun, 18 Oct 2009 12:16:07 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MzYQL-00038h-Hb for emacs-devel@gnu.org; Sun, 18 Oct 2009 12:16:01 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MzYQF-0002xy-Rw for emacs-devel@gnu.org; Sun, 18 Oct 2009 12:16:00 -0400 Original-Received: from [199.232.76.173] (port=38202 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MzYQF-0002xg-Kv for emacs-devel@gnu.org; Sun, 18 Oct 2009 12:15:55 -0400 Original-Received: from out1.smtp.messagingengine.com ([66.111.4.25]:50282) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MzYQF-0008BU-Ep for emacs-devel@gnu.org; Sun, 18 Oct 2009 12:15:55 -0400 Original-Received: from compute2.internal (compute2.internal [10.202.2.42]) by gateway1.messagingengine.com (Postfix) with ESMTP id 18AB6A3DD6 for ; Sun, 18 Oct 2009 12:15:55 -0400 (EDT) Original-Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by compute2.internal (MEProxy); Sun, 18 Oct 2009 12:15:55 -0400 X-Sasl-enc: UEdXAI5wn+cS+5O+ICQyV9J7uKTIUoLeLHh8O88CrFfG 1255882554 Original-Received: from thinkpad.tsdh.de (p54AF00AA.dip0.t-ipconnect.de [84.175.0.170]) by mail.messagingengine.com (Postfix) with ESMTPA id 2BEEAA4FE for ; Sun, 18 Oct 2009 12:15:53 -0400 (EDT) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1.50 (gnu/linux) Mail-Copies-To: never X-detected-operating-system: by monty-python.gnu.org: Genre and OS details not recognized. X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:116226 Archived-At: Hi all, I've just noticed that it's not possible to start multiple asynchronous processes using `shell-command', because they all want to be associated with the one and only "*Async Shell Command*" buffer. This is especially annoying when using dired and its `&' (dired-do-async-shell-command) command. I frequently want to open a file with an external application, and as long as this process is alive, another & will query A command is running. Kill it? (yes or no) where I don't want to kill the former process. As a workaround, I can rename the *Async Shell Command* buffer before starting the second process, but that's quite inconvenient. IMO, the right thing would be to create another *Async Shell Command* buffer, uniquified with the executed command and its pid or something like that. Am I missing something obvious, because it looks to me like some quite normal dired use case? Bye, Tassilo