** Changed in: command-not-found (Ubuntu)
Status: Fix Committed => Fix Released
--
wrong exit code
https://launchpad.net/bugs/67726
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Fixed in my bzr tree, will be part of the next upload.
I changed it to return always 127.
** Changed in: command-not-found (Ubuntu)
Assignee: (unassigned) => Michael Vogt
Status: Confirmed => Fix Committed
--
wrong exit code
https://launchpad.net/bugs/67726
--
ubuntu-bugs mailing
Please note that the command-not-found hook is only active when the
shell is run interactively and not in posix mode. So configure scripts
will not fail.
The disadvantage of returning 127 is that the output will look more ugly:
$ galeon
The program 'galeon' is currently not installed, you can ins
The exit code should be 127, not 1. (Compare with the shell.)
--
wrong exit code
https://launchpad.net/bugs/67726
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Couldn't this be fixed by simply rewriting the 'try' clause in /usr/bin
/command-not-found? I've got something like this in mind:
try:
...
#except KeyboardInterrupt: # don't need this anymore
# ...
finally:
import sys
sys.exit(1)
This would ensure that no matter wha
** Changed in: command-not-found (Ubuntu)
Status: Unconfirmed => Confirmed
--
wrong exit code
https://launchpad.net/bugs/67726
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
We can't promote command-not-found to main until this is fixed; it would
hose builds on developer machines in thoroughly exciting ways.
** Changed in: command-not-found (Ubuntu)
Importance: Undecided => High
--
wrong exit code
https://launchpad.net/bugs/67726
--
ubuntu-bugs mailing list
ubu
