[vim/vim] Slow vim paste (showing character 'P' temporarily) (Issue #13003)
Daniel Torres
Steps to reproduce
- Open a file with at least one word inside.
- Put cursor under the first letter in the word
- Now, do this sequence quickly - Change word (cw) , exit insert mode (ESC) and paste (P).
- Observe that paste is slightly slow and 'P' shows up for a split second before it disappears and the word from the buffer is actually pasted.
Expected behaviour
I expect paste that follows this sequence to be immediate and to not see the 'P' being displayed for a split second.
I tried to load vim without .vimrc and the issue persists.
vim -N -u NONE test
Version of Vim
VIM - Vi IMproved 9.0 (2022 Jun 28, compiled Jul 2 2023 20:24:33) macOS version - arm64 Included patches: 1-1544
Environment
macOS
TERM = xterm-256color
shell = bash
Logs and stack traces
No response
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
lacygoill
ESC P is the Device Control String (aka DCS), which is used as a prefix in various sequences to call Device-Control functions. Vim is waiting to give such a possible sequence enough time to complete. This waiting time is controlled by 'ttimeoutlen' whose default value is -1. It means that Vim actually uses 'timeoutlen', whose default value is 1000 (i.e. 1 second).
You can delay the waiting time by setting 'ttimeoutlen' in your vimrc:
set ttimeoutlen=100
In this example, Vim will only wait 100 ms. Note that this value is set in defaults.vim, which is read when you start Vim with --clean instead of -u NONE.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
Daniel Torres
Closed #13003 as completed.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
Daniel Torres
Thanks for the explanation @lacygoill .
The issue does go away by reducing ttimeoutlen.
I'm closing the issue.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.