From: Roman Perepelitsa <roman.perepelitsa@gmail.com>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: Ray Andrews <rayandrews@eastlink.ca>, zsh-users@zsh.org
Subject: Re: The elements of enlightenment
Date: Tue, 6 Dec 2022 21:22:38 +0100 [thread overview]
Message-ID: <CAN=4vMraqPmKDj=xACzBcyRkQD19iSbgGEPbQs0f3=z4gknVSA@mail.gmail.com> (raw)
In-Reply-To: <CAH+w=7Y9gt2h853qnB9Pc0thKcsS93U0GkhN1mzXXoG0cmL9+w@mail.gmail.com>
On Tue, Dec 6, 2022 at 9:07 PM Bart Schaefer <schaefer@brasslantern.com> wrote:
>
> On Tue, Dec 6, 2022 at 12:01 PM Roman Perepelitsa
> <roman.perepelitsa@gmail.com> wrote:
> >
> > Yeah, it's probably non-trivial. Thankfully, it wouldn't require
> > inserting mutex locks in random places because the parent shell will
> > never be executing concurrently with the child.
>
> I generally hate slippery-slope arguments, but ... as soon as we have
> $[...], someone is going to want "coproc" and <(...) threads too.
And `&` for threads obviously. Yeah, any of those are very difficult.
In practice I don't think $[ .. ] would be super useful. One can use
`printf -v` instead of $(printf) and the same applies to pretty much
all instances of invoking a builtin and capturing its stdout: there is
always a way to get the same data without printing it. I know of only
one exception. To the best of my knowledge, the only way to get
keybindings is to invoke bindkey and capture stdout.
Roman.
next prev parent reply other threads:[~2022-12-06 20:23 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
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 [this message]
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='CAN=4vMraqPmKDj=xACzBcyRkQD19iSbgGEPbQs0f3=z4gknVSA@mail.gmail.com' \
--to=roman.perepelitsa@gmail.com \
--cc=rayandrews@eastlink.ca \
--cc=schaefer@brasslantern.com \
--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).