A possible changelog entry is:
* /etc/bash_command_not_found: print error message if a command
is not found, and the package has been removed but not purged.
I think an indentation with four spaces is better for this file (in order to
avoid line wrapping on 80x25 terminals).
This file is indented accordingly and I have replaced ']] ;' with ']];', since,
unlike the zsh variant, it contains no ')) ;' :
http://stateful.de/~carsten/tmp/150730QuR6xwuv7Z0/bash_command_not_found
Testing the function, i.e., w/o the “if [[ -x /usr/lib/command-not-found
]] ; then” guard around the function definition, before committing seems
to be a good idea. This requires an Ubuntu installation (which I do not
have) and should be done with the package installed, and with the
package removed but not purged.
Btw., \builtin print avoids functions and aliases named printf, which
could lead to a command-not-found-error in command_not_found_handle() -
not in a bulletproof way, but for this we'd need a new POSIX release.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1479805
Title:
/etc/bash_command_not_found is utterly broken
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/command-not-found/+bug/1479805/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
