zsh-users
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: Roman Perepelitsa <roman.perepelitsa@gmail.com>
Cc: Mikael Magnusson <mikachu@gmail.com>, Eric Cook <llua@gmx.com>,
	zsh-users@zsh.org
Subject: Re: Bug/regression: tt(RANDOM) seed not updating when $RANDOM is used in a pipe
Date: Thu, 29 Jun 2023 16:41:21 -0700	[thread overview]
Message-ID: <CAH+w=7b32beE6v_rAXHJ5sV0SUNdS==+HkCUr8nJaTHmqxY=qw@mail.gmail.com> (raw)
In-Reply-To: <CAN=4vMoMnDFhgH7nZAUGg27g0tieFGEaAhLx1DGi70xqHoroKA@mail.gmail.com>

On Thu, Jun 29, 2023 at 11:16 AM Roman Perepelitsa
<roman.perepelitsa@gmail.com> wrote:
>
> > On 6/29/23, Roman Perepelitsa <roman.perepelitsa@gmail.com> wrote:
> > >
> > >     % echo ${foo::=bar} | cat
> > >     % zmodload zsh/system; echo $sysparams[pid] | cat
> > >
>
> I can also confirm that the two test cases I posted above behave
> differently in zsh 5.4.2 and 5.9. In all these cases 5.9 behaves as I
> would expect, and the behavior of 5.4.2 is surprising to me.

The change that had this effect dates from May 2018 and has been "in
production" since the 5.6 release in September 2018, so I think it's
reasonable to say that it hasn't had any significant impact on usage
-- MacOS Catalina has zsh 5.7, Ubuntu 20.04 has 5.8 -- but it's
probably worth mentioning somewhere.


  reply	other threads:[~2023-06-29 23:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-28 20:10 Jon Oster
2023-06-29  2:46 ` Eric Cook
2023-06-29  5:42   ` Bart Schaefer
2023-06-29 14:41     ` Ray Andrews
2023-06-29 14:56     ` Roman Perepelitsa
2023-06-29 17:53       ` Mikael Magnusson
2023-06-29 18:15         ` Roman Perepelitsa
2023-06-29 23:41           ` Bart Schaefer [this message]
2023-07-02  7:17 ` Mikael Magnusson
2023-07-02  7:29   ` Roman Perepelitsa

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='CAH+w=7b32beE6v_rAXHJ5sV0SUNdS==+HkCUr8nJaTHmqxY=qw@mail.gmail.com' \
    --to=schaefer@brasslantern.com \
    --cc=llua@gmx.com \
    --cc=mikachu@gmail.com \
    --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).