<snapname> may be clearer than <snap name>
Bug #1764413 reported by
Mark Shuttleworth
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
command-not-found (Ubuntu) |
Fix Released
|
High
|
Unassigned |
Bug Description
In the did-you-mean case (a command that is not found and which is not an exact match for an existing command but is close enough to warrant suggestions) it might be clearer to suggest 'snap info <snapname>' rather than 'snap info <snap name>'. The use of a tight snapname suggest a single-word input.
To post a comment you must log in.
Just a quick question: we have three cases where we use "<snap name>" right now. I assume we change all three (for consistency):
"""
sudo snap install aws-cli-compat # version 0.1
sudo apt install aws # version 1.0
-See 'snap info <snap name>' for additional versions.
+See 'snap info <snapname>' for additional versions.
and
sudo snap install foo1 # version 1.0, or
sudo snap install foo2 # version 2.0
-See 'snap info <snap name>' for additional versions.
+See 'snap info <snapname>' for additional versions.
and
command 'x-aws' from snap aws-cli (2.0)
command 'x-aws' from deb aws (1.0)
-See 'snap info <snap name>' for additional versions.
+See 'snap info <snapname>' for additional versions.
"""