From: Sweth Chandramouli <sweth@astaroth.nit.gwu.edu>
To: zsh-users@math.gatech.edu
Subject: Re: path/PATH function
Date: Fri, 21 Nov 1997 14:23:56 -0500 [thread overview]
Message-ID: <19971121142356.16832@astaroth.nit.gwu.edu> (raw)
In-Reply-To: <971119082751.ZM574@candle.brasslantern.com>; from Bart Schaefer on Wed, Nov 19, 1997 at 08:27:51AM -0800
On Wed, Nov 19, 1997 at 08:27:51AM -0800, Bart Schaefer wrote:
> This "feature" is restricted at present to a few pairs of variables that are
> hardwired at compile time. They include:
>
> CDPATH cdpath
> FPATH fpath
> MAILPATH mailpath
> MANPATH manpath
> PATH path
maybe the documentation i have isn't that complete, but all i could find
in the manpage for zshparam is the fact that the variables like cdpath and path
exist and are "special" varaibles; there isn't any mention of how they are
mapped on to their capitalized counterparts. my next question, then, is if
these do, in fact, work the way i surmised (that is, they remove redundancies
and map their colon-delimited versions onto the capitalized equivalent
variable). also, what exactly is the format for defining them? is it just
paren-enclosed, space-delimited lists?
> You might also wish to look into `typeset -U` which causes an array to
> remove all non-unique elements from itself. A function to test whether
> any given directory is already in your path shouldn't be necessary.
the version of typeset on my system doesn't seem to support this option
(or at least, the man page doesn't mention it). typeset doesn't return an error
if i try to use the -U switch, however; could someone summarize the syntax so i
could see if it is, in fact, implemented?
tia,
sweth.
next prev parent reply other threads:[~1997-11-21 19:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-11-19 15:37 Sweth Chandramouli
1997-11-19 16:20 ` Bruce Stephens
1997-11-19 16:27 ` Bart Schaefer
1997-11-21 19:23 ` Sweth Chandramouli [this message]
1997-11-24 10:04 ` Bruce Stephens
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=19971121142356.16832@astaroth.nit.gwu.edu \
--to=sweth@astaroth.nit.gwu.edu \
--cc=zsh-users@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).