From: "Oliver Kiddle" <okiddle@yahoo.co.uk>
To: zsh-workers@sunsite.dk
Subject: Re: Two missing completion functions that bug me
Date: Thu, 29 Mar 2001 11:09:02 +0100 (BST) [thread overview]
Message-ID: <20010329100902.61890.qmail@web9305.mail.yahoo.com> (raw)
In-Reply-To: <1010329075937.ZM17818@candle.brasslantern.com>
--- Bart Schaefer <schaefer@candle.brasslantern.com> wrote:
> ---- 8< ---- _vared ---- 8< ---
Damn, I was holding exactly that for afer Sven's big move and rename.
> '-c+[create parameter or change type]' \
I'm not sure you need the + after -c, or at least that is the only
difference to my function (other than wording for the help info).
Would it be worth it to try to have completions for all builtins ready
for 4.0? I've put a (quickly generated so not ideal) list of all those
which don't have a completion below so feel free to mention requests or
views. Any ideas what should be done for commands with just one option
(like suspend) - completing -f might not be what people expect.
Oliver
ulimit
[
compfiles
pushln
exit
getln
pwd
zparseopts
logout
comptags
compdescribe
r
zregexparse
return
compadd
ttyctl
test
comparguments
comptry
zprof
compset
compvalues
compgroups
echo
dirs
:
bye
compquote
zformat
suspend
break
continue
umask
____________________________________________________________
Do You Yahoo!?
Get your free @yahoo.co.uk address at http://mail.yahoo.co.uk
or your free @yahoo.ie address at http://mail.yahoo.ie
next prev parent reply other threads:[~2001-03-29 10:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-29 7:59 Bart Schaefer
2001-03-29 10:09 ` Oliver Kiddle [this message]
2001-03-29 16:24 ` Bart Schaefer
2001-03-30 9:16 ` Oliver Kiddle
2001-03-30 15:38 ` Bart Schaefer
2001-03-30 15:59 ` Bart Schaefer
2001-03-30 16:35 ` Oliver Kiddle
2001-03-30 16:53 ` Bart Schaefer
2001-03-30 8:21 Sven Wischnowsky
2001-03-30 16:11 ` Bart Schaefer
2001-03-30 8:23 Sven Wischnowsky
2001-04-02 9:15 Sven Wischnowsky
2001-04-02 12:04 ` Oliver Kiddle
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=20010329100902.61890.qmail@web9305.mail.yahoo.com \
--to=okiddle@yahoo.co.uk \
--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).