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.0 required=5.0 tests=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 e1c107ba for ; Wed, 19 Feb 2020 19:25:54 +0000 (UTC) Received: (qmail 29087 invoked by alias); 19 Feb 2020 19:25:46 -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: 45477 Received: (qmail 15014 invoked by uid 1010); 19 Feb 2020 19:25:46 -0000 X-Qmail-Scanner-Diagnostics: from mail-yw1-f44.google.com by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.102.2/25725. spamassassin: 3.4.2. Clear:RC:0(209.85.161.44):SA:0(-1.9/5.0):. Processed in 1.946314 secs); 19 Feb 2020 19:25:46 -0000 X-Envelope-From: dana@dana.is 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.161.44 as permitted sender) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=i302wiTtNY2yKBIxm/L5nRrxyAsUZVtszZ8XbamGYtk=; b=Z7Fk7qCHG8PcS8DltNAoNkVBP++W9y2sCCGWjvNWPsA8YUUobtvS5zrFjIshv9sFyb 8JLQJCfRmz07PNS/PweOX5Ixr9KFpo5sOE00dtBiqChJDgLcHs/v61JNDUbl4jbf4IKH auKwuaujVLWyRcwodS7YXgLePzVGQCCUfecp/NF1mIj27i31CKXktL/tIqRBViRL57jG Atx6WobNddcWCSXhfV3FOjRu8/V37lOZHzm5M031urynoC2mf+BdjHRRSXPZoUGXr8aI CJU+lAJUyrwcWEtRog7Yo0k5HeowI08OmScELtRIyOE7cXAkLLLpsZDi3UU4OLQjcOU1 ol0A== X-Gm-Message-State: APjAAAXZk9upOZCZsvOgk+JvS6gIxqCIbnGzp4Xm066T7gEg+/5Iky3I F7/LJDoLQHCImEbjgA7ZsKA68ZCnb7PTbw== X-Google-Smtp-Source: APXvYqzs75EGa3zeUGTKNz+lIF40Tq/uBIC31hMB+drN45lat6tc2qO4frptph9T6wgdc0qqe/3lWA== X-Received: by 2002:a0d:c243:: with SMTP id e64mr22379145ywd.12.1582140311455; Wed, 19 Feb 2020 11:25:11 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) Subject: Re: [BUG] Issue with set built-in in 5.8 (?) From: dana In-Reply-To: <1582105061.6506.5.camel@samsung.com> Date: Wed, 19 Feb 2020 13:25:08 -0600 Cc: Zsh hackers list , Daniel Shahaf Content-Transfer-Encoding: quoted-printable Message-Id: References: <6908034E-BC9E-41B3-8457-111F275AF3A7@dana.is> <20200217090236.17a82c53@tarpaulin.shahaf.local2> <75380C1D-ED7C-46A8-AB57-5FC9892581A5@dana.is> <1582105061.6506.5.camel@samsung.com> To: Peter Stephenson X-Mailer: Apple Mail (2.3445.104.11) On 19 Feb 2020, at 03:37, Peter Stephenson = wrote: > Tracing through POSIX to get an exact answer can be a bit of a pain I found it: = https://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#= tag_18_08_01 When encountering a 'special built-in utility error', a non-interactive = shell 'shall exit'. The documentation for the set built-in doesn't seem to anticipate any errors besides those related to option-parsing, but i = guess the 'letter of the law' is clear; if we were going to follow it strictly, = we'd leave set the way it is. idk. On balance, maybe we should just let it be until someone complains = (which probably won't happen). Otherwise, with all of the weird variables in = this code path, we could be tinkering with it until next February... dana