zsh-workers
 help / color / mirror / code / Atom feed
From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: Odd autoremoveslash behaviour
Date: Tue, 16 May 2000 10:03:06 +0200 (MET DST)	[thread overview]
Message-ID: <200005160803.KAA23295@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: Peter Stephenson's message of Mon, 15 May 2000 16:06:04 +0100


Peter Stephenson wrote:

> I don't think this is anything I've done...  it may be only with menu
> completion:
> 
> % echo <TAB>
> % echo dir1/
> dir1/ dir2/
> 
> type `/':
> 
> % echo /
>       ^gorn.

(Hey, super woody word...)


Oops. That was a more general problem, caused by the ^G-change, it
didn't accept the currently inserted match when a normal character was 
pressed (and the undid it).

One question is if typing a character should make it be inserted
directly after the match (as in menucompletion) or if it should first
really accept the match as in a completion with only one match. After
very little testing I decided to make it be really accepted, but that
can be changed if our menu-completion experts say that we should...

Bye
 Sven

Index: Src/Zle/complist.c
===================================================================
RCS file: /cvsroot/zsh/zsh/Src/Zle/complist.c,v
retrieving revision 1.15
diff -u -r1.15 complist.c
--- Src/Zle/complist.c	2000/05/11 08:40:11	1.15
+++ Src/Zle/complist.c	2000/05/16 08:02:46
@@ -2112,6 +2112,7 @@
 	    continue;
 	} else {
 	    ungetkeycmd();
+	    acc = 1;
 	    break;
 	}
 	do_single(**p);

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


             reply	other threads:[~2000-05-16  8:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-05-16  8:03 Sven Wischnowsky [this message]
2000-05-16 10:59 ` Peter Stephenson
  -- strict thread matches above, loose matches on Subject: below --
2000-05-15 15:06 Peter Stephenson
2000-05-15 15:11 ` 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=200005160803.KAA23295@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).