Davy Durham <[EMAIL PROTECTED]> wrote:
> I was wondering if it's possible to make the build-in 'read' command
> not always stop at ascii 0.
Shell variable values are null-terminated; they can't hold internal
nulls. Even if bash were changed, it's still not possible to pass
such values as argume
On Tue, Mar 08, 2005 at 03:26:37PM -0600, Davy Durham wrote:
> Hey,
> I was wondering if it's possible to make the build-in 'read' command
> not always stop at ascii 0.
>
> I've got a file "foo" with "asdf\0qwer\n" in it and when I do:
> read x < foo
> then
> echo ${#x}
> always returns 4 in
Hey,
I was wondering if it's possible to make the build-in 'read' command
not always stop at ascii 0.
I've got a file "foo" with "asdf\0qwer\n" in it and when I do:
read x < foo
then
echo ${#x}
always returns 4 instead of 9 or 10 because it stopped after "asdf" at
the null char
I've played
