From: Eli Zaretskii <eliz@gnu.org>
To: Tino Calancha <f92capac@gmail.com>
Cc: 23206@debbugs.gnu.org
Subject: bug#23206: 25.0.92; dired-shell-stuff-it: wait until all parallel jobs finish
Date: Mon, 04 Apr 2016 20:25:25 +0300 [thread overview]
Message-ID: <83inzxnv5m.fsf@gnu.org> (raw)
In-Reply-To: <alpine.LRH.2.20.1604040133440.32717@calancha-ilc.kek.jp> (message from Tino Calancha on Mon, 4 Apr 2016 01:38:52 +0900 (JST))
> Date: Mon, 4 Apr 2016 01:38:52 +0900 (JST)
> From: Tino Calancha <f92capac@gmail.com>
> cc: Tino Calancha <f92capac@gmail.com>, 23206@debbugs.gnu.org
>
> Let's assume COMMAND is "du -s"
> and LIST contains the dirs foo bar baz:
> foo is ~ Gb with depth > 1
> and bar and baz are few kB dirs with depth 1.
>
> The effective shell command to run is:
> du -s foo& du -s bar& du -s baz&
>
> This creates a new process PROC in the system.
> PROC returns with the return code of the last command in the list
> (du -s baz): this is a shell feature.
> The output from the remaining jobs is still comming to stdout,
> but is not associated to PROC, which already succeded.
>
> With `dired-do-shell-command', we get all output only if foo
> is the last dir in LIST.
>
> POSIX shells provide the builtin 'wait' to change this behaviour:
> it forces PROC to wait until all background jobs end.
Thanks. This means the fix should only affect systems with a Posix
shell. The stock MS-Windows shells don't have a 'wait' command (and
don't need this fix in the first place, as the problem doesn't exist
on MS-Windows, AFAICS).
Can you modify the patch to do that?
Thanks.
next prev parent reply other threads:[~2016-04-04 17:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-03 13:02 bug#23206: 25.0.92; dired-shell-stuff-it: wait until all parallel jobs finish Tino Calancha
2016-04-03 15:03 ` Eli Zaretskii
2016-04-03 16:38 ` Tino Calancha
2016-04-04 6:20 ` Tino Calancha
2016-04-04 17:25 ` Eli Zaretskii [this message]
2016-04-05 5:24 ` Tino Calancha
2016-04-05 14:59 ` Eli Zaretskii
2016-04-05 15:58 ` Tino Calancha
2016-04-08 14:06 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83inzxnv5m.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=23206@debbugs.gnu.org \
--cc=f92capac@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).