package python-coverage clone 726255 -1 retitle -1 Improve error message for users expecting ‘coverage’ command outlook -1 Seek a means of suggesting alternatives for not-found commands. thanks
On 28-Oct-2013, Barry Warsaw wrote: > My own gut feeling is that not providing /usr/bin/coverage will confuse > our users who are reading upstream documentation, not just for coverage > but possibly other packages too. So I tend to think there should be > *some* mechanism for providing this. Okay. I'm cloning this bug report to one for this separate issue. > At the very least, I think there should be some way of hinting to users > that run `coverage` that `python-coverage` or `python3-coverage` is the > command. Maybe command-not-found will save us here? The documentation for ‘command-not-found’ suggests that it gets its information from available packages, and suggests one to install. How does that help us if the ‘python-coverage’ package is already installed? Moreover, I don't see how to inform ‘command-not-found’ of what we want. The documentation doesn't imply any means of explicitly specifying this information. -- \ “Dad always thought laughter was the best medicine, which I | `\ guess is why several of us died of tuberculosis.” —Jack Handey | _o__) | Ben Finney <b...@benfinney.id.au>
signature.asc
Description: Digital signature
