From: Peter Stephenson <p.w.stephenson@ntlworld.com>
To: Bart Schaefer <schaefer@brasslantern.com>,
Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: Partial reads in ${ ... } capture
Date: Tue, 3 Oct 2023 09:29:02 +0100 (BST) [thread overview]
Message-ID: <223205032.356097.1696321742153@mail.virginmedia.com> (raw)
In-Reply-To: <CAH+w=7aX03B1mnYPQgm193DXz3Rjpq8iidKFzst7W=2pUfCVaQ@mail.gmail.com>
> On 03/10/2023 01:27 Bart Schaefer <schaefer@brasslantern.com> wrote:
> However, I did want to raise a question: Should this instead return a
> partly-filled buffer on a short read? In which case a different patch
> must be applied.
Without knowing a concrete example, I would say it would be cleaner to
leave it as it is.
pws
prev parent reply other threads:[~2023-10-03 8:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-03 0:27 Bart Schaefer
2023-10-03 8:29 ` Peter Stephenson [this message]
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=223205032.356097.1696321742153@mail.virginmedia.com \
--to=p.w.stephenson@ntlworld.com \
--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).