[Octave-bug-tracker] [bug #47950] glob and dir functions fail with escaped wildcard characters in Windows

[Philip Nienhuis]

Follow-up Comment #17, bug #47950 (project octave):

@Mike:

AFAIK, no. 
See here
(https://msdn.microsoft.com/en-us/library/windows/desktop/aa365247%28v=vs.85%29.aspx#naming_conventions)
for an overview of forbidden filename characters:

<
>
:
"
/
\
|
?
*
...and anything with a uint8 value below 32.


I got the impression that this bug isn't so much about allowed characters in
path & file names but rather about characters allowed/used in globbing
patterns (hence the issue with '[' and ']'). 
In MSYS, globbing simply works. For a directory tree:

c:\tmp\octave\dirab.txt
c:\tmp\octave\dirac.txt

I get:

address@hidden /c/tmp/octave
$ ls dira[bd].txt
dirab.txt

address@hidden /c/tmp/octave
$ ls dira[bdef].txt
dirab.txt

address@hidden /c/tmp/octave
$ ls dira[acf].txt
dirac.txt


so I'd somewhat naively guess that if Octave invokes the file I/O in the mingw
libraries, globbing in Octave should simply work on Windows as well.


    _______________________________________________________

Reply to this item at:

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

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