Zsh reporting bad return status of commands

Zsh reporting bad return status of commands

[Clint Olsen]

This is version 3.0.0.

On HP-UX for some reason, 3.0 started doing this:

/foo not found
zsh: exit 2     ls -AF /foo

It doesn't exhibit this behavior on SunOS.  It's not that big of a deal,
but it's rather irritating to see the extra output.

Thanks,

-Clint

Re: Zsh reporting bad return status of commands

[Zefram]

Clint Olsen wrote:
>On HP-UX for some reason, 3.0 started doing this:
>
>/foo not found
>zsh: exit 2     ls -AF /foo
>
>It doesn't exhibit this behavior on SunOS.  It's not that big of a deal,
>but it's rather irritating to see the extra output.

This output is controlled by a zsh option, PRINT_EXIT_VALUE.  Use
"setopt noprintexitvalue" to disable it.  Or, since it's off by
default, remove the "setopt printexitvalue" from your
.z(profile|login|sh(rc|env)).

-zefram

Re: Zsh reporting bad return status of commands

[Clint Olsen]

On Jan 28, Zefram wrote:
> Clint Olsen wrote:
> >On HP-UX for some reason, 3.0 started doing this:
> >
> >/foo not found
> >zsh: exit 2     ls -AF /foo
> >
> >It doesn't exhibit this behavior on SunOS.  It's not that big of a deal,
> >but it's rather irritating to see the extra output.
> 
> This output is controlled by a zsh option, PRINT_EXIT_VALUE.  Use
> "setopt noprintexitvalue" to disable it.  Or, since it's off by
> default, remove the "setopt printexitvalue" from your
> .z(profile|login|sh(rc|env)).

Interesting.  Then it must be broken on SunOS since it is also set there
but it doesn't print out the bad exit status.

pdxgp1 ~# uname -a
SunOS pdxgp1 4.1.3 10 sun4m

pdxgp1 ~# setopt
allexport
autolist
automenu
interactive
login
monitor
printexitvalue
rcexpandparam
shinstdin
zle

pdxgp1 ~# ls /foo
/foo not found

-Clint
-- 
Clint Olsen                                        .  __
olsenc@ichips.intel.com                              /o \/  o
                                                  .  \__/\

Re: Zsh reporting bad return status of commands

[Zefram]

Clint Olsen wrote:
>Interesting.  Then it must be broken on SunOS since it is also set there
>but it doesn't print out the bad exit status.
...
>pdxgp1 ~# ls /foo
>/foo not found

No, it's just that the native ls on SunOS (and Solaris) returns an exit
code of 0 under these circumstances.  A bug in ls?  It wouldn't be the
first one.

-zefram

Re: Zsh reporting bad return status of commands

[Risto J Laitinen]

zefram@dcs.warwick.ac.uk writes:
 > Clint Olsen wrote:
 > >Interesting.  Then it must be broken on SunOS since it is also set there
 > >but it doesn't print out the bad exit status.
 > ...
 > >pdxgp1 ~# ls /foo
 > >/foo not found
 > 
 > No, it's just that the native ls on SunOS (and Solaris) returns an exit
 > code of 0 under these circumstances.  A bug in ls?  It wouldn't be the
 > first one.

It's just the BSD variant of ls that returns 0:

kanto% uname -a
SunOS kanto 5.4 Generic_101945-41 sun4m sparc
kanto% /usr/bin/ls /foo; echo $?
/foo: No such file or directory
2
kanto% /usr/ucb/ls /foo; echo $? 
/foo not found
0