Snap points me to a package that, in fact, doesn’t exist, when trying to install the nonexisting "vscode" package.

[Nagy Gergely]

Let’s try to install the VS Code editor, and commit the noob mistake of using a wrong package name "vscode" instead of the correct "code". Instead of the expected `error: snap "vscode" not found.`, we get a chain of suggestions to packages that doesn't exist:

(Please ignore my custom $PS1, this is in a Bash shell).

```
(base) nagyg -> snap install vscode
error: snap "vscode" is not available on stable but is available to install on the following
       channels:

       candidate snap install --candidate vscode
       beta snap install --beta vscode
       edge snap install --edge vscode

       Please be mindful pre-release channels may include features not completely tested or
       implemented. Get more information with 'snap info vscode'.

(base) nagyg -> snap install --beta vscode
error: snap "vscode" is not available on beta but is available to install on the following
       channels:

       edge snap install --edge vscode

       Get more information with 'snap info vscode'.

(base) nagyg -> snap install --edge vscode
error: snap "vscode" is not available on latest/edge but other tracks exist.

       Please be mindful that different tracks may include different features. Get more information
       with 'snap info vscode'.

(base) nagyg -> snap info vscode
error: no snap found for "vscode"
```

[Paweł Stołowski (stolowski)]

Thanks for reporting, confirmed, I agree it's confusing, something is off and needs to be looked at.