GNOME Bugzilla – Bug 660995
change the error message on command not found
Last modified: 2011-10-05 17:13:57 UTC
I often will type something like jhbuild dconf-editor to which jhbuild replies: jhbuild dconf-editor: command not found and *sometimes* I parse that correctly and realize I forgot the "run", but other times I think "oops, I must have forgotten to reinstall that after installing F16", so I do "sudo yum install dconf-editor", and then get very confused when yum tells me that it's already installed. So, here's a suggestion. I don't care about the exact wording (or the "did you mean" suggestion), as long as it says something other than what bash says ("command not found").
Created attachment 198352 [details] [review] commands: change the error message on command not found to make it more obvious that it's complaining about not finding a jhbuild sub-command as opposed to a command-line command
Review of attachment 198352 [details] [review]: Looks OK, though - and I have no data - I think it's a lot more likely for people to typo commands than to forget "run". Long term I want to encourage people to stay in "jhbuild shell" anyways. A "did you mean command X" patch would be cool...harder to implement though. If you want to commit this that's fine, if you want to do the harder one - yay!
committed as-in