From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: The elements of enlightenment
Date: Mon, 5 Dec 2022 17:34:38 -0800 [thread overview]
Message-ID: <a07a692b-5eaa-3b14-bec5-2225ca1a21cd@eastlink.ca> (raw)
In-Reply-To: <CAH+w=7b43rc8gHkiKD=6bdVkFdW8SFpqY9XBgiCe2gJxsK169w@mail.gmail.com>
On 2022-12-05 16:17, Bart Schaefer wrote:
>
>> $(...) spawns a subshell because stdin/stdout text is passed from one
>> process to another using pipes, and if a process has a pipe to itself
>> it can deadlock trying to read something it hasn't written yet (or
>> write something there isn't room for because not enough has been read
>> yet).
Yeah I remember we discussed it. It doesn't stick because I don't
really understand it. As just now, one can do it the forking way or one
can do it in the one shell, and the later works fine, so the former is
obviously not needed. But, not knowing the guts, I can only make the
most superficial comments. As you say, traffic control could mandate
things that might not be desirable from the point of view of speed.
next prev parent reply other threads:[~2022-12-06 1:35 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-05 15:57 Ray Andrews
2022-12-05 16:24 ` Roman Perepelitsa
2022-12-05 18:30 ` Bart Schaefer
2022-12-05 19:35 ` Ray Andrews
2022-12-05 19:44 ` Bart Schaefer
2022-12-05 19:58 ` Roman Perepelitsa
2022-12-05 21:20 ` Ray Andrews
2022-12-05 21:49 ` Roman Perepelitsa
2022-12-05 23:52 ` Ray Andrews
2022-12-06 0:17 ` Bart Schaefer
2022-12-06 1:34 ` Ray Andrews [this message]
2022-12-06 18:55 ` Roman Perepelitsa
2022-12-06 19:45 ` Bart Schaefer
2022-12-06 20:01 ` Roman Perepelitsa
2022-12-06 20:07 ` Bart Schaefer
2022-12-06 20:22 ` Roman Perepelitsa
2022-12-06 23:52 ` Lawrence Velázquez
2022-12-07 1:04 ` Lawrence Velázquez
2022-12-05 21:49 ` Bart Schaefer
2022-12-05 21:51 ` Bart Schaefer
2022-12-05 22:24 ` Ray Andrews
2022-12-05 23:24 ` Bart Schaefer
2022-12-06 1:47 ` Ray Andrews
2022-12-06 6:39 ` Lawrence Velázquez
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=a07a692b-5eaa-3b14-bec5-2225ca1a21cd@eastlink.ca \
--to=rayandrews@eastlink.ca \
--cc=zsh-users@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).