zsh-users
 help / color / mirror / code / Atom feed
From: Thorsten Kampe <thorsten@thorstenkampe.de>
To: zsh-users@sunsite.dk
Subject: Problem with 'predict-on'
Date: Wed, 24 Mar 2004 05:18:57 +0100	[thread overview]
Message-ID: <hg5h9729cfc5$.dlg@thorstenkampe.de> (raw)

Hi zsh-users,

I'm testing the ZLE widget "predict-on" with...

autoload -U predict-on; predict-on
zle -N predict-on
zle -N predict-off
bindkey '^X^Z' predict-on
bindkey '^Z'   predict-off
zstyle ':predict' verbose 1

This means that predict-on is active by default. But there are some
flaws with predict-on: first of all I can not backspace the first
character I typed in the command line. Then pasting text via
[Shift]-[Ins] doesn't turn off prediction (like it should[1]).

So I RTFMed and chose "toggle"[2]: "zstyle ':predict' toggle 1".
But when I write this in my .zshrc, predict-on is automatically "off"
(although "toggle"'s conditions for "toggling" aren't met: "when
editing a multi-line buffer or after moving into the middle of a line
and then deleting a character").

So my question is: how can I turn on "predict-on" by default and
circumvent its negative circumstances when pasting text (and maybe
others I haven't discovered yet)?


Thorsten

[1] "Editing a multiline buffer or pasting in a chunk of text; it's
unlikely prediction is wanted"  --  functions/predict-on

[2] used by predict-on [...] in the context ':predict'. If set to
[...] 'true', predictive typing is automatically toggled off in
situations where it is unlikely to be useful, such as when editing a
multi-line buffer or after moving into the middle of a line and then
deleting a character.


             reply	other threads:[~2004-03-24  4:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-24  4:18 Thorsten Kampe [this message]
2004-03-24 16:45 ` Bart Schaefer
2004-03-24 20:25   ` Thorsten Kampe
2004-03-25  3:17     ` 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='hg5h9729cfc5$.dlg@thorstenkampe.de' \
    --to=thorsten@thorstenkampe.de \
    --cc=zsh-users@sunsite.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).