Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: The elements of enlightenment
- X-seq: zsh-users 28512
- From: Roman Perepelitsa <roman.perepelitsa@xxxxxxxxx>
- To: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- Cc: Ray Andrews <rayandrews@xxxxxxxxxxx>, zsh-users@xxxxxxx
- Subject: Re: The elements of enlightenment
- Date: Tue, 6 Dec 2022 21:22:38 +0100
- Archived-at: <https://zsh.org/users/28512>
- In-reply-to: <CAH+w=7Y9gt2h853qnB9Pc0thKcsS93U0GkhN1mzXXoG0cmL9+w@mail.gmail.com>
- List-id: <zsh-users.zsh.org>
- References: <54bcd6dd-e589-4696-f042-1155b78df9d2@eastlink.ca> <CAN=4vMp2r4Syu-CuF=gxed5om9JQ+NDQm6LvNZRBE4d5a4v1xw@mail.gmail.com> <819c9630-f315-8b1c-cb52-3d3ae8de2d5c@eastlink.ca> <CAN=4vMqKXudgwwQAPNzJ0OymhYWwPWu+ec+LyiVK2nhDP1jbeg@mail.gmail.com> <7eadf163-da34-d90b-61ce-b527fb75b597@eastlink.ca> <CAN=4vMq7=BGygpKU4ed_b33tdE0NGoCALZdaF10hz0co4zqksQ@mail.gmail.com> <37b2456f-0459-4b85-74d1-bb380715e2ed@eastlink.ca> <CAN=4vMp_LqvioJE_uW2_CwJ7CKL2dVwGn-6LMonPf_5pfngkzA@mail.gmail.com> <CAH+w=7ZNaobKgabqiCJb4VGwRGN0xfzG=RHtuUFMzf=Y8YQTkw@mail.gmail.com> <CAN=4vMoq7p51C7VE6sAniq3CgFEJ8qLGYf4pP+hz5DtKwMNJNQ@mail.gmail.com> <CAH+w=7Y9gt2h853qnB9Pc0thKcsS93U0GkhN1mzXXoG0cmL9+w@mail.gmail.com>
On Tue, Dec 6, 2022 at 9:07 PM Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx> wrote:
>
> On Tue, Dec 6, 2022 at 12:01 PM Roman Perepelitsa
> <roman.perepelitsa@xxxxxxxxx> 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.
Messages sorted by:
Reverse Date,
Date,
Thread,
Author