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: Sun, 10 Feb 2013 15:52:43 +0200 Organization: JURTA Message-ID: <87k3qgl1hw.fsf@mail.jurta.org> References: <87zjzcmqkb.fsf@mail.jurta.org> <87halks3r3.fsf@jidanni.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1360504494 2679 80.91.229.3 (10 Feb 2013 13:54:54 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 10 Feb 2013 13:54:54 +0000 (UTC) Cc: 13649@debbugs.gnu.org To: jidanni@jidanni.org Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Sun Feb 10 14:55:15 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 1U4XNC-0004D7-G6 for geb-bug-gnu-emacs@m.gmane.org; Sun, 10 Feb 2013 14:55:14 +0100 Original-Received: from localhost ([::1]:50826 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1U4XMt-0000iT-65 for geb-bug-gnu-emacs@m.gmane.org; Sun, 10 Feb 2013 08:54:55 -0500 Original-Received: from eggs.gnu.org ([208.118.235.92]:60713) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1U4XMq-0000iO-3b for bug-gnu-emacs@gnu.org; Sun, 10 Feb 2013 08:54:53 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1U4XMo-000738-Pa for bug-gnu-emacs@gnu.org; Sun, 10 Feb 2013 08:54:52 -0500 Original-Received: from debbugs.gnu.org ([140.186.70.43]:42919) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1U4XMo-000731-Me for bug-gnu-emacs@gnu.org; Sun, 10 Feb 2013 08:54:50 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.72) (envelope-from ) id 1U4XN1-0002l0-GZ for bug-gnu-emacs@gnu.org; Sun, 10 Feb 2013 08:55:04 -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: Sun, 10 Feb 2013 13:55:02 +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.136050447410555 (code B ref 13649); Sun, 10 Feb 2013 13:55:02 +0000 Original-Received: (at 13649) by debbugs.gnu.org; 10 Feb 2013 13:54:34 +0000 Original-Received: from localhost ([127.0.0.1]:48383 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.72) (envelope-from ) id 1U4XMX-0002kB-Sr for submit@debbugs.gnu.org; Sun, 10 Feb 2013 08:54:34 -0500 Original-Received: from ps18281.dreamhost.com ([69.163.218.105]:44394 helo=ps18281.dreamhostps.com) by debbugs.gnu.org with esmtp (Exim 4.72) (envelope-from ) id 1U4XMU-0002k3-Fu for 13649@debbugs.gnu.org; Sun, 10 Feb 2013 08:54:31 -0500 Original-Received: from localhost (ps18281.dreamhostps.com [69.163.218.105]) by ps18281.dreamhostps.com (Postfix) with ESMTP id 25249258B92971; Sun, 10 Feb 2013 05:54:13 -0800 (PST) In-Reply-To: <87halks3r3.fsf@jidanni.org> (jidanni@jidanni.org's message of "Sun, 10 Feb 2013 21:22:08 +0800") 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:70997 Archived-At: > You guys are forgetting what the user really wants in the first place. > All he wants to do is do another > $ some_command & > as in the shell. > He is used to doing lots of these without regard if the previous one has > finished yet or not... else what fun would asynchronous be? > > Therefore the wisest thing would be to automatically create > *Async Output of bla gla* (or no word Async) > *Async Output of moo goo* > *Async Output of bla gla<2>* > for him, without bothering him with questions. You can customize `async-shell-command-buffer' to `new-buffer' (labeled "Create a new buffer") that creates new buffers automatically without questions.