René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"variable completion of `$:` provides no results","articleBody":"# Steps to reproduce\r\n\r\n```powershell\r\n$:\u003cCTRL SPACE\u003e\r\n\r\n# OR\r\n\r\ntabexpansion2 '$:' 2 # result set shows that it found nothing to match\r\n\r\n```\r\n\r\n# Expected behavior\r\n\r\nExpected was a full list of all the variables that could be used at least with the notation `$:`\r\n\r\n# Actual behavior\r\n\r\nNo results are returned, or list is offered.\r\n\r\n# Environment data\r\n\r\n\u003c!-- provide the output of $PSVersionTable --\u003e\r\n\r\n```none\r\nName                           Value\r\n----                           -----\r\nPSVersion                      7.0.0-preview2.27045\r\nPSEdition                      Core\r\nGitCommitId                    7.0.0-preview2.27045\r\nOS                             Microsoft Windows 10.0.18941\r\nPlatform                       Win32NT\r\nPSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}\r\nPSRemotingProtocolVersion      2.3\r\nSerializationVersion           1.1.0.1\r\nWSManStackVersion              3.0\r\n```\r\nPrevious versions behave the same way.\r\n\r\nI believe this should work, since `$:` is a valid start to specifying a variable.   See https://github.com/PowerShell/PowerShell/pull/10226/commits/033ef6cd6bf0b3f8a78a9b618f98334cd5aa7626 for a commit that would fix this issue.\r\n\r\nIt might need to be determined if the `:` representing a blank drive/scope/provider field should be stripped from the returned completions, when they are not needed), and if the common scopes and providers should still be included in the list.","author":{"url":"https://github.com/msftrncs","@type":"Person","name":"msftrncs"},"datePublished":"2019-07-27T06:04:42.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":6},"url":"https://github.com/10239/PowerShell/issues/10239"}