From: Oliver Kiddle <email@example.com>
To: Bart Schaefer <firstname.lastname@example.org>
Cc: Zsh hackers list <email@example.com>
Subject: Re: [PATCH 1/3] Extended ksh compatibility: namespace parameter syntax
Date: Sun, 05 Mar 2023 23:24:57 +0100 [thread overview]
Message-ID: <52850-1678055097.553101@HAUa.4aGe.fmcC> (raw)
Bart Schaefer wrote:
> Assignment should be possible.
> % .foo.bar=something
There must be an off-by-one error in a check:
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.
next prev parent reply other threads:[~2023-03-05 22:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-27 3:56 Bart Schaefer
2023-03-05 9:10 ` Oliver Kiddle
2023-03-05 9:57 ` Sebastian Gniazdowski
2023-03-05 20:20 ` Bart Schaefer
2023-03-05 21:11 ` Bart Schaefer
2023-03-05 20:16 ` Bart Schaefer
2023-03-05 22:24 ` Oliver Kiddle [this message]
2023-03-05 22:42 ` Bart Schaefer
2023-05-20 2:05 ` Phil Pennock
2023-05-20 6:54 ` Bart Schaefer
2023-05-20 17:32 ` Phil Pennock
2023-05-22 2:36 ` Mikael Magnusson
2023-05-22 4:35 ` Bart Schaefer
2023-05-22 21:02 ` Phil Pennock
2023-05-24 15:57 ` Oliver Kiddle
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).