Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
PATCH: Re: pws-19: compinstall should build absolute paths
- X-seq: zsh-workers 6369
- From: "Bart Schaefer" <schaefer@xxxxxxxxxxxxxxxxxxxxxxx>
- To: "ZSH workers mailing list" <zsh-workers@xxxxxxxxxxxxxx>
- Subject: PATCH: Re: pws-19: compinstall should build absolute paths
- Date: Sat, 29 May 1999 10:30:00 +0000
- In-reply-to: <000201bea852$585d80a0$21c9ca95@xxxxxxxxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxxxxxx; run by ezmlm
- References: <000201bea852$585d80a0$21c9ca95@xxxxxxxxxxxxxx>
On May 27, 7:05pm, Andrej Borsenkow wrote:
} Subject: pws-19: compinstall should build absolute paths
}
} source .zsh.d/compinstall
}
} that resulted in relative paths placed in .zshrc:
}
} . .zsh.d/compinit -f .zsh.d -d
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.
Index: Completion/Core/compinstall
===================================================================
@@ -141,6 +141,9 @@
else
print "Keeping existing completion directiory $_ci_fdir"
fi
+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}
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Messages sorted by:
Reverse Date,
Date,
Thread,
Author