[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #40989] ls fails if blank spaces exist in file

From: Rik
Subject: [Octave-bug-tracker] [bug #40989] ls fails if blank spaces exist in filepath
Date: Thu, 02 Jan 2014 19:46:04 +0000
User-agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:26.0) Gecko/20100101 Firefox/26.0

Update of bug #40989 (project octave):

                  Status:                   Fixed => In Progress            
             Open/Closed:                  Closed => Open                   


Follow-up Comment #7:

There is a problem with cset 05a53cc522b7
(http://hg.savannah.gnu.org/hgweb/octave/rev/05a53cc522b7) so I am re-opening
the bug.  The patch wraps all non-options in double quote characters. 
However, following the wrapping there is a regexprep call which escapes all
non-word characters like the double quote character.  This makes ls unusuable
whenever you have an actual file name.  See the following example:

ls /home
ls: cannot access "/home": No such file or directory
error: ls: command exited abnormally with status 2

You might get away with modifying the regexprep to not include double quotes
on line 80 of ls.m

args = regexprep (args, '([^\w.*? -])', '\\$1');


args = regexprep (args, '([^\w.*? -"])', '\\$1');

But I haven't thought through all of the implications.


Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]