[dundee] BashPitfalls

Axel newsletter at axelbor.de
Wed Feb 9 21:42:00 UTC 2011


There is now reason to use a spaces for a file name, is there an  
reason to use other
characters than A-Z0-9_ for a file name?

Anyway, you should not call a piece of code program, which isn't able  
to process a ASCII
character. In circumstance you have to port your program to another  
operation system such as Windows, you have to avoid this or is will be  
crashing. There are directories like "Documents and Settings", which  
contain spaces.

I take the view, both ways are bad. Spaces in file names make working  
with the command line
much complicated and programs which ignore spaces are not reliable in  
their behaviour.

Quoting James Le Cuirot <chewi at aura-online.co.uk>:

> On Wed, 9 Feb 2011 16:25:54 +0000
> Andrew Clayton <andrew at digital-domain.net> wrote:
>
>> > These are some very negative attitudes. I sometimes use spaces for
>> > stuff in my home folder. I certainly use them for my music files.
>> > I
>>
>> Why? Assuming your music is properly tagged (why wouldn't it be?) then
>> spaces serve no purpose.
>
> My music is tagged properly and I must admit, I don't have a good a
> answer for that, but I feel my point still stands. Good coders should
> always take them into account.
>
> James
>
> _______________________________________________
> dundee GNU/Linux Users Group mailing list
> dundee at lists.lug.org.uk  http://dundeelug.org.uk
> https://mailman.lug.org.uk/mailman/listinfo/dundee
> Chat on IRC, #tlug on irc.lug.org.uk
>







More information about the dundee mailing list