From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: zsh-workers@sunsite.auc.dk
Subject: Re: PATCH: Re: cvs <TAB> dumps core.
Date: Sun, 21 Nov 1999 05:12:58 +0000 [thread overview]
Message-ID: <991121051258.ZM16504@candle.brasslantern.com> (raw)
In-Reply-To: <rsqln7sa3mw.fsf@crane.jaist.ac.jp>
On Nov 21, 1:07pm, Tanaka Akira wrote:
} Subject: Re: PATCH: Re: cvs <TAB> dumps core.
}
} Z:akr@is27e1u11% Src/zsh -f
} is27e1u11% bindkey -e; fpath=($PWD/Completion/*(/)); autoload -U compinit; compinit -D; compdef _tst tst
} is27e1u11% cvs <TAB>
} CVS/ Src/ commit init rtag
} Completion/ StartupFiles/ diff log status
} Config/ Util/ edit login tag
} Doc/ add editors logout unedit
} Etc/ admin export rdiff update
} Functions/ annotate history release watch
} Misc/ checkout import remove watchers
}
} Wow. filenames shouldn't listed.
It's only directory names, and it's related to:
} is27e1u11% cvs --allow-root=CVS/
}
} Of cause, the option `--allow-root' shouldn't completed.
If you do
compstyle '*:descriptions' format '%d'
before trying "cvs <TAB>", you'll see that it says
cvs command
rootdir
So it's listing directories to be the argument of --allow-root=. This
in turn is because _arguments at line 299 is calling
compadd -M -D equal - --allow_root
and then setting IPREFIX to --allow-root= at line 304, etc. However,
it's beyond my understanding of the interaction between _arguments and
comparguments to tell how it got into that state in the first place.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
prev parent reply other threads:[~1999-11-21 5:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-19 16:34 Tanaka Akira
1999-11-20 19:38 ` PATCH: " Bart Schaefer
1999-11-21 4:07 ` Tanaka Akira
1999-11-21 5:12 ` Bart Schaefer [this message]
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=991121051258.ZM16504@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--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).