Re: Reserved namespaces

[Sebastian Gniazdowski <sgniazdowski@gmail.com>]

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 <schaefer@brasslantern.com> wrote:
>
> On Thu, Mar 9, 2023 at 9:13 PM Bart Schaefer <schaefer@brasslantern.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:
>
> zle_bracketed_paste
> zle_highlight
> ZLE_LINE_ABORTED
> ZLE_RECURSIVE
> ZLE_STATE
>
> ZLE_REMOVE_SUFFIX_CHARS
> ZLE_RPROMPT_INDENT
> ZLE_SPACE_SUFFIX_CHARS
>
> 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
> overlap.
>


-- 
Best regards,
Sebastian Gniazdowski