[debbugs-tracker] bug#8023: closed (Why can't one run more than one dired-do-async-shell-command at once?)

[GNU bug Tracking System]

Your message dated Sun, 29 Jul 2012 03:04:12 +0300
with message-id <address@hidden>
and subject line Re: bug#4719: 23.1; M-& to run commands asynchronously 
(async-shell-command)
has caused the debbugs.gnu.org bug report #4719,
regarding Why can't one run more than one dired-do-async-shell-command at once?
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
4719: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=4719
GNU Bug Tracking System
Contact address@hidden with problems
> --- Begin Message ---
>
>
>
> 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*'.
>
>
>
>
> --- End Message ---
> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#4719: 23.1;	M-& to run commands asynchronously (async-shell-command)
>
>
>
>
> Date: 
>
> Sun, 29 Jul 2012 03:04:12 +0300
>
>
>
>
> User-agent: 
>
> Gnus/5.13 (Gnus v5.13) Emacs/24.1.50 (x86_64-pc-linux-gnu)
>
>
>
>
> >> So I propose a minimal change that just removes the current annoyance
> >> where async-shell-command asks to kill the buffer instead of doing
> >> something more constructive like creating a new buffer for running
> >> another asynchronous command.
> >>
> >> This is implemented in the patch below.
> >
> > Patch looks fine to me.
>
> Installed and closed.
>
>
> --- End Message ---