From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: PATCH: Add jobdirs association to parameter module
Date: Tue, 14 Dec 1999 10:26:30 +0100 (MET) [thread overview]
Message-ID: <199912140926.KAA29080@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: Peter Stephenson's message of Mon, 13 Dec 1999 21:31:10 +0000
Peter Stephenson wrote:
> ...
>
> It's a shame we didn't have more specific names for parameters, since the
> parameter module is quiet heavily used in completion, so there is quite a
> lot of name space pollution. They stop being special if made local, but
> it's still a problem. The ksh mechanism ${.param.jobdirs} would be
> excellent for this.
When I last added parameters to it, I asked if I should rename them to
`z...' -- we decided against that.
I agree that it would be nice to have this cleaner so I just tried to
allow dots in parameter names by simply adding `typtab['.'] |= IIDENT;'
to inittyptab(). It /seems/ to work, only `$.a.b' doesn't (but
`${.a.b}' does), haven't found the place where it fails yet -- mainly
because I haven't really searched for it.
So, can anyone think of a good reason why we shouldn't do that? Like
Peter (at least I think Peter meant that) I prefer the solution with
the dots over the solution with just prepending a `z' before every
parameter name. It's clean, it's extensible...
Bye
Sven
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next reply other threads:[~1999-12-14 9:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-14 9:26 Sven Wischnowsky [this message]
1999-12-14 10:27 ` Zefram
1999-12-14 12:55 ` Andrej Borsenkow
-- strict thread matches above, loose matches on Subject: below --
1999-12-14 13:33 Sven Wischnowsky
1999-12-14 10:34 Sven Wischnowsky
1999-12-14 6:39 Felix Rosencrantz
1999-12-13 5:55 Felix Rosencrantz
1999-12-13 21:31 ` Peter Stephenson
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=199912140926.KAA29080@beta.informatik.hu-berlin.de \
--to=wischnow@informatik.hu-berlin.de \
--cc=zsh-workers@sunsite.auc.dk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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
https://git.vuxu.org/mirror/zsh/
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).