From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26683 invoked by alias); 4 May 2018 16:30:11 -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: 23384 Received: (qmail 25338 invoked by uid 1010); 4 May 2018 16:30:10 -0000 X-Qmail-Scanner-Diagnostics: from mail-oi0-f54.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.218.54):SA:0(-1.9/5.0):. Processed in 3.032045 secs); 04 May 2018 16:30:10 -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,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,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:in-reply-to:references:from:date:message-id:subject:to :cc; bh=ji+pwNp8NFM8TL+GkH1eLyQhooRiTwQXyVU1hXkbnSc=; b=tpJwhed+vZ4Uv4yqMXhKZbWqUdeUL5WXd5CFG/dG1RUjbCZkkmvi/0QmLaNV5u5on2 qmCHGubNrp/WH7XaU8jfoWQ7NejK1ev3290oVEaEOBJvyCi5siEmV9Qdx+PjzozeSnYL hXNigr4hJupOrreQI0YaBIriVdyJQW7b0DHp884Ts7PGLoNWzC6eWxscrxQBG23SgdWX rbwSdPcH2stdNxShFrPWjzvG0vm9FxyccPmiaCRT+ioudRhAaoftdXpjSdmal+hhBTPe 2R8HKkL+I50M5XhkQ+EBrP4T4t41DIY2/XQjbyAeB+5CNd4kN4lKKs943v+4TuokSCGm uCgg== 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=ji+pwNp8NFM8TL+GkH1eLyQhooRiTwQXyVU1hXkbnSc=; b=WSkdWIPxPQ58MN7bkZvKP59upVK8BRUP9uQ7XxstPJjWDBFD6wQCBL86gr+9ScZ8BG GpJx2nc0gHK/ipNVQ7ls4n30eIxlWZ6WsFRjst2b7x29KH4MadpfmN9VNo2+DLHhEvTz f+p79iaMc4BRNB6Og+lWOOfQs2G+GeEJdUGvJ9ho2pcInxuysg82AMBu2ekyAvv28prJ TLb89jhO841DuJMN7DX8DcpzplWd3FkcmLfzhRcIxxbJeLtYk46vLOliqlNR1nefBrPi z9FB/7shGETvIFJAgogtDd/Oox/BSagvrzmMXoNNP+XzNBtBiLefpcDvak2lVXgR10K2 nwug== X-Gm-Message-State: ALQs6tAb0Z5hnFQHQi9vJPYraPfi8BoFhTdF0qD3gPeeNiWYK4v38lQW DMXKinenRBOZQ1f4+b+wnxHxQkEylaTm4uLXqxpKPA== X-Google-Smtp-Source: AB8JxZrmhRxQEVPUYYGCIlCubzSZ6plYwzRqFoKLepyPd8Yods6oYYWgV2kR7sT6DfSvL/ZE1zgyV1AA2/QItGcL1tI= X-Received: by 2002:aca:3ec3:: with SMTP id l186-v6mr10645939oia.231.1525451405037; Fri, 04 May 2018 09:30:05 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <180429120250.ZM3463@torch.brasslantern.com> References: <180429120250.ZM3463@torch.brasslantern.com> From: Sebastian Gniazdowski Date: Fri, 4 May 2018 18:29:44 +0200 Message-ID: Subject: Re: Suppress print_exit_value for single function To: Bart Schaefer Cc: Zsh Users Content-Type: multipart/alternative; boundary="0000000000001e95e0056b63d53c" --0000000000001e95e0056b63d53c Content-Type: text/plain; charset="UTF-8" On 29 April 2018 at 21:02, Bart Schaefer wrote: > On Apr 29, 8:42pm, Sebastian Gniazdowski wrote: > } > } Can I block `setopt print_exit_value' effects for this sched function or > to > } all sched functions in general? > > You can always > > setopt localoptions no_print_exit_value > Can it be true that the C array of structures, `funcstack': typedef struct funcstack *Funcstack; will have something distinct for function ran from sched? The print_exit_value code would be then able to easily check for this distinct trait. I think all this is worth doing, not for aesthetics aspect, but to allow background functions to maintain $? unchanged (and e.g. repeat erroneous exit code). It is a poor situation currently, e.g. syntax highlighting runs after key press and $? is lost, it cannot be directly used at command line. Lets do something to address this, at least for sched. -- Best regards, Sebastian Gniazdowski --0000000000001e95e0056b63d53c--