[vim/vim] pasting from unnamedplus broken since 9.1.1734 (Issue #19050)

snek

unread,

Dec 31, 2025, 7:17:40 AM (6 days ago) 12/31/25

to vim/vim, Subscribed

devsnek created an issue (vim/vim#19050)

Steps to reproduce

After updating to any version past 9.1.1734 (on arch), if you set clipboard=unnamedplus, pasting no longer works. I find that a minimal repro is to launch vim with --clean, run :set clipboard=unnamedplus, type something, then use y and p, and it logs: E353: Nothing in register + instead of pasting whatever you typed. The text you yanked is in the system clipboard though, and can be pasted in other applications. Restarting vim after this point and then using p will also work, until you use y again.

Expected behaviour

pasting works

Version of Vim

9.1.1975

Environment

Operating system: Arch
Terminal: foot
Value of $TERM: xterm-256color
Shell: fish

Logs and stack traces

—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.

Christian Brabandt

unread,

Dec 31, 2025, 9:36:04 AM (6 days ago) 12/31/25

to vim/vim, Subscribed

chrisbra left a comment (vim/vim#19050)

can you please verify using latest master? Also there have been a few additions using e.g. clipmethod. So make sure to test using vim --clean

—
Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.

snek

unread,

Dec 31, 2025, 10:02:33 AM (6 days ago) 12/31/25

to vim/vim, Subscribed

devsnek left a comment (vim/vim#19050)

I just cloned the repo and built with the following (copied from arch PKGBUILD):

 ./configure \
   --prefix=/usr \
   --localstatedir=/var/lib/vim \
   --with-features=huge \
   --with-compiledby='Arch Linux' \
   --enable-gpm \
   --enable-acl \
   --with-x=yes \
   --enable-gui=gtk3 \
   --enable-multibyte \
   --enable-cscope \
   --enable-netbeans \
   --enable-perlinterp=dynamic \
   --enable-python3interp=dynamic \
   --enable-rubyinterp=dynamic \
   --enable-luainterp=dynamic \
   --enable-tclinterp=dynamic \
   --enable-canberra

I still see the same behavior.

—
Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.

Foxe Chen

unread,

Jan 2, 2026, 4:05:52 PM (4 days ago) Jan 2

to vim/vim, Subscribed

64-bitman left a comment (vim/vim#19050)

I cannot reproduce, are you sure this is not due to some external Wayland tool?

—
Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.

snek

unread,

Jan 4, 2026, 3:57:16 PM (2 days ago) Jan 4

to vim/vim, Subscribed

devsnek left a comment (vim/vim#19050)

seems like it may be due to interaction with wl-clip-persist? i'm not sure why specifically vim and only vim would exhibit this behavior though.

—
Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.

Foxe Chen

unread,

Jan 4, 2026, 4:25:30 PM (2 days ago) Jan 4

to vim/vim, Subscribed

64-bitman left a comment (vim/vim#19050)

seems like it may be due to interaction with wl-clip-persist? i'm not sure why specifically vim and only vim would exhibit this behavior though.

It is because Vim essentially has a special mime type that it uses to determine if a selection event is from itself. However, since wl-clip-persist takes in any mime type by default, Vim assumes the selection event is from itself and ignores it.

Looking at wl-clip-persist --help, I suppose the solution would be:

wl-clip-persist --all-mime-type-regex '^(?!application/x-vim-instance).+'f --clipboard ...