New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Experimental feature PSNativeWindowsTildeExpansion does not expand when there is backtick escaping #21276
Comments
Related (the same bug has existed for a long time on Unix-like platforms, where tilde expansion is a stable feature):
cmd /c echo ~\'foo bar' # should expand, doesn't
cmd /c echo `~ # shouldn't expand, does
cmd /c echo ~'\' # shouldn't expand, does And, with respect to tab-completion: |
@mklement0 I checked my PR branch and your first case works as you expect. For the second case, I don't know if you should expect it not to expand. Even thought you are escaping it, I don't recall another case where it would be treated as a literal. You'd have to enclose it with single-quotes to indicate it's literal. The 3rd case I also don't see any inconsistency in expanding as it resolves to |
Glad to hear it (in my initial response I missed that you were referring to your PR).
By way of analogy: both
The very purpose of this feature - at least originally - was emulation of the behavior of POSIX-like shells. # From a POSIX-compatible shell; contrast with: echo ~/ or echo ~/'foo'
# -> '~/'
echo ~'/' |
@SteveL-MSFT, speaking of the analogous case; please see: I haven't looked into any technical challenges that may prevent interpreting |
Prerequisites
Steps to reproduce
Enable the
PSNativeWindowsTildeExpansion
experimental feature.Expected behavior
Actual behavior
Error details
No response
Environment data
Visuals
No response
The text was updated successfully, but these errors were encountered: