Re: [PATCH 1/3] Extended ksh compatibility: namespace parameter syntax

[Oliver Kiddle <opk@xxxxxxx>]

Bart Schaefer wrote:
> Assignment should be possible.
>
> % .foo.bar=something

There must be an off-by-one error in a check:

  a.b=c
  zsh: command not found: a.b=c

But it does work for anything longer than one character in the first
component such as foo.bar. I was confused when this didn't work for me
this morning because I was sure I had done some tests of assignments.

> Yes, I've been working on doc and tests.  One difference that I want
> to add is that parameters starting with "." are omitted from the
> default output of "set" and "typeset" (with no arguments).

Yes, that would be good.

> Given zsh dynamic scoping, it works reasonably well to have ZLE
> variables behave like locals -- you can't access them outside a shell
> function (widget) anyway.  If there were controls we wanted to expose
> higher up -- such as, perhaps, fiddling with keymaps without having to
> invoke "zle -K" or "bindkey -[eva]") then yes, a ".zle" namespace
> could be handy.

I was thinking of things like zle_bracketed_paste, zle_highlight and
ZLE_RPROMPT_INDENT which it'd be nice to have more hidden.

Oliver