From: Sebastian Gniazdowski <firstname.lastname@example.org>
To: Bart Schaefer <email@example.com>
Cc: Zsh hackers list <firstname.lastname@example.org>
Subject: Re: Reserved namespaces
Date: Sat, 11 Mar 2023 10:00:36 +0000 [thread overview]
Message-ID: <CAKc7PVBKeBprkqnfEbtpLmPyFUZNrBw9qe3cC+YfUU5GUYjkemail@example.com> (raw)
I'm not fully following, but is this about adding namespace.*
prefixes? Like zle.CURSOR, for example?
On Sat, 11 Mar 2023 at 04:56, Bart Schaefer <firstname.lastname@example.org> wrote:
> On Thu, Mar 9, 2023 at 9:13 PM Bart Schaefer <email@example.com> wrote:
> > We're suggesting something like
> > .zle.layout=$'\n\n\n\n\n\n\n\n\n\n\n\n\n\n etc etc'
> > and then the spdist function would read the value of that variable.
> There are at least 8 existing parameters that could be mapped into a
> "zle" namespace:
> There are a couple of dozen more like BUFFER and CURSOR that could be
> in "zle" but might fit better in a "widget" namespace. Of course it
> would be a while before we could retire the existing names, and
> because most of those variables act like locals there's less benefit
> to isolating them.
> It occurs to me that the CORRECT options and their behavior do not
> depend on ZLE being active, so it might not be appropriate to put
> keyboard layouts in that namespace. There are also the parameters
> CORRECT_IGNORE and CORRECT_IGNORE_FILE to consider. Reserving
> "correct" as a namespace feels odd as well, but I think mostly because
> it can be used as both a verb and an adjective. Other ideas?
> Other namespaces to reserve? For example there are a number of
> variables starting with "zsh" though again there'd be a long period of
next prev parent reply other threads:[~2023-03-11 10:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-11 4:56 Bart Schaefer
2023-03-11 10:00 ` Sebastian Gniazdowski [this message]
2023-03-11 19:47 ` Bart Schaefer
2023-03-12 9:24 ` Sebastian Gniazdowski
2023-03-12 13:54 ` Eric Cook
2023-03-12 16:46 ` Sebastian Gniazdowski
2023-03-12 19:24 ` Bart Schaefer
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).