From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26846 invoked by alias); 14 Dec 2017 23:00:59 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: List-Unsubscribe: X-Seq: 42127 Received: (qmail 14200 invoked by uid 1010); 14 Dec 2017 23:00:59 -0000 X-Qmail-Scanner-Diagnostics: from mail-qt0-f172.google.com by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.99.2/21882. spamassassin: 3.4.1. Clear:RC:0(209.85.216.172):SA:0(-1.9/5.0):. Processed in 9.872325 secs); 14 Dec 2017 23:00:59 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE, SPF_PASS,T_DKIM_INVALID autolearn=ham autolearn_force=no version=3.4.1 X-Envelope-From: schaefer@brasslantern.com X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brasslantern-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=ZKY+JKF82JhL4lzQA+YeUjQmf6SUkYX+HPmPdW6GP4M=; b=u9vmvlafCxHHQVN6aauemKY9SThwVofuIjPiqdNAITzhk2rncL0iRysnaf4l/9vu3s 8eEuBlZcRIHRySYktwTmZmrUZpSlHZ0ACTKXZbJzU5drIuHYIjEFuJVRJSPwYoCxtlPA fXgQlXA5VpVuG+fH4gwMDrBpmGALmJurWNrVo+Tpw67RGMbd7V8lIw4zSsVMz4VQF46b 4ZfYEj4QAnw1gY7b1cZ0bnQl7N5ey4HYC9hIc7bme3MeV2gaqOHqZK+0vYWjXOaBoDmB bXQh7Bguz4CvYYRKmK51QrQvhT0XzPNuj8alt96yTRAzA6jMqFJuwFbKDyPoZBWLyDTV 0rXA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=ZKY+JKF82JhL4lzQA+YeUjQmf6SUkYX+HPmPdW6GP4M=; b=P+XDrlu5Hl5dhQeKmhf4BiFwHfpFkbyXts9HNgZwO0iLKbMIDI2J4oUCKmM44Xvw7O y966GpjdrhLqGT9DT10VRWtpdFqW1qHB0TQ8OtBXJLEucImgaQ1RZSH2H+JFA67A7ssf k6dXvB6bJ25KyMaXW04Dh6/1IBz6SV8VUN1S3u8IZmf5UWiK5WL6VW7q1c4rWAFkz/lv cTGiM+96vmDHThye/s6l/qwKjW1N6V23N2Z/rw2xzvczDuRuEKkwVfByw6iU1WgnRchN 0btVA0950JC6ptjUUMLwEK56ImSnZBK3iEJkZZD1fTS0HMDghhDeiiirSsSbWL7YN57H U5MA== X-Gm-Message-State: AKGB3mJGBpwCFvinqNXhYHiMkBd14eD7sVaWzvucTAz2PemZu8SDICbd pSi5LR38jd8iM7fyIndS3vUvcJXAT08IvHaHSE2sQQ== X-Google-Smtp-Source: ACJfBouESOde1vFSFnCoDTE38o6rSLchcIuMnTtyaCmEtJdJJn8L7pdFJnqTVVtfFUAvJddeoiFqU089YhPhDQIAz7Q= X-Received: by 10.200.7.7 with SMTP id g7mr17975013qth.279.1513292446226; Thu, 14 Dec 2017 15:00:46 -0800 (PST) MIME-Version: 1.0 In-Reply-To: References: From: Bart Schaefer Date: Thu, 14 Dec 2017 15:00:45 -0800 Message-ID: Subject: Re: [BUG] err_exit misbehaviour involving function call inside else To: dana Cc: "zsh-workers@zsh.org" Content-Type: text/plain; charset="UTF-8" On Thu, Dec 14, 2017 at 2:40 PM, dana wrote: > > It seems like it has something to do specifically with calling a function inside > the body of an `else`. See the thread w/Subject: "set -e" handling is broken with zsh 5.3.1 and 5.4.1 In particular workers/41608 and workers/41615 ... I wonder if you have found the regression that wasn't found at the time of that patch. At the very least this sounds related.