Difficulty using shell in Ubuntu Linux

[Thomas McGrath III]

Bob,

I am going to be dealing with the problem of spaces in file names  
across platforms and also with the problem of file names being too  
long in my project. Can you summarize what you have figured out (with  
the help you have gotten). Do you have any sample code snippets?  
stacks? or examples?

I tried to follow but got lost somewhere. I know we are talking about  
replacing " " with "\" but where do these work? in unix/mac/win from  
a shell or command line or from REV path tools?


Thanks

Tom


On Feb 21, 2006, at 1:10 PM, Bob Warren wrote:

> Dear Stephen,
>
> Unfortunately, the decision whether to use spaces in folder/file  
> names is something that is generally out of my hands. In Windows,  
> they are used by all and sundry all the time, with absolutely no  
> problem, and of course Linux progressively tries to follow similar  
> standards in order to compete with Windows. Since I am producing  
> software to work on other people's computers rather than my own, I  
> need to take the use of spaces into account.
>
> But have no fear, Dave Cope has been here! His solution of using  
> escape codes (i.e. "\ ") in command lines works like a charm, and  
> in RR programming terms (using REPLACE) it is very simple.
>
> Regards,
> Bob
>
> Stephen Barncard wrote:
>
>> I don't think spaces in filenames or foldernames on any platform  
>> is a good idea.
>> They don't work on my webservers either.
>>
>>  Too many platforms don't like them, especially on networks.  
>> People have gotten used to OS's that clean up after them but  
>> filenames just shouldn't have spaces! I've ingrained myself with  
>> no-space habits for years.  Use underscore in place of spaces.
>> What do you do? Rename all the files with spaces!!
>>
>> sdqb
>>
>>
>>> I now have an explanation as to why the shell in (Ubuntu) Linux  
>>> seems to work sometimes, but not others: the HD path to the  
>>> executable for launching MUST NOT CONTAIN BLANKS!
>>>
>>> For example, this works like a charm:
>>>
>>>   global myVar
>>>   put "/home/bob/Desktop/folderwithnospaces/myprog" into myVar
>>>   set the defaultFolder to "/home/bob/Desktop/folderwithnospaces"
>>>   get shell(myVar)
>>>
>>> This doesn't work at all:
>>>
>>>   global myVar
>>>   put "/home/bob/Desktop/folder with spaces/yourprog" into myVar
>>>   set the defaultFolder to "/home/bob/Desktop/folder with spaces"
>>>   get shell(myVar)
>>>
>>> Exactly the same thing applies to the LAUNCH command.
>>>
>>> Now what do I do?
>>> Any ideas anyone?
>>>
>>> Bob
>>>
>>
>
>
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your  
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-revolution

Thomas J McGrath III
3mcgrath at adelphia.net

Lazy River Software™ - http://www.lazyriversoftware.com

Lazy River Metal Art™ - http://www.lazyriversoftware.com/metal.html

Meeting Wear™ - http://www.cafepress.com/meetingwear

Semantic Compaction Systems - http://www.minspeak.com

SCIconics, LLC - http://www.sciconics.com/sciindex.html