On Wed, Apr 01, 2015 at 05:21:42PM +, 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
On Tue, 31 Mar 2015 15:39:13 -0500, John McKown wrote:
> Hum, on my system, I get the message you are expecting. Transcript:
<-snip->
And, here...
This is puzzling.
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@n
Hum, on my system, I get the message you are expecting. Transcript:
$ uname -a
Linux it-johnmckown-linux 3.19.1-201.fc21.x86_64 #1 SMP Wed Mar 18
04:29:24 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
[tsh009@it-johnmckown-linux junk]$ bash --version
GNU bash, version 4.3.33(1)-release (x86_64-redhat-li
It was fixed a year ago:
https://github.com/hughsie/PackageKit/commit/b8f5de2e0ceaf7424e4e2c94adc46fa06eefce73
On Tue, Mar 31, 2015 at 1:04 PM, Robin A. Meade
wrote:
> ok, thanks. If I run bash with no startup files, I get expected output.
>
> With my regular start-up files:
>
> $ declare -f c
ok, thanks. If I run bash with no startup files, I get expected output.
With my regular start-up files:
$ declare -f command_not_found_handle
command_not_found_handle ()
{
runcnf=1;
retval=127;
[ ! -S /var/run/dbus/system_bus_socket ] && runcnf=0;
[ ! -x /usr/libexec/packagekitd ]
Cannot reproduce with these versions:
dualbus@yaqui:~/local/src/gnu/bash$ "a nonexistent command name with spaces"
bash: a nonexistent command name with spaces: command not found
dualbus@yaqui:~/local/src/gnu/bash$
GNU bash, version 4.4.0(1)-devel (x86_64-unknown-linux-gnu)
dualbus@yaqui:~$ "a n
