From: Elliott Cable <me@ell.io>
To: zsh-users@zsh.org
Subject: edit-command-line, vim, and pasting
Date: Sun, 1 Nov 2015 10:37:45 -0600 [thread overview]
Message-ID: <CAPZ477Oz5BCB797hpE5SO+X9f_Sz8BXX49nUZ9jPERgVGcXHzw@mail.gmail.com> (raw)
I've just set up my Zsh to allow me to use the `edit-command-line` widget:
autoload -z edit-command-line && zle -N edit-command-line
bindkey -M vicmd v edit-command-line
For some reason I can't puzzle out, though, `vim` *when invoked via
`edit-command-line`* goes haywire when I try to *paste* something,
even with `:set paste` enabled.
When I attempt to paste even a single character, my terminal-bell
signals a few times, and then *part* of whatever I attempted to paste
(usually sans the first few characters, or in some other way messed
up) is actually inserted into the document.
I can't verify precisely what character-sequence vim is receiving, but
it's something mangled; there's clearly a couple BELs in there, and
some ESCs (because I'm already in insert mode when I ⌘V, and
normal-mode commands get run; sometimes the contents of a vim buffer
are inserted at the beginning of the *actual* paste, for instance.)
It's not anything in my Vim configuration, because it occurs in the
same way even if I set `VISUAL="vim -u ''"`, preventing Vim from
loading any configuration at all. Strangely enough, however, while it
does continue to occur if I invoke a new `zsh` without configuration
(`zsh -f`), it *does not* if I indirect that sub-invocation via env …
even when manually keeping all of the environment: `env -i "$(env)"
zsh -f (what the hell does that imply?)
This doesn't occur, ever, outside Zsh; or, specifically, outside of
the `edit-command-line` mode. Does anybody have any ideas what could
be causing this?
⁓ ELLIOTTCABLE — fly safe.
http://ell.io/tt
next reply other threads:[~2015-11-01 16:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-01 16:37 Elliott Cable [this message]
2015-11-01 18:39 ` Bart Schaefer
2015-11-02 11:16 ` Oliver Kiddle
2015-12-07 3:01 ` Elliott Cable
2015-12-07 6:38 ` Bart Schaefer
2015-12-11 5:33 ` Oliver Kiddle
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=CAPZ477Oz5BCB797hpE5SO+X9f_Sz8BXX49nUZ9jPERgVGcXHzw@mail.gmail.com \
--to=me@ell.io \
--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).