Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Odd autoremoveslash behaviour
- X-seq: zsh-workers 11401
- From: Sven Wischnowsky <wischnow@xxxxxxxxxxxxxxxxxxxxxxx>
- To: zsh-workers@xxxxxxxxxxxxxx
- Subject: Re: Odd autoremoveslash behaviour
- Date: Tue, 16 May 2000 10:03:06 +0200 (MET DST)
- In-reply-to: Peter Stephenson's message of Mon, 15 May 2000 16:06:04 +0100
- Mailing-list: contact zsh-workers-help@xxxxxxxxxxxxxx; run by ezmlm
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@xxxxxxxxxxxxxxxxxxxxxxx
Messages sorted by:
Reverse Date,
Date,
Thread,
Author