Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: PATCH: wrapper functions in modules
- X-seq: zsh-workers 4745
- From: Phil Pennock <phil@xxxxxxxxxxxxxxxxxxxxx>
- To: zsh-workers@xxxxxxxxxxxxxxx
- Subject: Re: PATCH: wrapper functions in modules
- Date: Fri, 11 Dec 1998 06:59:50 +0000
- In-reply-to: <9812100922.AA18305@xxxxxxxxxxxxxxxxx>; from "Peter Stephenson" on Thu 10 Dec 1998 (10:22 +0100)
- Mail-followup-to: zsh-workers@xxxxxxxxxxxxxxx
- Organisation: Organisation? Here? No, over there ---->
- References: <199812100922.KAA03277@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <9812100922.AA18305@xxxxxxxxxxxxxxxxx>
Typing away merrily, Peter Stephenson produced the immortal words:
> And someone pointed out MODULE_PATH is a bit generic for a
> shell-specific variable, you never know what something else is going
> to do with the environment variable.
Environment?
Since MODULE_PATH is only used by zsh and any zsh normall uses .zshenv,
it can be set there. Why pollute the environment needlessly.
The namespace is getting a bit polluted though, yes. Perhaps a few more
variables should start with 'Z', just as 'modload' became 'zmodload'.
And I know that they're local and will just shadow other variables, but
I keep looking at the ZLE special variable like CURSOR and wincing a
little.
A thought:
How about a convention that any special variables, and perhaps commands,
defined by a module should start with that module's name, and a leading
Z or z if the module name doesn't start with a z? Exemptions for
specific overrides such as the files module or where it's just a
modularisation of established naming (sched). But we'd then have zstat,
zexample, etc.
--
--> Phil Pennock ; GAT d- s+:+ a22 C++(++++) UL++++/I+++/S+++/H+ P++@ L+++
E-@ W(+) N>++ o !K w--- O>+ M V !PS PE Y+ PGP+ t-- 5++ X+ R !tv b++>+++ DI+ D+
G+ e+ h* r y?
Messages sorted by:
Reverse Date,
Date,
Thread,
Author