zsh-users
 help / color / mirror / code / Atom feed
From: "Lawrence Velázquez" <larryv@zsh.org>
To: "Roman Perepelitsa" <roman.perepelitsa@gmail.com>
Cc: zsh-users@zsh.org
Subject: Re: The elements of enlightenment
Date: Tue, 06 Dec 2022 18:52:44 -0500	[thread overview]
Message-ID: <21586f92-9a78-419c-84e5-f203a6f069b6@app.fastmail.com> (raw)
In-Reply-To: <CAN=4vMp_LqvioJE_uW2_CwJ7CKL2dVwGn-6LMonPf_5pfngkzA@mail.gmail.com>

On Tue, Dec 6, 2022, at 1:55 PM, Roman Perepelitsa wrote:
> That said, it's totally possible to extend zsh with something like $[
> ... ] which would work like $( ... ) but without forking. It would run
> the commands in another thread within the same process.

FWIW, ksh has a ${ list;} construct that avoids a subshell:

	$ cd / && pwd
	/
	$ : "${ cd /tmp;}" && pwd
	/tmp
	$ : "${ cd /usr }" && pwd
	/usr

Amusingly, the archaic $[...] is still used for arithmetic expansion.
It's even documented!  (Other shells have memory-holed it.)

-- 
vq


  parent reply	other threads:[~2022-12-06 23:55 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
2022-12-06 23:52               ` Lawrence Velázquez [this message]
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=21586f92-9a78-419c-84e5-f203a6f069b6@app.fastmail.com \
    --to=larryv@zsh.org \
    --cc=roman.perepelitsa@gmail.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).