zsh-workers
 help / color / mirror / code / Atom feed
From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: PATCH: predict-on: suppress long listings
Date: Wed, 3 Nov 1999 09:11:17 +0100 (MET)	[thread overview]
Message-ID: <199911030811.JAA29634@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: "Bart Schaefer"'s message of Tue, 2 Nov 1999 19:05:19 +0000


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


             reply	other threads:[~1999-11-03  8:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-11-03  8:11 Sven Wischnowsky [this message]
  -- strict thread matches above, loose matches on Subject: below --
1999-10-28  8:03 Sven Wischnowsky
1999-11-02 19:05 ` Bart Schaefer
1999-10-27 14:03 Sven Wischnowsky
1999-10-27 15:51 ` Bart Schaefer
1999-10-27 16:10 ` Bart Schaefer
1999-10-27 16:15 ` Bart Schaefer
1999-10-26 16:08 Bart Schaefer

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=199911030811.JAA29634@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).