Bob Proulx wrote:
Matthew Woehlke wrote:
Bob Proulx wrote:
Yes. And cursed they are but so it is. :-)
Oh, come on. I know all about the inherent danger, and I still use
spaces in my file names, and probably always will. It's simply easier
for us humans to think that way.
If you couldn't
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Matthew Woehlke on 7/7/2009 5:38 PM:
Hmm, is xargs a GNU extension? Otherwise I'd say non-GNU xargs.
No. POSIX requires it:
http://www.opengroup.org/onlinepubs/9699919799/utilities/xargs.html
However, xargs -d is a GNU extension.
-
On Wed, Jul 1, 2009 at 11:47 AM, Craig Sandersc...@taz.net.au wrote:
On Wed, Jul 01, 2009 at 10:13:15AM +0100, James Youngman wrote:
The essential point though has already been made by Bob and Andreas;
this causes failures for filenames which themselves contain newlines
(all Unix-like
are you to stupid to understand the words fuck off?
i have no interest in arguing with you. or communicating with you in any way.
is it that important to you to revive debate over a proposal i
abandoned three days ago just so your loser ego can have it's two cents
worth?
well, you know where
On Sun, Jun 28, 2009 at 2:20 AM, Craig Sandersc...@taz.net.au wrote:
please add a -0 option to tr, which is equivalent to
running:
tr '\n' '\000'
this is a useful command for converting \n-terminated input lines to
null-terminated strings suitable for feeding into 'xargs -0' as many
On Wed, Jul 01, 2009 at 10:13:15AM +0100, James Youngman wrote:
The essential point though has already been made by Bob and Andreas;
this causes failures for filenames which themselves contain newlines
(all Unix-like filesystems I am familiar with allow this).
i've already heard this stupid
Bob Proulx wrote:
Craig Sanders wrote:
spaces and quote characters and even backslashes in filenames are far
more common, especially on systems were files are uploaded by users from
non-unix systems (e.g. ftp upload to web servers, samba file servers,
etc)
Yes. And cursed they are but so it
Matthew Woehlke wrote:
Bob Proulx wrote:
Yes. And cursed they are but so it is. :-)
Oh, come on. I know all about the inherent danger, and I still use
spaces in my file names, and probably always will. It's simply easier
for us humans to think that way.
If you couldn't tell I was
On Sat, Jun 27, 2009 at 09:26:17PM -0600, Eric Blake wrote:
According to Craig Sanders on 6/27/2009 7:20 PM:
please add a -0 option to tr, which is equivalent to
running:
tr '\n' '\000'
Why should we burn an option letter, when it is not that much more typing
to get what you
Craig Sanders wrote:
Eric Blake wrote:
According to Craig Sanders:
please add a -0 option to tr, which is equivalent to
running:
tr '\n' '\000'
Why should we burn an option letter, when it is not that much more typing
to get what you wanted anyways?
because it's a
Craig Sanders c...@taz.net.au writes:
GNU grep has -z and -Z options - by your reasoning above, these
convenience options are completely unecessary because you can easily
run tr '\0' '\n' before grep and tr '\n' '\0' after grep.
No, you can't. The combination of these two operations is not
On Sun, Jun 28, 2009 at 08:27:20PM +0200, Andreas Schwab wrote:
Craig Sanders c...@taz.net.au writes:
GNU grep has -z and -Z options - by your reasoning above, these
convenience options are completely unecessary because you can easily
run tr '\0' '\n' before grep and tr '\n' '\0' after
please add a -0 option to tr, which is equivalent to
running:
tr '\n' '\000'
this is a useful command for converting \n-terminated input lines to
null-terminated strings suitable for feeding into 'xargs -0' as many
programs can not generate null-terminated ouput by themselves.
it would
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Craig Sanders on 6/27/2009 7:20 PM:
please add a -0 option to tr, which is equivalent to
running:
tr '\n' '\000'
Why should we burn an option letter, when it is not that much more typing
to get what you wanted anyways? An
14 matches
Mail list logo
