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

[Rik]

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:

  <http://savannah.gnu.org/bugs/?40989>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/