Closed Artoria2e5 closed 1 week ago
Four in a row!
This issue has not had any activity in 6 months, if there is no further activity in 7 days, the issue will be closed automatically.
Activity in this case refers only to comments on the issue. If the issue is closed and you are the author, you can re-open the issue using the button below. Please add more information to be considered during retriage. If you are not the author but the issue is impacting you after it has been closed, please submit a new issue with updated details and a link to this issue and the original.
I found this issue while trying to take on #13089 myself. It's a minor headache to be unable to glob stuff with escapes and embedded spaces. This is not a limitation in POSIX shell, nor is it one in the original glob(3) language.
Steps to reproduce
Expected behavior
Actual behavior
Environment data
How did this happen?
Test case (4) indicates that the parser sees two string literals glued together as two distinct "words". This could be improved without breakings stuff by just making a cmdlet for globbing a mixture of quoted (to be escaped) and bare (to be put into the pattern raw) character runs.
Test case (3) indicates that the heuristic in
NativeCommandParameterBinder::AppendOneNativeArgument
is inadequate. Even when fed a valid glob, it sees the space in the string and decides that it is non-globbable from that. Bad idea.