Michael Klement

@iSazonov: Not in terms of native globbing, as far as I can tell, but you can do the following: ```powershell /bin/echo (Get-Item 'a *').Name ```

It's not a duplicate, because the linked issue relates to resolving PS-drive-based paths to native paths, (which would also apply to Windows), whereas this issue is related to the (Unix-only)...

I see: it happens to be technically related rather than a duplicate.

Note that there's a previous discussion about generally allowing targeting _variables_ in contexts where _file paths_ are expected, so that `Start-Process ... -RedirectStandardOutput variable:out` would capture stdout in variable `$out`....

@jborean93, it's a good point that redirecting to _variables_ could only work meaningfully with (possibly implied) `-Wait` > You can already capture output with just invoking the exe today The...

@jhoneill: * The uses cases in my previous comment imply _hidden_ execution, in which case the question of a blank window is moot. * Even if the launched window runs...

@jborean93 > I’m not sure why this needs `Start-Process`. You can certainly just do `pwsh { … }` Good point: `pwsh { … }` is definitely the way to go...

@aetonsi, yes, when you call a script via the PowerShell CLI, the stdout and stderr streams are the only ones available, as with any child process. By default, PowerShell only...

> Also it is not clear why path without prefix is expected behavior. To quote from the OP, emphasis added: > While $PWD.ProviderPath does reflect the unprefixed (but always native)...

@iSazonov : In this case you're not _working with_ one path form of the other. Instead, you're using acceptable variations in the syntactic form of an _argument_ to _target_ a...