René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Resolve file paths before passing to native commands","articleBody":"# Summary of the new feature/enhancement\r\n\r\nOn Windows, the `~` is only understood by PowerShell.  So if you try: `notepad ~\\foo.txt`, it complains it can't find the file path.  On Windows and non-Windows PSDrives have no meaning outside of PowerShell, so you can't do something like `pico temp:/temp.txt` with expectation that you're creating a file in the temp drive.\r\n\r\n# Proposed technical implementation details (optional)\r\n\r\nThe problem is determining if the file path should be resolved or if it's a literal string being passed to the native command.  In most cases, it would seem that resolving the path would be fine.  Literal strings can have quotes around them making it explicit.","author":{"url":"https://github.com/SteveL-MSFT","@type":"Person","name":"SteveL-MSFT"},"datePublished":"2019-10-01T21:38:17.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":2},"url":"https://github.com/10675/PowerShell/issues/10675"}