From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25454 invoked by alias); 29 Apr 2018 18:43:09 -0000 Mailing-List: contact zsh-users-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Users List List-Post: List-Help: List-Unsubscribe: X-Seq: 23370 Received: (qmail 14921 invoked by uid 1010); 29 Apr 2018 18:43:09 -0000 X-Qmail-Scanner-Diagnostics: from mail-ot0-f180.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(74.125.82.180):SA:0(-1.9/5.0):. Processed in 2.78669 secs); 29 Apr 2018 18:43:09 -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,FREEMAIL_FROM, HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS,T_DKIM_INVALID autolearn=ham autolearn_force=no version=3.4.1 X-Envelope-From: sgniazdowski@gmail.com X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=AbVTwre+fX1Otl19hfLjgfPE7v+3KgCh6NsX2n7sozY=; b=JSayHnE4IF8SdFr4uDJ7me8QYM2BAFQ4UV7nfrrdHDVxvrWyqCOiesguGlca78VDEB LdnVvyGNehpxkQ6Cu6Xi9Vml68oJ4JU93XSk3mjpHLxLL3EWlbQE1OyW0Tz9M/NiLcs7 JuubBt2NTF0dLcbJPmrVFGEH4oo+b5/bG9XYE/CmGGzbHLiEN2wwXljydHq6DrIw8SKm wU3QGa9j8rw/EiQWkK+Dcy/5pfwqIFnK3Bb2l0LRqr1qq5K7ypOYV7OgoOE7DU87PDB8 wNZzdeP4d5CLFKjEqsXdj/q0ag0bE4aeZSp5uDsQHfxRpD8KAjQ4QB4XkbDJfG9UpvtO EakA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=AbVTwre+fX1Otl19hfLjgfPE7v+3KgCh6NsX2n7sozY=; b=tPJzzQLThVvmoXou7/4eCqsWk+zgbFKdvcUYOFCV70/UkZHBl74lLzLuexjID6c2+5 pa21goz9b2124lI55NjnEfiB1ER4QXNXxH0SSUrFW5A//OteXTzjn3uVVron51zaDXN5 uG24gdgo2hJCsw5ijKHHbB0rlkVgz0VV9IFs0hiFgfN7ri6Vk5SY91kkhPMtBMSPYR28 qD3c6N34UPWKys4PytSAKn+KdCja3FJxOukdo5oXDgWNYmL+VaX8ehh+CDbF8fEcGl7R 8aJx6rF2NoyhHLF14fPwu6euQt4jzRyDF05fOQCX7rQflXl/d49trcVZS8e5lFN8c6GN WPVw== X-Gm-Message-State: ALQs6tB6sb33fLKbKL4J5i3VJL/r5vgQb1oc3ai6917xUhfu6oYQWl9A 9GQ9lsEa3CZt+wvSrRd25zpKvTO0EvB+ZtWHF40= X-Google-Smtp-Source: AB8JxZqfnybuAf4FW2sXCJzGBbwC8vhtRoY3hBkUNP2iN/PIQHTC5b5XzJQuzHktdVfEinjRR4nFjN6iRsFCsDolTV8= X-Received: by 2002:a9d:2c8:: with SMTP id 66-v6mr3032300otl.28.1525027383838; Sun, 29 Apr 2018 11:43:03 -0700 (PDT) MIME-Version: 1.0 From: Sebastian Gniazdowski Date: Sun, 29 Apr 2018 20:42:43 +0200 Message-ID: Subject: Suppress print_exit_value for single function To: Zsh Users Content-Type: multipart/alternative; boundary="0000000000007c8e46056b011b3f" --0000000000007c8e46056b011b3f Content-Type: text/plain; charset="UTF-8" Hello, in a 1-second sched function, I do: __ret=$? ... return $__ret This solves $? malforming by background task. However, for `setopt print_exit_value', this leads to constant "zsh: Exit 1" message, every second. Can I block `setopt print_exit_value' effects for this sched function or to all sched functions in general? I think a feature could be added for this, it looks very reasonable and useful. -- Best regards, Sebastian Gniazdowski --0000000000007c8e46056b011b3f--