From: Felix Rosencrantz <f_rosencrantz@yahoo.com>
To: zsh-workers <zsh-workers@sunsite.auc.dk>
Subject: Re: PATCH: Add jobdirs association to parameter module
Date: Mon, 13 Dec 1999 22:39:47 -0800 (PST) [thread overview]
Message-ID: <19991214063947.8893.qmail@web1305.mail.yahoo.com> (raw)
Peter Stephenson wrote:
> What is this chunk for? It's going to mean the parameters are permanently
> stuck in the parameter table, even if the module is unloaded, and if the
> module is reloaded the parameters won't be. Sven just fixed this a week or
> so ago.
Sigh... I'm terribly embarrassed. I made the change more than a week ago, and
wanted to try it before sending it. Then I made the patch with the latest
version of parameter.c rather than the original version.
> 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.
I agree, there is a problem with the name space pollution. I would suggest
that zsh is included in the name, like ${.zshparam.jobdirs} or
${.zsh.param.jobdirs} (I'm not familiar with ksh). I think if we say that
parameters beginning with zsh are reserved for future expansion, then there is
room for expansion without stepping on people's toes.
-FR.
__________________________________________________
Do You Yahoo!?
Thousands of Stores. Millions of Products. All in one place.
Yahoo! Shopping: http://shopping.yahoo.com
next reply other threads:[~1999-12-14 6:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-14 6:39 Felix Rosencrantz [this message]
-- 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 9:26 Sven Wischnowsky
1999-12-14 10:27 ` Zefram
1999-12-14 12:55 ` Andrej Borsenkow
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=19991214063947.8893.qmail@web1305.mail.yahoo.com \
--to=f_rosencrantz@yahoo.com \
--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).