From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: zsh-workers@zsh.org
Subject: Re: [PATCH] sh/ksh init: don't initialise lowercase parameters
Date: Fri, 31 Jan 2020 04:17:18 +0000 [thread overview]
Message-ID: <20200131041718.0b31056c@tarpaulin.shahaf.local2> (raw)
In-Reply-To: <CAH+w=7aya1dK8OxTaDsaJNavfamVbhXJtgp53YJwhgKVbJN8fA@mail.gmail.com>
Bart Schaefer wrote on Wed, 29 Jan 2020 16:00 -0600:
> On Wed, Jan 29, 2020, 3:36 PM Daniel Shahaf <d.s@daniel.shahaf.name> wrote:
>
> >
> > I see. Yes, we can bless $HISTCHARS as the preferred spelling for
> > native mode and keep $histchars for csh compatibility…but 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.
Why does HISTCHARS need to be available in sh/ksh modes?
About $signals, it's too late to change zsh mode special parameters to
uppercase (e.g., $path). Perhaps we should use uppercase for any new
parameters we introduce going forward, but that's another conversation.
Cheers,
Daniel
next prev parent reply other threads:[~2020-01-31 4:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20200128152042eucas1p20cbbeeb7cbe5f6abff08128ba8792661@eucas1p2.samsung.com>
2020-01-28 15:19 ` Martijn Dekker
2020-01-28 15:26 ` Peter Stephenson
2020-01-28 15:45 ` Martijn Dekker
2020-01-29 8:49 ` Daniel Shahaf
2020-01-29 18:36 ` Bart Schaefer
2020-01-29 21:35 ` Daniel Shahaf
2020-01-29 22:00 ` Bart Schaefer
2020-01-31 4:17 ` Daniel Shahaf [this message]
2020-01-31 4:31 ` Bart Schaefer
2020-02-01 9:42 ` Daniel Shahaf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200131041718.0b31056c@tarpaulin.shahaf.local2 \
--to=d.s@daniel.shahaf.name \
--cc=zsh-workers@zsh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).