help / color / mirror / code / Atom feed
From: Eric Cook <llua@gmx.com>
To: zsh-workers@zsh.org
Subject: Re: Reserved namespaces
Date: Sun, 12 Mar 2023 09:54:10 -0400	[thread overview]
Message-ID: <545a4073-0458-3ba2-186a-230334bfdaa8@gmx.com> (raw)
In-Reply-To: <CAKc7PVC_jP7PCbf+bXhQ+oSw_6nJXG1kG+f1tEy2AAxHkzEJMA@mail.gmail.com>

On 3/12/23 05:24, Sebastian Gniazdowski wrote:
> yes, nice. I would go for zle.CURSOR, it's looking worse than zle.cursor,
> however it follows upcase↔scalar convention.
That convention, as noted by bart, was to avoid name collisions with user variables.
Something that wouldn't be an issue with this, from what i understand.

  reply	other threads:[~2023-03-12 13:54 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 [this message]
2023-03-12 16:46       ` Sebastian Gniazdowski
2023-03-12 19:24         ` Bart Schaefer

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=545a4073-0458-3ba2-186a-230334bfdaa8@gmx.com \
    --to=llua@gmx.com \
    --cc=zsh-workers@zsh.org \


* 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).