From: Christian Brabandt <cb@256bit.org>
To: Oliver Kiddle <okiddle@yahoo.co.uk>
Cc: zsh-users@zsh.org
Subject: Re: vi mode reset
Date: Fri, 9 Dec 2016 16:48:13 +0100 [thread overview]
Message-ID: <20161209154813.GG19559@256bit.org> (raw)
In-Reply-To: <57127.1481294647@hydra.kiddle.eu>
Hi Oliver!
On Fr, 09 Dez 2016, Oliver Kiddle wrote:
> Christian Brabandt wrote:
> > However, since the upgrade I noticed that my zsh resets vi mode, on
> > various occasions, but I cannot reproduce exactly when exactly this
>
> What exactly do you mean by "resets vi mode". Switches to command/normal
> mode without your having pressed escape, perhaps? Many key combinations
> send a sequence of characters starting with an escape so zsh may be
> mis-interpreting that.
It is reset to emacs mode I believe. I have to hit set -o vi again.
> > happens. I think this usually happens either if I am pasting something
> > into the terminal (using putty from Windows and pasting using
> > <shift><insert> keys) or running Vim.
>
> Sounds like possibly an effect of the bracketed paste feature. You can
> disable that with: unset zle_bracketed_paste
I'll try that, thanks. However I always thought, bracket paste mode is
useful...
> It'd be better to understand how it is coming to fail for you. Perhaps
> your terminal has a different bracketed paste mode. Or perhaps you've
> removed the key binding for it. Do you perhaps clear a range of key
> bindings in your .zshrc? What does this show?:
> bindkey -L |grep 200
>
> What do you see if you press Ctrl-V before pasting text?
>
> Do you perhaps have some other safe-paste or bracketed-paste plugin from
> elsewhere. Are you using something like oh-my-zsh or prezto?
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
# Here I pasted the string zsh using Ctrl-V:
0 59929 chrisbra@debian ~ % ^[[200~zshG
# Here I pasted the usual way hitting <shift><insert>, then pressing
# <esc> stops working:
1 59929 chrisbra@debian ~ % wget -c 'https://github.com/vim/vim/issues/1204'
--2016-12-09 14:14:10-- https://github.com/vim/vim/issues/1204
Resolving github.com (github.com)... 192.30.253.113, 192.30.253.112
[...]
2016-12-09 14:14:12 (284 KB/s) - ‘1204’ saved [76470]
# Now hitting esc won't go back into command mode.
2 59933 chrisbra@debian ~ % set -o |grep "^vi"
vi on
# Looks like it is still on. Hm, that is strange. However when I press
# <esc> it won't go back into normal mode but keeps entering keys.
# Entering set -o vi fixes that.
Best,
Christian
--
Linux wird nie das meistinstallierte Betriebssystem sein.
Bedenken Sie nur, wie oft man Windows neu installieren muß.
next prev parent reply other threads:[~2016-12-09 15:48 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 ` Christian Brabandt [this message]
2016-12-09 16:46 ` vi mode reset Oliver Kiddle
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=20161209154813.GG19559@256bit.org \
--to=cb@256bit.org \
--cc=okiddle@yahoo.co.uk \
--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).