Re: feature request: -0 option for tr

[Craig Sanders]

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 argument three times and it's as cretinous
the fourth time as it was the first three.  it's even more annoying to hear
it again almost two days after i gave up the lost cause of getting anybody
to actually give a damn about implementing a useful feature.

but the really annoying thing about the argument is that it has nothing
to do with my proposed feature.  FILENAMES WITH NEWLINES ARE EXPLICITLY
OUT OF THE FUCKING SCOPE OF THE REQUEST SO HARPING ON ABOUT THEM NOT
BEING CATERED TO IS CRIMINALLY FUCKING STUPID.

is that in simple enough terms for you to understand?

if you're too lazy or indifferent to implement a feature then have the
guts to say so - as volunteers you have every right to say "I don't want
to do that" - but don't make up lame bullshit excuses.


> Where no file names contain newlines, the measure is not necessary
> anyway.

actually, it is because the proposal wasn't about translating newlines
in filenames.  it was about changing the termination character from newline
to null to make the input suitable for use with 'xargs -0' 

i would have thought it was obvious that newlines aren't the concern
here, and never were. the point of using null terminated strings for
input to xargs is to avoid problems with spaces and other punctuation
characters.

now fuck off and quit bothering me. i've wasted enough of my time on you
losers.

craig

-- 
craig sanders <address@hidden>