From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: zsh-workers@sunsite.dk
Subject: Re: Distributed Completion/ structure and compinit
Date: Thu, 26 Apr 2001 08:10:35 +0000 [thread overview]
Message-ID: <1010426081035.ZM12445@candle.brasslantern.com> (raw)
In-Reply-To: <200104260711.JAA04111@beta.informatik.hu-berlin.de>
On Apr 26, 9:11am, Sven Wischnowsky wrote:
} Subject: Re: Distributed Completion/ structure and compinit
}
} Bart Schaefer wrote:
}
} > The doc for compinit says:
} >
} > subdirectories of the directory where Base is to the path: this allows
} > the functions to be in the same format as in the zsh source
} > distribution.
} >
} > This doesn't quite work any more.
}
} Do you want to say that we should change the tests to also look for,
} say, $_compdir/Base/Core and if that exists, add `$_compdir/*/*(/)'?
Either that, or we should fix the docs. Having it work for the source
tree layout is helpful to developers, I think: No "make install" before
trying out some change, just set _compdir and let compinstall figure it
out. However, developers are also likely capable of setting the fpath
manually, so it's not that big a deal.
} > Also, I'm curious why this line in compaudit was commented out:
} >
} > ### [[ -d $_compdir/../Base ]] && _compdir=${_compdir:h}
}
} [...] since nowadays the comp* functions are in the top-level
} directory itself it didn't seem to make sense to look for certain
} sub-directories of the parent directory of $_compdir. Was I mistaken?
No, that's OK, I just was curious.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net
next prev parent reply other threads:[~2001-04-26 8:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-25 15:44 Bart Schaefer
2001-04-26 7:11 ` Sven Wischnowsky
2001-04-26 8:10 ` Bart Schaefer [this message]
2001-04-26 13:01 ` Sven Wischnowsky
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=1010426081035.ZM12445@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=zsh-workers@sunsite.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).