Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #11910
| From | Linda Walsh <bash@tlinx.org> |
|---|---|
| Newsgroups | gnu.bash.bug |
| Subject | Re: redirecting a file descriptor to an array variable? Possible? How? RFE? |
| Date | 2015-11-18 12:29 -0800 |
| Message-ID | <mailman.181.1447878567.31583.bug-bash@gnu.org> (permalink) |
| References | <564532BD.60801@tlinx.org> <CAJnmqwbeSXYrNF6zEJ9nEx2Zyi23X9fxLvkkc1HFOh7JkqZUsw@mail.gmail.com> <564CC7A1.9090004@tlinx.org> <20151118185629.GJ27325@eeg.ccf.org> |
Greg Wooledge wrote: > On Wed, Nov 18, 2015 at 10:46:57AM -0800, Linda Walsh wrote: >> One thing that seems to be another problem. Greg called >> my attention to another printf format bug: >> >> %q causes printf to output the corresponding argument in >> a >> format that can be reused as shell input. >> >> Which it doesn't when nuls are involved. > > An argument cannot contain a NUL byte. So it's moot. --- As in: > printf '"%c"\n' $'\x00'|hexdump -C 00000000 22 00 22 0a |".".| I see 2 arguments being passed to printf. That puts the NUL byte between 2 double quotes and terminates the line w/a newline. What I'm pointing out is that a NUL byte can be used and processed as an argument in some cases. The fact that it doesn't work in most places, I will agree, is a short-coming. However one cannot categorically say that a NUL byte can't be used as an argument. Solving other places where it doesn't work might make it so that it *would* work... Maybe a "-b" (binary) option could be added to 'declare'?
Back to gnu.bash.bug | Previous | Next | Find similar
Re: redirecting a file descriptor to an array variable? Possible? How? RFE? Linda Walsh <bash@tlinx.org> - 2015-11-18 12:29 -0800
csiph-web