From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Juri Linkov Newsgroups: gmane.emacs.devel Subject: Re: Starting multiple async processes from inside dired using & Date: Mon, 19 Oct 2009 01:05:17 +0300 Organization: JURTA Message-ID: <873a5g4axm.fsf@mail.jurta.org> References: <87skdgd6fb.fsf@thinkpad.tsdh.de> <87skdgbfsm.fsf@stupidchicken.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1255903764 13644 80.91.229.12 (18 Oct 2009 22:09:24 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 18 Oct 2009 22:09:24 +0000 (UTC) Cc: emacs-devel@gnu.org To: Chong Yidong Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Oct 19 00:09:13 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 1Mzdw7-0004JV-Bw for ged-emacs-devel@m.gmane.org; Mon, 19 Oct 2009 00:09:11 +0200 Original-Received: from localhost ([127.0.0.1]:53667 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Mzdw3-0003PG-SQ for ged-emacs-devel@m.gmane.org; Sun, 18 Oct 2009 18:09:07 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Mzdvy-0003N6-38 for emacs-devel@gnu.org; Sun, 18 Oct 2009 18:09:02 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Mzdvs-0003Ga-R0 for emacs-devel@gnu.org; Sun, 18 Oct 2009 18:09:01 -0400 Original-Received: from [199.232.76.173] (port=38534 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Mzdvs-0003GT-LG for emacs-devel@gnu.org; Sun, 18 Oct 2009 18:08:56 -0400 Original-Received: from smtp-out1.starman.ee ([85.253.0.3]:54376 helo=mx1.starman.ee) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Mzdvs-0005Sj-8Z for emacs-devel@gnu.org; Sun, 18 Oct 2009 18:08:56 -0400 X-Virus-Scanned: by Amavisd-New at mx1.starman.ee Original-Received: from mail.starman.ee (82.131.98.217.cable.starman.ee [82.131.98.217]) by mx1.starman.ee (Postfix) with ESMTP id 030123F4129; Mon, 19 Oct 2009 01:08:48 +0300 (EEST) In-Reply-To: <87skdgbfsm.fsf@stupidchicken.com> (Chong Yidong's message of "Sun, 18 Oct 2009 16:36:25 -0400") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1.50 (x86_64-pc-linux-gnu) X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6, seldom 2.4 (older, 4) 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:116229 Archived-At: >> 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? > > The only problem I can see is that these buffers will proliferate if you > execute lots of async commands over the course of a session. Yes, this is a real problem. I've tried for some time using a patch that creates a new *Async Shell Command* buffer for every async process and it ends up collecting a lot of dead *Async Shell Command* buffers. > So instead of uniquifying, the code first needs to search for an > *Async Shell Command XXX* buffer containing a dead process, and only > uniquify if no such buffer exists. It seems the best option is to search and revive an existing buffer, but there is another problem: the user might want to keep the output of an old *Async Shell Command* buffer and not overwrite it with the output of another process. -- Juri Linkov http://www.jurta.org/emacs/