[Octave-bug-tracker] [bug #62282] ls command in 7.1.0 may not function

[Markus Mützel]

Follow-up Comment #26, bug #62282 (project octave):

Let's quote the part of the documentation for `ls` about glob patterns to be
able to dissect it here:
>     Filenames are subject to shell expansion if they contain any
>     wildcard characters '*', '?', '[]'.  To find a literal example of a
>     wildcard character the wildcard must be escaped using the backslash
>     operator '\'.

Maybe, I'm misunderstanding. But I'd understand that this means that '*', '?',
and characters between braces '[]' are treated as glob patterns. If any of
these characters are escaped with a backslash (I don't know why it is called
"operator" here), they are treated as literals instead.

If you are executing `ls
C:\Octave\Octave-7.1.0\mingw64\share\octave\packages\audio-2.0.4\*`, the
asterisk at the end is escaped with a backslash. So, it is treated as a
literal asterisk, and `ls` searches for a file (or folder) named
`audio-2.0.4*`.
If I understand correctly, you would like that the function recognizes that
you didn't mean to escape the asterisk in this case. But how should it decide
whether the user meant to escape the asterisk or not?



    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?62282>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/