zsh-workers
 help / color / mirror / code / Atom feed
From: Oliver Kiddle <opk@zsh.org>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: zsh-workers@zsh.org
Subject: Re: [PATCH?] Nofork and removing newlines
Date: Thu, 14 Mar 2024 23:15:47 +0100	[thread overview]
Message-ID: <31438-1710454547.652877@WxhA.vkY6.ljF0> (raw)
In-Reply-To: <CAH+w=7aFbL8c=RLcrkKJU4R-o2ZhNJgS+zi60STswpFbE4BWqg@mail.gmail.com>

Bart Schaefer wrote:
> like ${|REPLY=...} when of course piping to "read" etc. are also valid
> ways to assign to REPLY.  How often would there be a command name with
> no arguments in that position?

Probably not all that often.

> I hesitate in suggesting this, but ... is there any existing case in
> which "${{" is valid?  If not, I think I can change ${|var|...} to be
> ${{var}...} without too much violence (except to the doc, bleah).

Inner `$' in nested parameter expansions are fairly superfluous in
general. ${|var|...} is closer to the REPLY default with ${|...} but
other than that, I marginally prefer ${{var}...}
Certainly if it does involve much violence, what we currently have is
working.

> > That might look like a default value assignment to someone
>
> Would ${{=var}...} look better?  The doubled braces do give me pause.

Not as good as ${={var}...} but probably better.

> This is the code diff to make emulation trim all, ${ ... } trim one,
> "${ ... }" trim none ... not re-doing the doc diff yet.

Looks good to me.

Oliver


  reply	other threads:[~2024-03-14 22:16 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-05  5:52 Bart Schaefer
2024-03-05  6:56 ` Stephane Chazelas
2024-03-05 22:48   ` Bart Schaefer
2024-03-06 17:57     ` Stephane Chazelas
2024-03-06 19:45       ` Bart Schaefer
2024-03-06 22:22         ` Mikael Magnusson
2024-03-06 22:42           ` Bart Schaefer
2024-03-07  4:53           ` Bart Schaefer
2024-03-07  7:02             ` Lawrence Velázquez
2024-03-07  8:09               ` ${<file} (Was: [PATCH?] Nofork and removing newlines) Stephane Chazelas
2024-03-08  1:29               ` [PATCH?] Nofork and removing newlines Bart Schaefer
2024-03-08 22:15                 ` Oliver Kiddle
2024-03-08 23:28                   ` Bart Schaefer
2024-03-09 20:43                     ` Oliver Kiddle
2024-03-10  6:11                       ` Bart Schaefer
2024-03-12 17:54                         ` Bart Schaefer
2024-03-12 23:19                           ` Oliver Kiddle
2024-03-13  4:13                             ` Bart Schaefer
2024-03-14 22:15                               ` Oliver Kiddle [this message]
2024-03-15  8:42                                 ` Stephane Chazelas
2024-03-27  1:16                                   ` Bart Schaefer
2024-03-27  7:05                                 ` Bart Schaefer
2024-03-07  7:10             ` Stephane Chazelas
2024-03-08  0:37               ` Bart Schaefer
2024-03-07  6:52           ` Lawrence Velázquez
2024-03-07  8:26             ` Mikael Magnusson
2024-03-07 19:02               ` Bart Schaefer
2024-04-02  6:45                 ` Lawrence Velázquez
2024-03-06 19:43     ` Stephane Chazelas

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=31438-1710454547.652877@WxhA.vkY6.ljF0 \
    --to=opk@zsh.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).