zsh-users
 help / color / mirror / code / Atom feed
From: Oliver Kiddle <okiddle@yahoo.co.uk>
To: Christian Brabandt <cb@256bit.org>
Cc: zsh-users@zsh.org
Subject: Re: vi mode reset
Date: Fri, 09 Dec 2016 17:46:33 +0100	[thread overview]
Message-ID: <62644.1481301993@hydra.kiddle.eu> (raw)
In-Reply-To: <20161209154813.GG19559@256bit.org>

Christian Brabandt wrote:
> It is reset to emacs mode I believe. I have to hit set -o vi again.

> > disable that with: unset zle_bracketed_paste
> I'll try that, thanks. However I always thought, bracket paste mode is 
> useful...

It is useful.

> I don't use any distribution.
>
> Here is an example:
> 0 59928 chrisbra@debian ~ % bindkey -L |grep 200
> bindkey "^X^[[200~" _start_quoted_paste
> bindkey "^[[200~" _start_paste

Maybe not from a distribution but those are custom functions, however.
Somewhere or other, you've got some configuration that is defining
those functions and binding the keys. Given that you started having
problems when upgrading zsh, you probably didn't have the necessary
configuration to turn your terminal's bracketed paste mode on and off.
The newer zsh is turning it on for you because it has an internal widget
for bracketed paste.

I would guess that _start_paste switches you to a custom keymap where
the end of bracketed paste is setup to switch you "back" to the emacs
keymap.

You want to get rid of all that: the _start_quoted_paste and
_start_paste functions and any additional keymap.
Then you should see:
  % bindkey -L |grep 200
  bindkey "^[[200~" bracketed-paste
To check for odd keymaps, run bindkey -l

Oliver


  reply	other threads:[~2016-12-09 16:54 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20161209130109epcas2p1fd786d46827852a8cf1badcb5d003ec9@epcas2p1.samsung.com>
2016-12-09 12:29 ` Christian Brabandt
2016-12-09 14:33   ` Ray Andrews
2016-12-09 14:41   ` Peter Stephenson
2016-12-09 14:44   ` Oliver Kiddle
2016-12-09 15:07     ` off topic Ray Andrews
2016-12-09 16:28       ` Oliver Kiddle
2016-12-09 17:45         ` Ray Andrews
2016-12-10  0:54           ` Bart Schaefer
2016-12-10  2:50             ` Oliver Kiddle
2016-12-10  3:13               ` Bart Schaefer
2016-12-10  3:31               ` Ray Andrews
     [not found]             ` <95362.1481338226__15466.9970310808$1481338718$gmane$org@hydra.kiddle.eu>
2016-12-11  4:32               ` Daniel Shahaf
2016-12-11 17:07                 ` Ray Andrews
2016-12-11 17:19                   ` Bart Schaefer
2016-12-11 18:02                     ` Ray Andrews
2016-12-11 19:20                       ` Bart Schaefer
2016-12-11 20:23                         ` Ray Andrews
     [not found]         ` <584AEDBF.2050402__19991.0537027337$1481307418$gmane$org@eastlink.ca>
2016-12-09 19:24           ` Daniel Shahaf
2016-12-09 20:25             ` Ray Andrews
     [not found]             ` <584B1325.1010907__10266.7204490446$1481316980$gmane$org@eastlink.ca>
2016-12-10  0:14               ` Daniel Shahaf
2016-12-10  0:21                 ` Ray Andrews
2016-12-12 13:11         ` Vincent Lefevre
2016-12-09 15:48     ` vi mode reset Christian Brabandt
2016-12-09 16:46       ` Oliver Kiddle [this message]
2016-12-09 20:24         ` Christian Brabandt

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=62644.1481301993@hydra.kiddle.eu \
    --to=okiddle@yahoo.co.uk \
    --cc=cb@256bit.org \
    --cc=zsh-users@zsh.org \
    /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).