This is fixed in openSUSE command_not_found_handler, which does extra
checks:
http://repo.or.cz/w/scout.git?a=blob;f=handlers/bin/command_not_found_bash;hb=HEAD
--
command-not-found runs in the background within Midnight Commander (mc)
https://bugs.launchpad.net/bugs/209519
You received this
see https://bugzilla.novell.com/show_bug.cgi?id=470844
there is a fix for this bug
--
bogus background command often causes shell to exit
https://bugs.launchpad.net/bugs/127399
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
see https://bugzilla.novell.com/show_bug.cgi?id=470844
there is a fix for this bug
--
command-not-found does not work when unknown command is piped to less/more
https://bugs.launchpad.net/bugs/300647
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Public bug reported:
Binary package hint: command-not-found
Steps to reproduce (can use more instead of less):
$ foobar | less
bash: foobar: command not found
lines ?-?/? (END)
[1]+ Stopped foobar | less
expected result:
$ foobar | less
bash: foobar: command not found
We created own implementation of command-not-found for SUSE and have the
same problem. So it is not Ubuntu specific, but it is broken somewhere
between command-not-found handler and python script.
--
command-not-found runs in the background within Midnight Commander (mc)
We created own implementation of command-not-found for SUSE and have the
same problem. So it is not Ubuntu specific, but it is broken somewhere
between command-not-found handler and python script.
--
bogus background command often causes shell to exit
https://bugs.launchpad.net/bugs/127399
You
Update: this has nothing to do with python.
If I put
command_not_found_handle() {
ls
}
into /etc/bash_command_not_found or something similar.
And run
foobar
bash will crash also (from time to time).
When handler contains only bash internals (echo ...), the crashes won't
happen. This
