Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Zsh reporting bad return status of commands
- X-seq: zsh-workers 2831
- From: olsenc@xxxxxxxxxxxxxxxx (Clint Olsen)
- To: zsh-workers@xxxxxxxxxxxxxxx
- Subject: Re: Zsh reporting bad return status of commands
- Date: Tue, 28 Jan 1997 08:56:22 -0800
- In-reply-to: <11269.199701281458@xxxxxxxxxxxxxxxxxxxxxxx>; from Zefram on Jan 28, 1997 14:58:56 +0000
- Organization: Intel Corporation, Hillsboro, OR
- References: <19970127141513.VX31036@@> <11269.199701281458@xxxxxxxxxxxxxxxxxxxxxxx>
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@xxxxxxxxxxxxxxxx /o \/ o
. \__/\
Messages sorted by:
Reverse Date,
Date,
Thread,
Author