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 a058783c for ; Wed, 29 Jan 2020 22:01:01 +0000 (UTC) Received: (qmail 9479 invoked by alias); 29 Jan 2020 22:00:56 -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: 45359 Received: (qmail 24358 invoked by uid 1010); 29 Jan 2020 22:00:56 -0000 X-Qmail-Scanner-Diagnostics: from mail-lf1-f65.google.com by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.102.1/25703. spamassassin: 3.4.2. Clear:RC:0(209.85.167.65):SA:0(-1.9/5.0):. Processed in 2.02077 secs); 29 Jan 2020 22:00:56 -0000 X-Envelope-From: schaefer@brasslantern.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.167.65 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:references:in-reply-to:from:date :message-id:subject:to:cc; bh=l1ljCb8/XkyFlc/TeFlWxLA9C+pdwIgDMOLboEh4PeU=; b=RuK6KlXqpDSXkUdmN6gdfv0khUvACOMXZYXH6GeA5jUGRHzsjGpVyInDz8XEK2qJQk PL2jx3od4R5etkmZp1NYRvcGPhA9fxculgtorakZIfs+f1HZWszp42FD4yZ66K31raiz UvzVhLyTQ1Ye/R79gPFRaDSjiUirCMYZWpkw6JRJK80zwupRjVuc++sKgyTKihe6gi3v 4kHXQIdPftkBMQfCcOeymEV6amFfFW+g+rPxUGniak6IPxuDtfSgOr2ImcDniX4CFbva KHDHWnzd40uKx7IPj7PW8r1dBMd3G0GzuM8jP7Hbl8xsHr6++aqMY4j+G2VsTeodayEM d8uw== X-Gm-Message-State: APjAAAXx2nWwgkmWNCOCchcLPdMpK8MYTHj7qWZOj44ZEPZn8HMsPvSs eNdh6DgfZ5c45iowCbjqNMGpyqxO2rwjQj2m558njQ== X-Google-Smtp-Source: APXvYqyDEr79rR+ePvBDYrExggRbrvm/CvJc5GGYDzXUBBHMhnRFUDPb7e8OQp14gt+C8OmX4vTpNTSMYP0xFhNFrBg= X-Received: by 2002:ac2:55a8:: with SMTP id y8mr754179lfg.117.1580335219356; Wed, 29 Jan 2020 14:00:19 -0800 (PST) MIME-Version: 1.0 References: <20200129084948.GA9843@tarpaulin.shahaf.local2> <20200129213530.428f2c76@tarpaulin.shahaf.local2> In-Reply-To: <20200129213530.428f2c76@tarpaulin.shahaf.local2> From: Bart Schaefer Date: Wed, 29 Jan 2020 16:00:06 -0600 Message-ID: Subject: Re: [PATCH] sh/ksh init: don't initialise lowercase parameters To: Daniel Shahaf Cc: Zsh hackers list , Martijn Dekker Content-Type: multipart/alternative; boundary="000000000000604aea059d4e77ee" --000000000000604aea059d4e77ee Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wed, Jan 29, 2020, 3:36 PM Daniel Shahaf wrote: > > I see. Yes, we can bless $HISTCHARS as the preferred spelling for > native mode and keep $histchars for csh compatibility=E2=80=A6but doesn't= this > imply that we should add a $SIGNALS variable (and possibly deprecate > $signals)? > No, I was not suggesting any change to native mode. I'm merely saying that if we can't have the lower-case version in sh/ksh modes, we need the upper case one there. $signals is strictly informational, so it doesn't need to be present in those modes at all, but HISTCHARS is writable and controls features of history. --000000000000604aea059d4e77ee--