Zsh Mailing List Archive Messages sorted by: Reverse Date, Date, Thread, Author

Re: Debian zsh bug triage

X-seq: zsh-workers 26193
From: Stephane Chazelas <Stephane_Chazelas@xxxxxxxx>
To: Richard Hartmann <richih.mailinglist@xxxxxxxxx>
Subject: Re: Debian zsh bug triage
Date: Mon, 29 Dec 2008 21:19:51 +0000
Cc: zsh-workers@xxxxxxxxxx, 276187@xxxxxxxxxxxxxxx, 288323@xxxxxxxxxxxxxxx
In-reply-to: <2d460de70812291246o62169a0bxa7b68ce4aa5be504@xxxxxxxxxxxxxx>
Mail-followup-to: Richard Hartmann <richih.mailinglist@xxxxxxxxx>, zsh-workers@xxxxxxxxxx, 276187@xxxxxxxxxxxxxxx, 288323@xxxxxxxxxxxxxxx
Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
References: <2d460de70812291246o62169a0bxa7b68ce4aa5be504@xxxxxxxxxxxxxx>

On Mon, Dec 29, 2008 at 09:46:07PM +0100, Richard Hartmann wrote:
[...]
> 2) Unexpected behaviour when stopping a job in a command chain[3]
> 
> Consider this:
> 
> echo one && sleep 10 && echo two
> 
> When stopping `sleep 10`, `echo two` will never be executed, no matter in
> what way you revive `sleep 10`. That is OK as backgrounding `sleep 10`
> will set $? to 20. Yet, with
> 
> echo one ; sleep 10 ; echo two
> 
> the same thing happens. As Bart pointed out[4]:
[...]

That'd be a feature. All the other shells except bash behave
like that. You'll find plenty of places where people complain
about bash behavior.

-- 
Stéphane

Follow-Ups:
- Re: Debian zsh bug triage
  - From: Richard Hartmann

References:
- Debian zsh bug triage
  - From: Richard Hartmann

Messages sorted by: Reverse Date, Date, Thread, Author