From: Oliver Kiddle <opk@thoth.u-net.com>
To: Andrej Borsenkow <Andrej.Borsenkow@mow.siemens.ru>
Cc: Zsh hackers list <zsh-workers@sunsite.auc.dk>
Subject: Re: PATCH: pws-25: saving old shell functions from overwriting
Date: Fri, 09 Jul 1999 12:05:21 +0100 [thread overview]
Message-ID: <3785D771.AA06CD9A@thoth.u-net.com> (raw)
In-Reply-To: <000601bec9f6$1ac74f80$21c9ca95@mow.siemens.ru>
Andrej Borsenkow wrote:
> I just realised, that it may be better to save the whole directory (in
> functions.old probably). Moving files to *.old has potential problem, that if
> anybody autloads whole $fpath, he will suddenly get a lot of fn.old functions.
One thing which I would like changed is for compinit to add directories
to the end of $fpath instead of the beginning. This way, I can override
the zsh supplied completions with my own. By putting them in a different
directory, I don't have to worry about them being overwritten when I
install a new zsh. I would also be tempted to prefix the zsh completion
directories with a 'Z' so that compinit would put other directories in
/usr/local/share/zsh/functions (such as one named 'Local') first in
$fpath.
A result of the latest compinstall seems to be that I get the Core
directory duplicated in my $fpath. The compinstall created .zshrc adds
it so that it can autoload compinit and compinit then adds it in again.
Oliver Kiddle
next prev parent reply other threads:[~1999-07-09 11:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-04 13:25 Peter Stephenson
1999-07-09 10:30 ` Andrej Borsenkow
1999-07-09 11:05 ` Oliver Kiddle [this message]
1999-07-09 11:15 ` Andrej Borsenkow
1999-07-09 12:25 ` PATCH: pws-25: old shell functions again Peter Stephenson
1999-07-09 13:00 ` Peter Stephenson
1999-07-09 16:23 ` Peter Stephenson
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=3785D771.AA06CD9A@thoth.u-net.com \
--to=opk@thoth.u-net.com \
--cc=Andrej.Borsenkow@mow.siemens.ru \
--cc=zsh-workers@sunsite.auc.dk \
/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).