René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Emulation of ~ (tilde) expansion for native utilities is incomplete","articleBody":"Note: \r\n\r\n* `~` expansion for native utilities currently fundamentally only works on _Unix_ platforms - but Windows would benefit from it too:  see #10675\r\n\r\n* Fully emulating the logic of `~` expansion in PowerShell requires recognizing _partial_ quoting of sub-tokens in arguments (e.g., `~/'foo bar'`), which may turn out to be a challenge based on how argument parsing currently works.\r\n\r\n# Steps to reproduce\r\n\r\nOn a Unix-like platform:\r\n\r\n```powershell\r\n# Quoting the argument as a whole always suppresses ~ expansion.\r\n/bin/echo '~/foo' | Should -Be '~/foo'\r\n\r\n# Both commands should expand ~ to the value of $HOME, \r\n# because the ~/ prefix is unquoted.\r\n/bin/echo ~/foo | Should -Not -BeLike '~/*'\r\n/bin/echo ~/'foo bar' | Should -Not -BeLike '~/*'\r\n```\r\n\r\n# Expected behavior\r\n\r\nAll tests should succeed.\r\n\r\n# Actual behavior\r\n\r\nThe 3rd test fails, because the partially quoted argument prevented `~` expansion - even though `~/` is _unquoted_.\r\n\r\n```none\r\nExpected like wildcard '~*' to not match '~/foo bar', but it did match.\r\n```\r\n\r\nNote that in POSIX-like shells - whose behavior here is being emulated - `/bin/echo ~/'foo bar'` indeed expands `~`, as expected.\r\n\r\n# Environment data\r\n\r\n```none\r\nPowerShell Core 7.0.0-rc.1\r\n```\r\n","author":{"url":"https://github.com/mklement0","@type":"Person","name":"mklement0"},"datePublished":"2019-12-17T20:40:51.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":4},"url":"https://github.com/11386/PowerShell/issues/11386"}