From: Bruce Stephens <B.Stephens@isode.com>
To: ZSH workers mailing list <zsh-workers@sunsite.auc.dk>
Subject: Re: Reading completion manual
Date: 02 Mar 1999 17:09:40 +0000 [thread overview]
Message-ID: <vbzp5vu8bv.fsf@snake.isode.com> (raw)
In-Reply-To: "Andrej Borsenkow"'s message of "Tue, 2 Mar 1999 19:52:50 +0300"
"Andrej Borsenkow" <borsenkow.msk@sni.de> writes:
> - use new option character (do we have one free?)
> - implement long options
> - (really wild one) implement name spaces.
>
> I'd like the last one, but it is probably impossible. A command name
> may have any character, so there is simply no char that can be
> (safely) used as delimiter. So, long options is probably the only
> viable solution. And quite useful in other places as well.
I thought namespaces had been discussed before? What's the objection
to allowing "." in variable names, and regarding it as a component
delimiter in function/command names? Hmm, this isn't a good idea; I
quite often use things like "cp $i $i.bak" and stuff. I wonder how
ksh93 copes with this? Maybe you have to predeclare name
spaces---that would be acceptable and sufficient, I should think.
I seem to remember that ksh93 supports this kind of use, and the
defines a number of special components which, if set, change the way
that variable assignment and things get done.
(So if you have a function foo.WRITE, then that gets called when you
try to write to foo. Something like that, anyway. A better interface
might be to copy the Perl tie ideas---allowing special associative
arrays and things as Bart suggested; you wouldn't need name spaces for
this, of course.)
next prev parent reply other threads:[~1999-03-02 17:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-02 16:52 Andrej Borsenkow
1999-03-02 17:09 ` Bruce Stephens [this message]
1999-03-02 17:20 ` Andrej Borsenkow
1999-03-02 17:29 ` Bruce Stephens
1999-03-03 9:29 Sven Wischnowsky
1999-03-04 5:50 ` Bart Schaefer
1999-03-03 13:34 Sven Wischnowsky
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=vbzp5vu8bv.fsf@snake.isode.com \
--to=b.stephens@isode.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).