zsh-workers
 help / color / mirror / code / Atom feed
From: Zefram <A.Main@dcs.warwick.ac.uk>
To: hzoli@cs.elte.hu (Zoltan Hidvegi)
Cc: zsh-workers@math.gatech.edu (Z Shell workers mailing list)
Subject: Re: A completion bug
Date: Wed, 12 Jul 1995 15:18:08 +0100 (BST)	[thread overview]
Message-ID: <27330.199507121418@stone.dcs.warwick.ac.uk> (raw)
In-Reply-To: <9507121355.AA04044@turan.elte.hu> from "Zoltan Hidvegi" at Jul 12, 95 03:55:55 pm

-----BEGIN PGP SIGNED MESSAGE-----

The patch below fixes a bug in the new completion list logic, pointed
out to me by Zoltan.  The symptom is that if LIST_AMBIGUOUS is unset,
and an unambiguous partial completion is performed, ZLE still thinks
the list is valid, which causes it to insert the unambiguous portion a
second time if completion is continued.

 -zefram

      *** Src/zle_tricky.c.old	Wed Jul 12 15:08:36 1995
      --- Src/zle_tricky.c	Wed Jul 12 15:09:25 1995
      ***************
      *** 3225,3233 ****
        		inststrlen(firstm, 1, ab);
        	    if (ae && !atend)
        		inststrlen(firstm + strlen(firstm) - ae, 0, ae);
        	    if (isset(LISTAMBIGUOUS) && (ab || (ae && !atend))) {
        		lastambig = 0;
      - 		invalidatelist();
        		return;
        	    }
        	}
      --- 3225,3234 ----
        		inststrlen(firstm, 1, ab);
        	    if (ae && !atend)
        		inststrlen(firstm + strlen(firstm) - ae, 0, ae);
      + 	    if(ab || (ae && !atend))
      + 		invalidatelist();
        	    if (isset(LISTAMBIGUOUS) && (ab || (ae && !atend))) {
        		lastambig = 0;
        		return;
        	    }
        	}

-----BEGIN PGP SIGNATURE-----
Version: 2.6.i

iQBVAgUBMAPZiGWJ8JfKi+e9AQF+SwH/X+QczHJD8FT4PWRUMWvZu23ZYdM6wAYJ
r+LcJUElDlrHLoPBMk+EVQai1gbUbLYwzdAkn2Ua6MvgCKVj6AhevQ==
=p+VS
-----END PGP SIGNATURE-----


           reply	other threads:[~1995-07-12 14:27 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <9507121355.AA04044@turan.elte.hu>]

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=27330.199507121418@stone.dcs.warwick.ac.uk \
    --to=a.main@dcs.warwick.ac.uk \
    --cc=hzoli@cs.elte.hu \
    --cc=zsh-workers@math.gatech.edu \
    /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).