On 05/01/08 14:06 +0100, Bram Moolenaar wrote:
An alternative would be to try using NUL characters to separate the
items. Unfortunately I could not find a way to make this work for the
sh of FreeBSD that I'm using. The builtin echo command accepts -n and
-e, but not at the same time. That's
Bram Moolenaar wrote:
[...]
echo is a builtin, printf is a program. I think this means it will
be a bit slower, right? Not sure if this matters.
Also, since printf is a program, isn't there a risk that with some
weird arguments something strange may go wrong?
Why do you put env before
Tony Mechelynck wrote:
Philip Prindeville wrote:
I'm trying to automate building Vim from scratch, but I'm running afoul
of something.
I start by grabbing and unpacking
ftp://ftp.vim.org/pub/vim/unix/vim-7.1.tar.bz2 and then grab
On Jan 6, 2008 9:09 AM, Bram Moolenaar wrote:
We haven't been using printf so far, thus this needs to be tested to
find any system where it doesn't work. The opengroup isn't always
right (I don't think they cover Cygwin).
The cygwin developers regularly reference opengroup man pages on the
On 06/01/08 17:14 -0500, Matt Wozniski wrote:
So, there ought to be no problems with
for i in *; do
printf %s\0 $i
done
Hmm, I found some tricky stuff this morning, just one
$ printf %s\0 *
is enough. Tested in freebsd, obsd, linux.
I don't know why and whether it will work on other
