zsh-workers
 help / color / mirror / code / Atom feed
From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re:  zsh-3.1.5-pws-5: mixing "old" and "new" completions?
Date: Mon, 25 Jan 1999 14:15:54 +0100 (MET)	[thread overview]
Message-ID: <199901251315.OAA16544@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: "Andrej Borsenkow"'s message of Mon, 25 Jan 1999 15:11:25 +0300


Andrej Borsenkow wrote:

> 
> I would like to start play with new completion stuff. But I do not want to
> completely lose all current compctl's I have. What I would really like, is
> something like
> 
>   if defined new style completion
>      do it
>   else
>      use compctl completion
> 
> Is it possible?

I knew someone would ask for this...

No, currently I'm not sure how to do this. Providing a builtin
(`compold' or whatever) to generate the completions from a compctl
shouldn't be too hard. But if you have a definition for default
completion  in the new style stuff you probably want to use compctl's
only if there is one for the command (not -T, -D, ...). On the other
hand some people may want them to be used, or only sometimes, or...

Maybe we should instead provide a function that automatically converts
compctls into definitions for the new completion stuff. Transforming
them by hand as I did at the weekend is very tedious anyway.
But then again, the things in `new-completion-examples' are only
examples. One advantage of the new style is that you can almost
completely define the way completion is done by implementing your own
functions. So we could only write a function to convert to the style
used currently in `new-completion-examples', there is no way to write
a generic function for this. Also, the example stuff still isn't
complete, for example I currently use function return values as a
replacement for `-t', but not all functions do this correctly or
handle those return values.

But for those who only want to play with it: you can probably bind the 
new completion to a different key, keeping TAB for the compctl-stuff,
by changing the bindkey-argument in `new-completion-examples'.

Bye
 Sven

P.S.: Sorry.

--
Sven Wischnowsky                         wischnow@informatik.hu-berlin.de


             reply	other threads:[~1999-01-25 13:15 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-01-25 13:15 Sven Wischnowsky [this message]
1999-01-25 13:27 ` Peter Stephenson
1999-01-26 11:52   ` Andrej Borsenkow
1999-01-28  7:06     ` Bart Schaefer
1999-01-28 11:28       ` Peter Stephenson
1999-01-28 16:31         ` Bart Schaefer
  -- strict thread matches above, loose matches on Subject: below --
1999-01-28 16:57 Sven Wischnowsky
1999-01-28 14:25 Sven Wischnowsky
1999-01-28 11:59 Sven Wischnowsky
1999-01-27 15:21 Sven Wischnowsky
1999-01-27 12:25 Sven Wischnowsky
1999-01-27 15:04 ` Andrej Borsenkow
1999-01-26 13:58 Sven Wischnowsky
1999-01-25 12:11 Andrej Borsenkow

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=199901251315.OAA16544@beta.informatik.hu-berlin.de \
    --to=wischnow@informatik.hu-berlin.de \
    --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).