zsh-workers
 help / color / mirror / code / Atom feed
From: Mikael Magnusson <mikachu@gmail.com>
To: dana <dana@dana.is>
Cc: Bart Schaefer <schaefer@brasslantern.com>,
	Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: [PATCH] Change documentation, dedication, loose ends
Date: Sun, 3 Apr 2022 22:59:27 +0200	[thread overview]
Message-ID: <CAHYJk3S6p4XkMSLj4ZV=fWPyVc+QpKns=Lg0D+2n7BN7ayZ+5A@mail.gmail.com> (raw)
In-Reply-To: <0b4be90c-53b0-4764-83b0-269ebfddbdd2@www.fastmail.com>

On 4/3/22, dana <dana@dana.is> wrote:
> On Sun 3 Apr 2022, at 11:34, Bart Schaefer wrote:
>> If we're adding a sections specifically for 5.8.1, should the
>> line-buffering bug be mentioned?
>
> Is there a behaviour change there? I thought it was just a crash fix

When reading commands from stdin, we would read too much before
starting to run them:
# git master (second line is read by python)
% print -l python2 'print "%s"%"hi"' | zsh
hi
# git master with 1640457f475 reverted
# zsh consumes all input, python does nothing, exits, then we run the
2nd line as zsh code
% print -l python2 'print "%s"%"hi"' | Src/zsh
%s%hi

See also "0:Non-interactive shell command input is line buffered" in
A01 added in that commit.

-- 
Mikael Magnusson


  reply	other threads:[~2022-04-03 21:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-03  3:29 dana
2022-04-03  9:23 ` PATCH: _brace_parameter: add (-) Mikael Magnusson
2022-04-03 21:13   ` Mikael Magnusson
2022-04-03 16:34 ` [PATCH] Change documentation, dedication, loose ends Bart Schaefer
2022-04-03 19:18   ` dana
2022-04-03 20:59     ` Mikael Magnusson [this message]
2022-04-08 19:29       ` dana
2022-04-10 21:20         ` Daniel Shahaf

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='CAHYJk3S6p4XkMSLj4ZV=fWPyVc+QpKns=Lg0D+2n7BN7ayZ+5A@mail.gmail.com' \
    --to=mikachu@gmail.com \
    --cc=dana@dana.is \
    --cc=schaefer@brasslantern.com \
    --cc=zsh-workers@zsh.org \
    --subject='Re: [PATCH] Change documentation, dedication, loose ends' \
    /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

Code repositories for project(s) associated with this 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).