pasting text into vim doesn't work as expected #225

New Issue

granquet · 2023-06-01T16:19:53+03:00

granquet commented

2023-06-01 16:19:53 +03:00

The input gets mangled when pasting into vim while in insert mode (from a tmux buffer or 'shift-insert' for the X buffer).

The issue is reproduced when running meli in tmux (console without X/Wayland)
The issue is reproduced when running meli in kitty (running Wayland)
The issue isn't reproduced with vim standalone.
The issue isn't reproduced with nano as EDITOR.

steps to reproduce:

have vim as your EDITOR
enter insert mode
paste into the console with eitheir tmux or wayland shortcuts
pasted result is missing the first few characters, sometimes with side effects in vim itself (out of insertion mode, commands got entered...)

The input gets mangled when pasting into vim while in insert mode (from a tmux buffer or 'shift-insert' for the X buffer). The issue is reproduced when running meli in tmux (console without X/Wayland) The issue is reproduced when running meli in kitty (running Wayland) The issue isn't reproduced with vim standalone. The issue isn't reproduced with nano as EDITOR. steps to reproduce: - have vim as your EDITOR - enter insert mode - paste into the console with eitheir tmux or wayland shortcuts - pasted result is missing the first few characters, sometimes with side effects in vim itself (out of insertion mode, commands got entered...)

Manos Pitsidianakis commented

2023-06-04 22:29:22 +03:00

@granquet So I could not reproduce this with

kitty 0.26.5
VIM - Vi IMproved 9.0 (2022 Jun 28, compiled May 04 2023 10:24:44)
NVIM v0.7.2
tmux 3.3a

With TERM values xterm-kitty and xterm. Are your own versions different than these?

@granquet So I could not reproduce this with ```text kitty 0.26.5 VIM - Vi IMproved 9.0 (2022 Jun 28, compiled May 04 2023 10:24:44) NVIM v0.7.2 tmux 3.3a ``` With `TERM` values `xterm-kitty` and `xterm`. Are your own versions different than these?

Manos Pitsidianakis added the

bug

question

labels 2023-06-04 22:29:32 +03:00

granquet commented

2023-06-22 11:57:08 +03:00

Poster

@granquet So I could not reproduce this with
kitty 0.26.5
VIM - Vi IMproved 9.0 (2022 Jun 28, compiled May 04 2023 10:24:44)
NVIM v0.7.2
tmux 3.3a
With TERM values xterm-kitty and xterm. Are your own versions different than these?

Sorry for the late answer.

It works when I force TERM=xterm, but doesn't when keeping the default TERM=tmux-256color set by tmux on startup.

> @granquet So I could not reproduce this with > > ```text > kitty 0.26.5 > VIM - Vi IMproved 9.0 (2022 Jun 28, compiled May 04 2023 10:24:44) > NVIM v0.7.2 > tmux 3.3a > ``` > > With `TERM` values `xterm-kitty` and `xterm`. Are your own versions different than these? Sorry for the late answer. It works when I force `TERM=xterm`, but doesn't when keeping the default `TERM=tmux-256color` set by tmux on startup.

Manos Pitsidianakis commented

2023-06-22 16:35:45 +03:00

@granquet I remember when I had problems with tmux-256color I had them fixed with xterm-256color. Can you try that? Maybe kitty doesn't like that value.

@granquet I remember when I had problems with `tmux-256color` I had them fixed with `xterm-256color`. Can you try that? Maybe kitty doesn't like that value.

granquet commented

2023-09-05 11:26:05 +03:00

Poster

things works fine now that I've switched to xterm-256color.

things works fine now that I've switched to `xterm-256color`.

granquet closed this issue

2023-09-05 11:26:05 +03:00

Manos Pitsidianakis commented

2023-09-05 11:35:13 +03:00

@granquet glad to hear it :)

Sign in to join this conversation.