From: Sebastian Gniazdowski <email@example.com>
To: Bart Schaefer <firstname.lastname@example.org>
Cc: Zsh hackers list <email@example.com>
Subject: Re: Reserved namespaces
Date: Sun, 12 Mar 2023 16:46:09 +0000 [thread overview]
Message-ID: <CAKc7PVD+-ft3a-D_Y=_cYNf3C+xGBt8mi0Rzf5eXZAPFfcJFBA@mail.gmail.com> (raw)
Will be creating own namespaces allowed? It would be good, for
example, to create `my_plugin` namespace, instead of hash (typeset -gA
MyPlugin, e.g.), to store plugin's state. It would also serve as a
quite good poor man's nested vars.
On Sun, 12 Mar 2023 at 09:24, Sebastian Gniazdowski
> yes, nice. I would go for zle.CURSOR, it's looking worse than zle.cursor,
> however it follows upcase↔scalar convention.
> On Sat, 11 Mar 2023 at 19:47, Bart Schaefer <firstname.lastname@example.org> wrote:
> > On Sat, Mar 11, 2023 at 2:01 AM Sebastian Gniazdowski
> > <email@example.com> wrote:
> > >
> > > I'm not fully following, but is this about adding namespace.*
> > > prefixes? Like zle.CURSOR, for example?
> > Yes, though it would be ".zle.CURSOR" or possibly just ".zle.cursor"
> > since we'd no longer have to worry as much about name collisions with
> > users' variables.
> Best regards,
> Sebastian Gniazdowski
next prev parent reply other threads:[~2023-03-12 16:46 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
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 [this message]
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).