Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!1.eu.feeder.erje.net!news.swapon.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: Tim Watts <tw_usenet@dionic.net>
Newsgroups: comp.os.linux.misc
Subject: Re: Unnamed documents
Date: Mon, 11 May 2015 21:34:11 +0100
Lines: 21
Message-ID: <3bg72c-vd5.ln1@squidward.dionic.net>
References: <mipv68$got$1@news.albasani.net> <wwvzj5b770g.fsf@l1AntVDjLrnP7Td3DQJ8ynzIq3lJMueXf87AxnpFoA.invalid> <miq29o$mf3$1@news.albasani.net> <mir0t9$miu$1@dont-email.me>
Mime-Version: 1.0
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-Trace: individual.net jCHf3RRz17T0KOz1Wtu0nAjYuDQzNswVPetMkvhfZpBALCp4NE
X-Orig-Path: squidward.dionic.net!not-for-mail
Cancel-Lock: sha1:L7GIwwm58umHcAPmjkftVxzbcaY=
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
In-Reply-To: <mir0t9$miu$1@dont-email.me>
Xref: csiph.com comp.os.linux.misc:14757

On 11/05/15 20:45, William Unruh wrote:
>
> will work. In all cases bash treats the spaces as characters, not
> terminators. (Yes, it is the shell that does that). Note that you could
> also tell the system to use some other character as the word terminator
> if you wanted, but it is not advisable except in unusual circunstances.
> (Not that I can tell you right now how to do that)
>
> Eg in the above you could make : bash's word terminator, and then the
> spaces would be fine.
>

Hmm

rm:-rf:somefile:someotherfile

Or we could just accept that whitespace in filenames are the work of 
Satan and remember what the underscore character is for ;->

Essentially it's all Bill Gates' fault...