Public bug reported:

The new language for CNF with snaps is much better thank you, but there
is a mistake in that it recommends that you use 'snap info' with the
*command* when it should in fact be 'snap info <snapname>'. As an
example:

mark@mark:~$ aws

Command 'aws' not found, but can be installed as:

 snap aws-cli
 deb awscli () 

See 'snap info aws' for additional versions.

mark@mark:~$ snap info aws
error: no snap found for "aws"

mark@mark:~$ snap info aws-cli 
name:      aws-cli
summary:   Universal Command Line Interface for Amazon Web Services
[...snip...]

In this case, the CNF output should be tweaked to use the snap name not
the command name:

See 'snap info aws-cli' for additional versions.

In fact, I think we should tweak the output as follows, in order to line
things up and make the commands cut-and-pasteable:

Command 'aws' not found, but can be installed with:

 snap install aws-cli  # version XXXX is latest/stable
 apt  install awscli    # version YYYY

See 'snap info aws-cli' for additional versions.

** Affects: command-not-found (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1754839

Title:
  CNF recommends 'snap info <command>' instead of 'snap info <snapname>'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/command-not-found/+bug/1754839/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to