Re: read command and ascii null as delimiter

Chet Ramey wrote: "Nathan Coulter" <[EMAIL PROTECTED]> writes: read -d $'\0' will do most of what you want, with one limitation. The This is actually equivalent to read -d ''. So, to recap, the way to read null-delimited data is: printf 'hello\0there' | { while read

Re: pwd isn't being updated when moved

Eddie wrote: > Machine: i686 > OS: linux-gnu > Compiler: gcc > Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i686' > -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i686-redhat-linux-gnu' > -DCONF_VENDOR='redhat' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='bash' > -DSHELL -DHAVE_CONFIG_H -I. -

Re: read command and ascii null as delimiter

> "Nathan Coulter" <[EMAIL PROTECTED]> writes: > > >> read -d $'\0' will do most of what you want, with one limitation. The > > > This is actually equivalent to read -d ''. Yes, it is, but it makes the point more clearly. Chet -- ``The lyf so short, the craft so long to le

Re: read command and ascii null as delimiter

"Nathan Coulter" <[EMAIL PROTECTED]> writes: >> read -d $'\0' will do most of what you want, with one limitation. The This is actually equivalent to read -d ''. > This doesn't seem be available in my version. Is it a newer feature? > > $bash --version > GNU bash, version 2.0

Re: read command and ascii null as delimiter

> From: Chet Ramey <[EMAIL PROTECTED]> > Subject: Re: read command and ascii null as delimiter > Sent: 2006-09-08 08:49 > > Nathan Coulter wrote: > > Feature request: an option, maybe "-0" to use ascii null as the delimiter > for the "read" command. It would make the following two command

pwd isn't being updated when moved

Machine: i686 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i686' -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i686-redhat-linux-gnu' -DCONF_VENDOR='redhat' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='bash' -DSHELL -DHAVE_CONFIG_H -I. -I. -I./include -I./lib

Re: typo in test cases

walter harms wrote: > hi chet, > > #! > may have unexpected side effects. e.g. i got 'unknown interpreter' while > locating a problem. Such side effects indicate a problem with the test environment. That script, and nearly all of the `.sub' scripts in the bash test directory, is supposed to be r

Re: typo in test cases

hi chet, #! may have unexpected side effects. e.g. i got 'unknown interpreter' while locating a problem. re, wh Chet Ramey wrote: > walter harms wrote: >> hi bash-developer, >> i used the bash test suite to check busybox ash and found >> two possible mistakes in the latest release. > [...