GNU bug report logs - #8023
Why can't one run more than one dired-do-async-shell-command at once?

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 8023 in the body.
You can then email your comments to 8023 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: jidanni <at> jidanni.org
To: bug-gnu-emacs <at> gnu.org
Subject: Why can't one run more than one dired-do-async-shell-command at once?
Date: Sat, 12 Feb 2011 19:29:48 +0800

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.

  & runs the command dired-do-async-shell-command, which is an
  interactive compiled Lisp function in `dired-aux.el'.

  It is bound to &, <menu-bar> <operate> <async-command>.

  (dired-do-async-shell-command COMMAND &optional ARG FILE-LIST)

  Run a shell command COMMAND on the marked files asynchronously.

  Like `dired-do-shell-command' but if COMMAND doesn't end in ampersand,
  adds `* &' surrounded by whitespace and executes the command asynchronously.
  The output appears in the buffer `*Async Shell Command*'.

Message #8 received at 8023 <at> debbugs.gnu.org (full text, mbox):

From: Juri Linkov <juri <at> jurta.org>
To: jidanni <at> jidanni.org
Cc: 8023 <at> debbugs.gnu.org
Subject: Re: 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

> 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>):

Message #11 received at 8023 <at> debbugs.gnu.org (full text, mbox):

From: jidanni <at> jidanni.org
To: juri <at> jurta.org
Cc: 8023 <at> debbugs.gnu.org
Subject: Re: bug#8023: Why can't one run more than one
	dired-do-async-shell-command at once?
Date: Tue, 15 Feb 2011 07:45:47 +0800

>>>>> "JL" == Juri Linkov <juri <at> jurta.org> writes:
JL> Async shell buffer (default *Async shell*<2>):
All I know is the user might also have code like
$ grep -i shell .emacs
 shell-command-default-error-buffer "shell-command-errors")
        (shell-command-on-region
	 START END COMMAND t t shell-command-default-error-buffer t)
(add-hook 'shell-mode-hook

etc. as found in http://jidanni.org/comp/configuration/
So there are several buffers involved...

Message #14 received at 8023 <at> debbugs.gnu.org (full text, mbox):

From: Juri Linkov <juri <at> jurta.org>
To: jidanni <at> jidanni.org
Cc: 8023 <at> debbugs.gnu.org
Subject: Re: bug#8023: Why can't one run more than one
	dired-do-async-shell-command at once?
Date: Wed, 16 Feb 2011 02:34:01 +0200

> JL> Async shell buffer (default *Async shell*<2>):
> All I know is the user might also have code like
> $ grep -i shell .emacs
>  shell-command-default-error-buffer "shell-command-errors")
>         (shell-command-on-region
> 	 START END COMMAND t t shell-command-default-error-buffer t)
> (add-hook 'shell-mode-hook
> etc. as found in http://jidanni.org/comp/configuration/
> So there are several buffers involved...

Processing of the new option will be added to `shell-command',
so it won't interfere with buffers as its input arguments.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.