From: Harald van Dijk <harald@gigawatt.nl>
To: Trek <trek00@inbox.ru>, dash@vger.kernel.org
Subject: Re: echo do not print NUL byte
Date: Wed, 20 Jan 2016 23:32:11 +0100 [thread overview]
Message-ID: <56A00AEB.5090606@gigawatt.nl> (raw)
In-Reply-To: <20160120223850.25cdf852@enterprise>
Hi,
On 20/01/2016 22:38, Trek wrote:
> there is no way to print the NUL byte with the echo utility
>
> with dash (XSI, no -e argument):
>
> $ dash -c 'echo \\0 | od -An -c'
> \n
This is https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=379227, which
did get fixed already, but it was after 0.5.8. That should mean it will
be in the next release of dash, but you can check out the sources from
Git if you want to see it now.
Cheers,
Harald van Dijk
next prev parent reply other threads:[~2016-01-21 0:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-20 21:38 echo do not print NUL byte Trek
2016-01-20 22:19 ` Eric Blake
2016-01-20 22:32 ` Harald van Dijk [this message]
2016-01-21 1:40 ` Trek
2016-01-21 7:18 ` Bastian Bittorf
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=56A00AEB.5090606@gigawatt.nl \
--to=harald@gigawatt.nl \
--cc=dash@vger.kernel.org \
--cc=trek00@inbox.ru \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox