From: Tanaka Akira <akr@jaist.ac.jp>
To: zsh-workers@sunsite.auc.dk
Subject: Re: PATCH: Completion/User/_cvs again.
Date: 08 Sep 1999 08:22:32 +0900 [thread overview]
Message-ID: <rsq1zca2ton.fsf@crane.jaist.ac.jp> (raw)
In-Reply-To: "Bart Schaefer"'s message of "Tue, 7 Sep 1999 21:06:27 +0000"
In article <990907210627.ZM8775@candle.brasslantern.com>,
"Bart Schaefer" <schaefer@candle.brasslantern.com> writes:
> Aren't we already requiring the parameters modlue for some of the other
> completion stuff? Would this be faster/cleaner/clearer as
>
> if ! (( $+functions[_cvs_command] )); then
I didn't know parameter module. Hm, it's good. But, I think the
module is not loaded by the completion stuff.
Z(2):akr@is27e1u11% grep zmodload Completion/**/*(.)
Completion/Builtins/CVS/Entries:/_zmodload/1.1.1.7/Thu Aug 19 15:41:03 1999//
Completion/Builtins/_zmodload:#compdef zmodload
Completion/Builtins/_zmodload: compadd "$expl[@]" - $(zmodload)
Completion/Core/_main_complete:# if zmodload -e parameter; then
Completion/Core/_normal: if zmodload -e parameter; then
Completion/Core/_parameters: if zmodload -e parameter; then
Completion/Core/_parameters: if zmodload -e parameter; then
Completion/User/_cvs: ! { zmodload -e stat || zmodload stat }; then
Z(2):akr@is27e1u11%
Although some functions examine whether parameter module is exist,
they doesn't try to load the module.
--
Tanaka Akira
next prev parent reply other threads:[~1999-09-07 23:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-06 18:10 Tanaka Akira
1999-09-07 21:06 ` Bart Schaefer
1999-09-07 23:22 ` Tanaka Akira [this message]
1999-09-07 7:17 Sven Wischnowsky
1999-09-07 10:47 ` Tanaka Akira
1999-09-07 22:26 ` Bart Schaefer
1999-09-07 22:58 ` Tanaka Akira
1999-09-08 0:46 ` Bart Schaefer
1999-09-07 11:22 Sven Wischnowsky
1999-09-07 11:51 Sven Wischnowsky
1999-09-08 7:08 Sven Wischnowsky
1999-09-08 8:27 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=rsq1zca2ton.fsf@crane.jaist.ac.jp \
--to=akr@jaist.ac.jp \
--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).