From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: compstate[old_list]
Date: Mon, 19 Apr 1999 12:00:37 +0200 (MET DST) [thread overview]
Message-ID: <199904191000.MAA19181@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: Peter Stephenson's message of Mon, 19 Apr 1999 11:18:51 +0200
Peter Stephenson wrote:
> I tried to add these lines to the top of _main_complete so that listing
> widgets could be made to use an existing list of completions.
>
> if [[ $WIDGET = *list* && -n $compconfig[old_list] &&
> -n $compstate[old_list] &&
> ( $compconfig[old_list] = always || $compstate[old_list] != shown ) ]]; then
> compstate[old_list]=keep
> return
> fi
>
> But when I start a non-contextual completion, and the list is displayed by
> autolist, and I then type ^D, this doesn't work --- it seems
> $compstate[old_list] is not set. Is this just me?
This was caused in zle_main.c, which I obviously forgot to change.
Bye
Sven
diff -u os/Zle/zle_main.c Src/Zle/zle_main.c
--- os/Zle/zle_main.c Tue Apr 13 09:41:27 1999
+++ Src/Zle/zle_main.c Mon Apr 19 11:59:59 1999
@@ -579,12 +579,7 @@
if(!(wflags & ZLE_KEEPSUFFIX))
removesuffix();
- if(!(wflags & ZLE_MENUCMP) ||
- ((wflags & WIDGET_NCOMP) && compwidget != w)) {
- /* If we are doing a special completion, and the widget
- * is not the one currently in use for special completion,
- * we are starting a new completion.
- */
+ if(!(wflags & ZLE_MENUCMP)) {
fixsuffix();
invalidatelist();
}
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next reply other threads:[~1999-04-19 10:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-19 10:00 Sven Wischnowsky [this message]
1999-04-20 12:36 ` compstate[old_list] Peter Stephenson
-- strict thread matches above, loose matches on Subject: below --
1999-04-21 6:50 compstate[old_list] Sven Wischnowsky
1999-04-20 14:17 compstate[old_list] Sven Wischnowsky
1999-04-20 15:34 ` compstate[old_list] Peter Stephenson
1999-04-19 9:18 compstate[old_list] Peter Stephenson
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=199904191000.MAA19181@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).