zsh-users
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@brasslantern.com>
To: Sweth Chandramouli <sweth@astaroth.nit.gwu.edu>,
	zsh-users@math.gatech.edu
Subject: Re: path/PATH function
Date: Wed, 19 Nov 1997 08:27:51 -0800	[thread overview]
Message-ID: <971119082751.ZM574@candle.brasslantern.com> (raw)
In-Reply-To: <19971119103756.34168@astaroth.nit.gwu.edu>

On Nov 19, 10:37am, Sweth Chandramouli wrote:
} Subject: path/PATH function
}
} 	i long time ago, i wrote a quick function to take a list of
} space-delimited dirs, check to see if each one was currently in my path,
} and if  not, add it.
} 
[describes cdpath mapping onto CDPATH]
} 
} 	i'm assuming that this is some sort of zsh path-addition option, along 
} the lines of what i had created; i couldn't find any reference to it in the
} FAQ,  however, other than a note in the wish-list for users to "be able to
} create  their own foopath/FOOPATH array/path combinations."  does anyone
} know anything  more about this feature?

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

These are documented in `man zshparam` and in the info files.  The remark
in the FAQ refers to the desire to provide arbitrary user-defined pairs
of variables that behave this way.

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.

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com


  parent reply	other threads:[~1997-11-19 16:58 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 [this message]
1997-11-21 19:23   ` Sweth Chandramouli
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=971119082751.ZM574@candle.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --cc=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).