Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: ISP OS upgrade = zsh function-files not found
- X-seq: zsh-users 13980
- From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- To: zsh-users@xxxxxxxxxx
- Subject: Re: ISP OS upgrade = zsh function-files not found
- Date: Sat, 28 Mar 2009 08:25:11 -0700
- In-reply-to: <20090327194351.GA17608@xxxxxxxxx>
- Mailing-list: contact zsh-users-help@xxxxxxxxxx; run by ezmlm
- References: <20090326183157.GA2269@xxxxxxxxx> <090326220427.ZM9826@xxxxxxxxxxxxxxxxxxxxxx> <20090327060332.GA24817@xxxxxxxxx> <090327001536.ZM10196@xxxxxxxxxxxxxxxxxxxxxx> <20090327194351.GA17608@xxxxxxxxx>
On Mar 27, 3:43pm, Russell Hoover wrote:
}
} Meanwhile I've commented-out this line in my .zshenv:
} #export FPATH=/usr/local/share/zsh/4.3.9/functions/:$HOME/.zfunc
Ah, yes, that would be somewhat important.
FPATH and fpath are "tied" together like PATH and path. If you assign
to the FPATH variable, you're stepping on the value of fpath, which
explains the whole situation.
There's no reason to assign to FPATH instead of to fpath, either one
will copy its value to the other (appropriately splitting or joining
with colons as needed). So if you want to use FPATH for some reason,
FPATH+=:$HOME/.zfunc
There's also really no reason to export FPATH, because it's not used
by any program other than zsh and zsh will always reset it on startup
(and you can't combine += syntax and "export" in one statement).
Messages sorted by:
Reverse Date,
Date,
Thread,
Author