From: Phil Pennock <phil@athenaeum.demon.co.uk>
To: zsh-workers@math.gatech.edu
Subject: Re: PATCH: wrapper functions in modules
Date: Fri, 11 Dec 1998 06:59:50 +0000 [thread overview]
Message-ID: <19981211065950.12315@athenaeum.demon.co.uk> (raw)
In-Reply-To: <9812100922.AA18305@ibmth.df.unipi.it>; from "Peter Stephenson" on Thu 10 Dec 1998 (10:22 +0100)
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?
next prev parent reply other threads:[~1998-12-11 7:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-12-10 9:22 Sven Wischnowsky
1998-12-10 9:22 ` Peter Stephenson
1998-12-11 6:59 ` Phil Pennock [this message]
1998-12-11 8:46 ` Peter Stephenson
-- strict thread matches above, loose matches on Subject: below --
1998-12-10 10:28 Sven Wischnowsky
1998-12-09 14:44 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=19981211065950.12315@athenaeum.demon.co.uk \
--to=phil@athenaeum.demon.co.uk \
--cc=zsh-workers@math.gatech.edu \
/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).