From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.1 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FROM,MAILING_LIST_MULTI,RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.2 Received: from primenet.com.au (ns1.primenet.com.au [203.24.36.2]) by inbox.vuxu.org (OpenSMTPD) with ESMTP id 34db53a1 for ; Sat, 28 Sep 2019 08:25:17 +0000 (UTC) Received: (qmail 274 invoked by alias); 28 Sep 2019 08:25:09 -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: 44790 Received: (qmail 17253 invoked by uid 1010); 28 Sep 2019 08:25:09 -0000 X-Qmail-Scanner-Diagnostics: from mail-vk1-f177.google.com by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.101.2/25580. spamassassin: 3.4.2. Clear:RC:0(209.85.221.177):SA:0(-2.0/5.0):. Processed in 2.988647 secs); 28 Sep 2019 08:25:09 -0000 X-Envelope-From: sgniazdowski@gmail.com X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received-SPF: pass (ns1.primenet.com.au: SPF record at _netblocks.google.com designates 209.85.221.177 as permitted sender) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=AoEs0qgZB+2nv8q6ZjCjN7+JcSctGw5k1Ed4SZ3tEHw=; b=XWdd29nMeTCEPQioHUQArbvKIj314YymUlKnHYzR5avOdEHBWropeCnVknBD4/+/h3 24swUgb+h5QP+fW9o1MKon1xLp9PiGV+f+/4m24tdp/R2Am8UyDl22882sIETd2dWcYf G6oJu8ztyNBJBjQVMVv1kRXxq2fhkSu4TSFLbsJEYUEy4WpZPIx2cdnhhVtvNR8rgwTi joPg/Y9vGdQbkGQFfCYnK0Iw5NEnzkU9fZAUj627mis9E6FBYTKaV4uiqiuoTRAJnnMS 8cc56oH261CZz1WqKF6mHhC/7U9470zW4YUcuPeK4juelkmhXFNDiP2qKpr5vS9JN49X or2w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=AoEs0qgZB+2nv8q6ZjCjN7+JcSctGw5k1Ed4SZ3tEHw=; b=hTAYP4dTFqh5Us2+QOv3KIK2FcqPT6G+q+44E+xYlmve13wLfSvTPGvdpsun+m9lcO OC4dsUb1VLIDGrKK8sVswKgVHIRFWxJLRYCEmEs5KBJ62hnRoQxX28GPidqN4Wkl7xJk 5EOupM+q2wMDLRc+WuekVZHW2nCXPE0KjYrsWQnOb41I54QMzBS8YvenRDuDU1hL7a7D SBV//cT/e6+wgH+BWLCswr/BceC/ibWQtzU+E9r1oVh3PTIJeGwm9D5J0RvH8uwDYcnB wf4C5LMYtKZ2Q2lcGM6W/iwee9+P2PRCy2R6Sf1qgJ1RhcJ83yKmUVvPjYElfVuBen5H OiQQ== X-Gm-Message-State: APjAAAXsw2OpA+4KZmIopLabJgj1TxjCfZwaDpuXel+wZVwWB+zUN330 6LsXo0U9qSVamFkYaveo5Krt4IWj9r/Pq4eo09Y= X-Google-Smtp-Source: APXvYqyw6tMLujoHDbnYZMvZkF+lQ7PemOserjLzFe26BY1rXgVHqq/HRhW2fCF8E1SuvxY81qLHvvc1PrqtH1mDN+g= X-Received: by 2002:a1f:8593:: with SMTP id h141mr668764vkd.7.1569659071784; Sat, 28 Sep 2019 01:24:31 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Sebastian Gniazdowski Date: Sat, 28 Sep 2019 10:21:48 +0200 Message-ID: Subject: Re: print_exit_value unset in an scheduled function, yet still active To: Bart Schaefer Cc: Zsh hackers list Content-Type: text/plain; charset="UTF-8" On Thu, 26 Sep 2019 at 21:49, Bart Schaefer wrote: > If the question instead is "why did printexitvalue become unset inside > the function": It's always turned off on entry to a function, so that > only the exit value of the function itself will later be printed, > exactly as happened here. Thanks, that was the question. -- Sebastian Gniazdowski News: https://twitter.com/ZdharmaI IRC: https://kiwiirc.com/client/chat.freenode.net:+6697/#zplugin Blog: http://zdharma.org