From: Bart Schaefer <schaefer@brasslantern.com>
To: Zsh Users <zsh-users@sunsite.dk>
Subject: Re: Yes, another completion question
Date: Wed, 27 Oct 2004 10:27:31 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.61.0410271016420.1295@toltec.zanshin.com> (raw)
In-Reply-To: <20041027170851.GB10509@DervishD>
On Wed, 27 Oct 2004, DervishD wrote:
> The new completion system is more configurable, more powerful,
> etc. but I don't think I need all that configuration and power. In
> fact I prefer the old way, with a dozen compctl commands to make my
> life easier... Am I plainly wrong?
No, not plainly. :-)
"New completion" started out with the noble goal of replacing the rather
arcane "compctl -x" syntax with the only somewhat less arcane but at least
more familiar syntax of the shell language.
However, once given a system that could do more powerful things, people
wanted to take full advantage of it. ("Gosh, if completion can do that,
couldn't it also do this little bit of extra work too?" Repeat until the
"little bit" of extra work done exceeds the original effort.) The result
is the current compsys collection of functions.
If you're not one of the people who wants or needs all of those extra
little bits, there's no reason to use it. Hence "compcall" and other
hooks for dropping from one system into the other. Also hence the use of
autoloading for all the compsys functions, so that even if you enable the
whole thing you only load the bits you actually call upon.
> Is compctl going to dissappear soon and I should not put a minute of
> work in writing my compctl recipes?
I don't think there's any reason that compctl will disappear -- but it's
unlikely to get any bugfixes or further improvements, either.
next prev parent reply other threads:[~2004-10-27 17:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-27 17:08 DervishD
2004-10-27 17:27 ` Bart Schaefer [this message]
2004-10-27 17:49 ` DervishD
2004-10-27 18:49 ` DervishD
2004-10-29 15:17 ` Yet " William Scott
2004-11-01 12:42 ` DervishD
2004-11-01 13:13 ` William Scott
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=Pine.LNX.4.61.0410271016420.1295@toltec.zanshin.com \
--to=schaefer@brasslantern.com \
--cc=zsh-users@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).