From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18343 invoked from network); 3 Nov 1999 08:11:25 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 3 Nov 1999 08:11:25 -0000 Received: (qmail 5556 invoked by alias); 3 Nov 1999 08:11:21 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 8506 Received: (qmail 5549 invoked from network); 3 Nov 1999 08:11:20 -0000 Date: Wed, 3 Nov 1999 09:11:17 +0100 (MET) Message-Id: <199911030811.JAA29634@beta.informatik.hu-berlin.de> From: Sven Wischnowsky To: zsh-workers@sunsite.auc.dk In-reply-to: "Bart Schaefer"'s message of Tue, 2 Nov 1999 19:05:19 +0000 Subject: Re: PATCH: predict-on: suppress long listings Bart Schaefer wrote: > On Oct 28, 10:03am, Sven Wischnowsky wrote: > } Subject: Re: PATCH: predict-on: suppress long listings > } > } > } Bart Schaefer wrote: > } > } > Ah, yes. It also does odd things with certain characters, like if you > } > type $! you end up with $\! with the cursor on the backslash. Probably > } > it should search rightwards until it finds the character you typed and > } > stay there, going back again if it doesn't find that character. > } > } That's what `compconf predict_cursor=key' tries to achieve. > > Yeah, but it searches rightwards from the end rather than leftwards from > the current cursor position. Most of the time that's OK, I guess. I hope it is actually better... I first did it from the left and then tried something like `zl/zle_tr..' (I had a `zle_tricky.c.orig' at that time). When searching from the left this put the cursor after the `.' before the `c', not on the one the dot typed really corresponded to. Bye Sven -- Sven Wischnowsky wischnow@informatik.hu-berlin.de