`ls` is not self-consistent

Prerequisites

• Write a descriptive title.
• Make sure you are able to repro it on the latest released version
• Search the existing issues.
• Refer to the FAQ.
• Refer to Differences between Windows PowerShell 5.1 and PowerShell.

Steps to reproduce

I have a file .\o\abc [defg].pdf, then I try all commands below to ls it. The first char y/x represents that the corresponding command works or not, i.e. prints the file or nothing without any error.

y ls 'abc `[defg`].pdf' -Recurse
y ls 'abc `[defg`].pdf' -Recurse -File | ls
x ls (ls 'abc `[defg`].pdf' -Recurse).FullName
x ls "$((ls 'abc `[defg`].pdf' -Recurse).FullName)"
x ls (ls 'abc `[defg`].pdf' -Recurse -File).ToString()

Expected behavior

All commands above should works exactly the same way.

Actual behavior

Just as the first char y/x in each command line shows. Output of `ls` can't be recognized by `ls` itself when the output is not passed via pipeline. 

Error details

No response

Environment data

Name                           Value
----                           -----
PSVersion                      7.2.6
PSEdition                      Core
GitCommitId                    7.2.6
OS                             Microsoft Windows 10.0.19043
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0

### Visuals

_No response_

[jhoneill]

@mklement0 yes 18038 is only another example of escaped wildcards not being processed correctly, there seems to be independent code in multiple places making similar errors, so a fix for 18038 wouldn’t fix 17992 and vice versa.

As another example, on Windows dir | out-file -path 'files [Sept].txt' gives a “file does not exist”, but dir | out-file -path 'files `[Sept`].txt' will create a file with ` in the name, I think this is another distinct bit of code.

[jhoneill]

@mklement0 I brought this up at the cmdlet working group yesterday. Things are being looked at again, although we may get the same conclusion as before. The point you make in 9475 that Set-Content and Out-File work differently suggests “cmdlet thing which is relatively easy to fix”, rather than “provider minefield”

You’ve got the best list of related issues for this that I’ve see so far here https://github.com/PowerShell/PowerShell/issues/17106#issuecomment-1088755835

I want to make sure this points to that one 😃