From: Stephane Chazelas <stephane@chazelas.org>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: Suggested changes to Etc/FAQ
Date: Sat, 11 Nov 2023 11:59:57 +0000 [thread overview]
Message-ID: <f8bb79a00979fa637feb4666da703888@chazelas.org> (raw)
In-Reply-To: <CAH+w=7ZOc-yXfGyu9K1Bj0k-o0T_Z3ftsq8pxpu8m3HD3t7Bew@mail.gmail.com>
On 2023-11-11 05:10, Bart Schaefer wrote:
> @@ -497,8 +504,9 @@ tt(RM_STAR_SILENT),
> it() Coprocesses are established by mytt(coproc); mytt(|&)
> behaves like
> csh. Handling of coprocess file descriptors is also
> different.
> it() In mytt(cmd1 && cmd2 &), only mytt(cmd2) instead of the
> whole
> - expression is run in the background in zsh. The manual
> implies
> - this is a bug. Use mytt({ cmd1 && cmd2 } &) as a workaround.
> + expression is run in the background in zsh. In versions
> beginning
> + with 5.9, the whole expression is backgrounded during sh emulation.
> + Use mytt({ cmd1 && cmd2 } &) as a workaround in zsh native mode.
> )
> it() Command line substitutions, globbing etc.:
> itemization(
Unless I'm misunderstanding that statement, that's not what I observe
here with zsh 5.9 from the Debian package, nor in the current git HEAD:
$ zsh --emulate sh -c 'sleep 2 && sleep 3 & echo $SECONDS'
2
$ ./Src/zsh --emulate sh -c 'sleep 2 && sleep 3 & echo $SECONDS'
2
$ zsh --version
zsh 5.9 (x86_64-debian-linux-gnu)
$ ./Src/zsh --version
zsh 5.9.0.1-dev (x86_64-pc-linux-gnu)
$ git describe
zsh-5.9-308-gd8a3bff4f
See also
https://unix.stackexchange.com/questions/761128/run-two-scripts-after-each-other-in-the-background-and-dont-work/761132#761132
--
Stephane
next prev parent reply other threads:[~2023-11-11 12:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-11 5:10 Bart Schaefer
2023-11-11 11:59 ` Stephane Chazelas [this message]
2023-11-11 21:51 ` Bart Schaefer
2023-11-13 7:13 ` Stephane Chazelas
2023-11-13 14:18 ` Peter Stephenson
2023-11-16 2:32 ` Bart Schaefer
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f8bb79a00979fa637feb4666da703888@chazelas.org \
--to=stephane@chazelas.org \
--cc=schaefer@brasslantern.com \
--cc=zsh-workers@zsh.org \
/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.vuxu.org/mirror/zsh/
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 NNTP newsgroup(s).