Sage has poor support for filenames that contain a space.  For
example, if you type `mkdir a\ e', which will create a directory named
"a e" in bash, SAGE provides the not-so-friendly error:

sage: mkdir a\ e
sh: -c: line 0: syntax error near unexpected token `('
sh: -c: line 0: `LD_LIBRARY_PATH=$SAGE_ORIG_LD_LIBRARY_PATH;mkdir
a._backslash_( e)'

You must type `mkdir "a e"'.  This is even more confusing with cd.  If
you have a directory named "banana float" and then type `cd banana'
and hit tab, sage will complete the command as follows:

sage: cd banana
sage: cd banana\ float

However, this command will once again only produce whine:

sage: cd banana\ float
[Errno 2] No such file or directory: 'banana._backslash_( float)'
/home/michael

You may type `cd banana float' or `cd "banana float"', even though
this is not what sage's autocompletion suggests.  There are also
errors when cd-ing to a directory that contains a number in its name.

sage: cd sage-3.0/
[Errno 2] No such file or directory: 'sage-RealNumber(3.0)/'
/opt

Sage will, however, still autocomplete without quotes.

--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/sage-support
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---

Reply via email to