Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: 3.0-pre1 odd behavior
- X-seq: zsh-workers 1519
- From: "Bart Schaefer" <schaefer@xxxxxxxxxxxxxxxxxxxxxxx>
- To: Clint Olsen <olsenc@xxxxxxxxxxxxxxxx>, zsh-workers@xxxxxxxxxxxxxxx
- Subject: Re: 3.0-pre1 odd behavior
- Date: Tue, 2 Jul 1996 21:52:55 -0700
- In-reply-to: Clint Olsen <olsenc@xxxxxxxxxxxxxxxx> "3.0-pre1 odd behavior" (Jul 2, 4:50pm)
- References: <199607022350.AA008521402@xxxxxxxxxxxxxxxxxxxxx>
- Reply-to: schaefer@xxxxxxx
On Jul 2, 4:50pm, Clint Olsen wrote:
} Subject: 3.0-pre1 odd behavior
}
} Is this a new feature?
}
} I've never seen zsh report exit status on jobs in the foreground before.
Happens only with both the `monitor' and `printexitvalue' options set,
and then only for commands that exit nonzero. I think `printexitvalue'
is a relatively new option, but I'm not sure (I've never set it).
By the way, workers, what's up with `monitor'?
MONITOR (-m, ksh: -m)
Allow job control. Set by default in interactive shells.
> exec zsh -l
zagzig[21] setopt | grep monitor
monitor off
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.nbn.com/people/lantern
New male in /home/schaefer:
>N 2 Justin William Schaefer Sat May 11 03:43 53/4040 "Happy Birthday"
Messages sorted by:
Reverse Date,
Date,
Thread,
Author