Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
RE: PATCH: Re: pws-19: compinstall should build absolute paths
- X-seq: zsh-workers 6373
- From: "Andrej Borsenkow" <borsenkow.msk@xxxxxx>
- To: "Bart Schaefer" <schaefer@xxxxxxxxxxxxxxxxxxxxxxx>, "ZSH workers mailing list" <zsh-workers@xxxxxxxxxxxxxx>
- Subject: RE: PATCH: Re: pws-19: compinstall should build absolute paths
- Date: Mon, 31 May 1999 10:41:12 +0400
- Importance: Normal
- In-reply-to: <990529103000.ZM7564@xxxxxxxxxxxxxxxxxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxxxxxx; run by ezmlm
> I'm not entirely certain that using absolute paths is the best thing here;
> I worry about things like NFS filesystems that don't have the same mount
> points everywhere. But I can't think of anything better.
>
I am not sure, that compinstall can take in account all possible
configurations. In case of NFS mounted HOME (probably, the most common
case) - I always used ``~/...'' - that should be portable even if HOME
changes.
> +if [[ ${~_ci_fdir} != /* ]]; then
> + _ci_fdir=$(cd $_ci_fdir;builtin pwd)
> +fi
>
> # Check if this is in fpath already, else put it there (with ~'s
> expanded).
> _ci_f=${~_ci_fdir}
>
Ehh ... but at this point _ci_fdir is an absolute path ... and starts with
``/'' ... so _ci_f is set to some directory in HOME instead to _ci_fdir, is
not it?
/andrej
Messages sorted by:
Reverse Date,
Date,
Thread,
Author