zsh-workers
 help / color / mirror / code / Atom feed
From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: BUG: listmatches called with bogus list
Date: Thu, 6 Jan 2000 10:27:00 +0100 (MET)	[thread overview]
Message-ID: <200001060927.KAA17174@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: Tanaka Akira's message of 06 Jan 2000 16:56:01 +0900


Tanaka Akira wrote:

> `echo =zsh<TAB>-<M-x>expand-word<CR>' shows `BUG: listmatches called
> with bogus list'.

Time for a bit of defensive programming, I think.

Avoiding the error message was simple but finding out how to avoid the 
display bug that showed up after that...

Bye
 Sven

diff -ru ../z.old/Src/Zle/compresult.c Src/Zle/compresult.c
--- ../z.old/Src/Zle/compresult.c	Wed Jan  5 16:41:42 2000
+++ Src/Zle/compresult.c	Thu Jan  6 10:24:36 2000
@@ -1827,9 +1827,9 @@
 mod_export int
 invalidate_list(void)
 {
-    if (showinglist == -2)
-	listmatches();
     if (validlist) {
+	if (showinglist == -2)
+	    zrefresh();
 	freematches(lastmatches);
 	lastmatches = NULL;
 	hasoldlist = 0;
diff -ru ../z.old/Src/Zle/zle_misc.c Src/Zle/zle_misc.c
--- ../z.old/Src/Zle/zle_misc.c	Wed Jan  5 16:41:43 2000
+++ Src/Zle/zle_misc.c	Thu Jan  6 09:51:28 2000
@@ -640,7 +640,8 @@
 executenamedcommand(char *prmt)
 {
     Thingy cmd;
-    int len, l = strlen(prmt), ols = listshown, feep = 0, listed = 0, curlist = 0;
+    int len, l = strlen(prmt), feep = 0, listed = 0, curlist = 0;
+    int ols = (listshown && validlist);
     char *ptr;
     char *okeymap = curkeymapname;
 

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


             reply	other threads:[~2000-01-06  9:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-01-06  9:27 Sven Wischnowsky [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-01-06  7:56 Tanaka Akira
1995-09-05 16:22 Zoltan Hidvegi
1995-09-05 17:40 ` Zoltan Hidvegi
1995-09-07 10:42   ` Zefram

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=200001060927.KAA17174@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).