adam/vim
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

patch 9.1.1704: Cannot determine non-X11/Wayland clipmethods

Browse Source 
Problem:  Cannot determine non-X11/Wayland clipmethods
Solution: Add the "gui" value to the 'clipmethod' option (Foxe Chen)

related: #18006
closes: #18067

Signed-off-by: Foxe Chen <chen.foxe@gmail.com>
Signed-off-by: Christian Brabandt <cb@256bit.org>
This commit is contained in:
Foxe Chen
2025-08-27 21:24:40 +02:00
committed by Christian Brabandt
parent 1f51bbc3b9
commit 528196c8a9
11 changed files with 209 additions and 179 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
runtime/doc/wayland.txt
View File

@ -1,4 +1,4 @@
*wayland.txt* For Vim version 9.1. Last change: 2025 Aug 20
*wayland.txt* For Vim version 9.1. Last change: 2025 Aug 27
VIM REFERENCE MANUAL by Bram Moolenaar
@ -22,7 +22,7 @@ multiple Wayland seats in the same Wayland session.
See |gui-wayland|. Please note that when using the GUI, Vim uses the toolkit
such as GTK for accessing the clipboard, and does not access the clipboard
though Wayland. You can check this though the |v:clipmethod| variable, which
should equal to "none" when running the GUI.
should equal to "gui" when running the GUI.
Wayland commands:
*:wlrestore* *:wl*
@ -72,7 +72,7 @@ selections, see |wayland-primary-selection| for more details.
*wayland-persist*
If you use X11 cut buffers, no such things exist on Wayland. Instead to
emulate such functionality, a separate clipboard manager must be used in order
to persist selection data when a Wayland client exists.
to persist selection data when a Wayland client exits.
*wayland-and-x11*
If your version of Vim comes compiled with both X11 and Wayland support, then