zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: DervishD <raul@pleyades.net>
Cc: Zsh <zsh-workers@sunsite.dk>
Subject: Re: Using the new completion system 'naked'
Date: Fri, 17 May 2002 11:36:25 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.44.0205171123260.28884-100000@ns1.sodaware.com> (raw)
In-Reply-To: <3CE54512.mail1J611TGTR@viadomus.com>

On Fri, 17 May 2002, DervishD wrote:

>     - Will the old 'compctl' completion system disabled in the
> future? And if the answer is 'yes', when?

The answers are "maybe, but probably not" and "nobody knows."

>     - Can I use the new completion system without compinstall'ing it
> and without compinit'ing it, just by suitably calling compadd,
> compset and compcall (no compdef...)?

Yes, of course you can.  The `compinit' system is only one of many that
could be built on top of the compadd etc. builtins.  It just happens to
be the best one we've come up with so far.

>     Moreover, if the answer is not very large: what advantages gives
> the new completion mechanism over the old one?

Depends on what you mean by "the new completion mechanism."

If you mean "the `compinit' system" then the answer is very large but
mostly boils down to having more completions available out of the box,
with a way to customize them without rewriting them (zstyles), plus a
better-organized system for adding others as we go along.

If you mean the compadd/compset/etc. builtins only, plus `zle -C', then
the advantage is meant to be that the syntax is less baroque than that
of `compctl -x', and correspondingly that more of the processing can be
described by shell functions which are presumably more readable and more
easily debugged than are the cryptic strings used by `compctl'.

One might observe that `_arguments' has become nearly as cryptic as
`compctl', but on the other hand it's also doing a lot more work.


  reply	other threads:[~2002-05-17 18:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-17 17:59 DervishD
2002-05-17 18:36 ` Bart Schaefer [this message]
2002-05-17 19:41   ` DervishD

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.44.0205171123260.28884-100000@ns1.sodaware.com \
    --to=schaefer@brasslantern.com \
    --cc=raul@pleyades.net \
    --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).