Re: Incomplete 'command not found' error message if command name contains spaces

[Greg Wooledge]

On Wed, Apr 01, 2015 at 05:21:42PM +0000, Allodoxaphobia wrote:
> On an older Ubuntu 10.04 system I still use (I know, I know...) I
> get _no_ response.  But the return code appears correct:
> 
> jonesy@nix4:~$ uname -a
> Linux nix4 2.6.32-39-generic #86-Ubuntu SMP Mon Feb 13 21:47:32 UTC 2012 i686 
> GNU/Linux
> jonesy@nix4:~$ bash -version
> GNU bash, version 4.1.5(1)-release (i486-pc-linux-gnu)
> Copyright (C) 2009 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later 
> <http://gnu.org/licenses/gpl.html>
> This is free software; you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.
> jonesy@nix4:~$ echo $?
> 0
> jonesy@nix4:~$ "a nonexistent command with spaces"
> jonesy@nix4:~$ echo $?
> 127

Check what your command_not_found_handle function is set to do.
Many Linux distributions create one in the default user profiles, and
as we've seen earlier in this thread, some of them have bugs.