From: "Andrej Borsenkow" <borsenkow.msk@sni.de>
To: "Sven Wischnowsky" <wischnow@informatik.hu-berlin.de>,
<zsh-workers@sunsite.auc.dk>
Subject: RE: PATCH: old lists compstate
Date: Mon, 29 Mar 1999 21:19:13 +0400 [thread overview]
Message-ID: <002e01be7a08$443cb9b0$21c9ca95@mowp.siemens.ru> (raw)
In-Reply-To: <199903290948.LAA01291@beta.informatik.hu-berlin.de>
>
> I've added a small example completer function `_menu' that may be put
> before the normal `_complete' completer and that gives menucompletion
> implemented fully in shell code (note that this does not work together
> with normal menucompletion).
>
bor@itsrm2:~%> compconf
correct_accept 2n
match_original yes
completer _complete:_match
dumpfile /home/bor/.zsh.d/Completion/Core/compinit.dump
correct_prompt correct to:
bor@itsrm2:~%> l /t/s/gl/co<TAB>
bor@itsrm2:~%> l /tools/src/glib-1.<TAB>/config
bor@itsrm2:~%> l /tools/src/glib-1.<TAB>/config
glib-1.1.15/ glib-1.2.0/
bor@itsrm2:~%> l /tools/src/glib-1.1.15<CURSOR>/config
glib-1.1.15/ glib-1.2.0/
that is O.K., but
bor@itsrm2:~%> compconf completer=_menu:_complete:_match
bor@itsrm2:~%> l /t/s/gl/co<TAB>
bor@itsrm2:~%> l /tools/src/glib-1.1.15/config.cache <CURSOR>
glib-1.1.15/ glib-1.2.0/
BTW to the first example. I have these options:
noautolist off
bashautolist off
nolistambiguous off
but list is shown only after the second TAB (as if bashautolist was set).
I'd expect, that with autolist+listambiguous list were shown after the first
TAB already. Actually, I think, it started with bashautolist option ... but
as I used menu completion before ... :-)
And about compconf ... exaclty in the case above I missed something like
compconf -i _list completer (meaning insert _list to the element completer)
or, at least,
compconf completer=_list:$(compconf -l completer)
or like. I mean, user probably should not see this array at all ...
cheers
/andrej
P.S. The same with zsh -f; fpath=(....); source ...; compconf
completer=_menu:_complete:_match But I get additional beep (I set nobeep
normally). And here list is shown immediately with the same options as
above. wonders ...
prev parent reply other threads:[~1999-03-29 17:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-29 9:48 Sven Wischnowsky
1999-03-29 17:19 ` Andrej Borsenkow [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='002e01be7a08$443cb9b0$21c9ca95@mowp.siemens.ru' \
--to=borsenkow.msk@sni.de \
--cc=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).