help / color / mirror / code / Atom feed
From: Pier Paolo Grassi <pierpaolog@gmail.com>
To: Peter Stephenson <p.w.stephenson@ntlworld.com>
Cc: Zsh-Users List <zsh-users@zsh.org>
Subject: Re: read string containing null
Date: Thu, 21 Oct 2021 15:30:32 +0200	[thread overview]
Message-ID: <CAP+y1xCU0LiFBmrkruDdVFzKNaZp-WMm7iVXTff5j8xUjiiYBQ@mail.gmail.com> (raw)
In-Reply-To: <899710302.733700.1634821721465@mail2.virginmedia.com>

[-- Attachment #1: Type: text/plain, Size: 1021 bytes --]

Yes, I want to read the whole stdin in a single operation, so the -d was
there to disable stopping at newline
It seem that instead made read stop at null bytes
I worked around this limitation with:

xx=$(echo -e - a$'\000'b; echo .); xx=${xx[1,-2]}; echo -n - $xx

but I will try also your suggestion, thanks

Pier Paolo Grassi

Il giorno gio 21 ott 2021 alle ore 15:08 Peter Stephenson <
p.w.stephenson@ntlworld.com> ha scritto:

> > On 21 October 2021 at 13:35 Pier Paolo Grassi <pierpaolog@gmail.com>
> wrote:
> > Hello, I just found out:
> >
> > echo -e - a$'\000'b | IFS='' builtin read -r -d '' xx; echo -n - $xx
> > result is "a"
> >
> > is it possible for builtin read not to stop an null bytes? I found
> nothing
> > in documentation.
> > thanks
> I think -d '' is telling it to treat NULL bytes as a delimiter.  Take that
> out.
> If you're not trying to read a line, don't use read.  If you "zmodload
> zsh/system"
> there's a sysread command which is more useful for lower level operations.
> pws

[-- Attachment #2: Type: text/html, Size: 1965 bytes --]

  reply	other threads:[~2021-10-21 13:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-21 12:35 Pier Paolo Grassi
2021-10-21 13:08 ` Peter Stephenson
2021-10-21 13:30   ` Pier Paolo Grassi [this message]
2021-10-22  9:05   ` Stephane Chazelas
2021-10-23  0:04     ` Bart Schaefer

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAP+y1xCU0LiFBmrkruDdVFzKNaZp-WMm7iVXTff5j8xUjiiYBQ@mail.gmail.com \
    --to=pierpaolog@gmail.com \
    --cc=p.w.stephenson@ntlworld.com \
    --cc=zsh-users@zsh.org \


* 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


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).