[vim/vim] Vim requires libwayland-client.so.0 to be installed, even on a server (Issue #17633)
DamianBossPL
DamianBossPL created an issue (vim/vim#17633)Steps to reproduce
- Ensure vim is installed on a system without wayland
- Try to run vim from the terminal
- Be greeted with
vim: error while loading shared libraries: libwayland-client.so.0: cannot open shared object file: No such file or directory
Expected behaviour
Vim should run as normal, discarding wayland clipboard.
Version of Vim
9.1
Environment
Operating system: Arch Linux x86_64
Terminal: /dev/pts/0 (ssh)
Value of $TERM: xterm-256color
Shell: zsh 5.9
Logs and stack traces
vim: error while loading shared libraries: libwayland-client.so.0: cannot open shared object file: No such file or directory—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
Christian Brabandt
chrisbra left a comment (vim/vim#17633)did you compile Vim yourself? Can you please share the configure log? Also you may want to compile using --without wayland configure switch.
I think configure should have disabled wayland feature, if those libraries are not present?
cc @64-bitman fyi
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
DamianBossPL
Closed #17633 as completed.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
DamianBossPL
DamianBossPL left a comment (vim/vim#17633)did you compile Vim yourself? Can you please share the configure log? Also you may want to compile using
--without waylandconfigure switch.I think configure should have disabled wayland feature, if those libraries are not present?
cc @64-bitman fyi
I didn't compile vim myself. I installed it straight from pacman.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
DamianBossPL
DamianBossPL left a comment (vim/vim#17633)accidental close
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
DamianBossPL
Reopened #17633.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
Christian Brabandt
chrisbra left a comment (vim/vim#17633)Then this sounds like a packaging issue from Arch. Can you please also report over there?
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
Foxe Chen
64-bitman left a comment (vim/vim#17633)Yeah this is a packaging issue
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
Marcel Svitalský
svitalsky left a comment (vim/vim#17633)I cannot even compile Vim on a system without Wayland (Ubuntu 16.04). Should I create new issue for that or does it belong here?
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
Christian Brabandt
chrisbra left a comment (vim/vim#17633)Please create a new issue with configure log etc. BTW: you can use --without-wayland to compile without wayland support.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
Christian Brabandt
chrisbra left a comment (vim/vim#17633)Nevermind, someone else already created it: #17634
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
JtMotoX
JtMotoX left a comment (vim/vim#17633)I am unable to use vim on my pikvm. Any fix or workaround that does not involve compiling vim?
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
Christian Brabandt
chrisbra left a comment (vim/vim#17633)If you are on Arch, please report over there to have this fixed.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
Christian Brabandt
chrisbra left a comment (vim/vim#17633)this has been fixed on Arch here: https://gitlab.archlinux.org/archlinux/packaging/packages/vim/-/commit/df4c250650026ad7900bee59144aa2b0b560767e
I am closing this one as not a bug for Vim.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
Christian Brabandt
Closed #17633 as not planned.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
JtMotoX
JtMotoX left a comment (vim/vim#17633)this has been fixed on Arch here: https://gitlab.archlinux.org/archlinux/packaging/packages/vim/-/commit/df4c250650026ad7900bee59144aa2b0b560767e
I am closing this one as not a bug for Vim.
Confirmed. Thanks 👍
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
Bones
TerrellAW left a comment (vim/vim#17633)did you compile Vim yourself? Can you please share the configure log? Also you may want to compile using
--without waylandconfigure switch.I think configure should have disabled wayland feature, if those libraries are not present?
cc @64-bitman fyi
Sorry for responding to such an old issue, but can you tell me what you mean by this? If I do make --without wayland I get an error.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today!
You are receiving this because you are subscribed to this thread.
Christian Brabandt
chrisbra left a comment (vim/vim#17633)Please give exact reproduction steps when building vim from master. make --without wayland is not the correct way to build Vim.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today!
You are receiving this because you are subscribed to this thread.
Bones
TerrellAW left a comment (vim/vim#17633)Please give exact reproduction steps when building vim from master.
make --without waylandis not the correct way to build Vim.
I'm having trouble finding the correct way to build vim. I think I'm supposed to use configure to set build options but Vim is still building the wayland version.
From the root dir vim/ I run ./configure --without-wayland and then I run make and trying to copy and paste within vim still pastes a wayland not found error.
I can't find any clear documentation on this and I'm not sure where I'm supposed to go to find this information. src/INSTALL does not have examples of shell commands to build a configured vim with manually set flags in the configure shell program. Sorry if there is an answer for this in the docs, I just can't find it.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today!
You are receiving this because you are subscribed to this thread.
Foxe Chen
64-bitman left a comment (vim/vim#17633)Please give exact reproduction steps when building vim from master.
make --without waylandis not the correct way to build Vim.I'm having trouble finding the correct way to build vim. I think I'm supposed to use
configureto set build options but Vim is still building the wayland version.From the root dir
vim/I run./configure --without-waylandand then I runmakeand trying to copy and paste within vim still pastes a wayland not found error.I can't find any clear documentation on this and I'm not sure where I'm supposed to go to find this information.
src/INSTALLdoes not have examples of shell commands to build a configured vim with manually set flags in theconfigureshell program. Sorry if there is an answer for this in the docs, I just can't find it.
If you want to build without wayland support:
cd src
./configure --without-wayland
make—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today!
You are receiving this because you are subscribed to this thread.
Christian Brabandt
chrisbra left a comment (vim/vim#17633)yes that should be correct, potentially run make distclean first, just to make sure we are starting fresh without anything cached
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today!
You are receiving this because you are subscribed to this thread.
Bones
TerrellAW left a comment (vim/vim#17633)I ran make distclean and then I ran these commands:
cd src
./configure --without-wayland
make
I am still unable to properly copy and paste, if I select text and press y and then press p to paste, I get this output:
Failed to connect to a Wayland server: No such file or directory
Note: WAYLAND_DISPLAY is unset (falling back to wayland-0)
Note: XDG_RUNTIME_DIR is set to /run/user/1000
Please check whether /run/user/1000/wayland-0 socket exists and is accessible.
The system has both wayland and X11 environments installed, but it is currently running an X11 environment via Qtile. Is autoconf detecting wayland and automatically building for it despite the --without-wayland flag?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today!
You are receiving this because you are subscribed to this thread.
Foxe Chen
64-bitman left a comment (vim/vim#17633)I ran
make distcleanand then I ran these commands:cd src ./configure --without-wayland makeI am still unable to properly copy and paste, if I select text and press
yand then presspto paste, I get this output:Failed to connect to a Wayland server: No such file or directory Note: WAYLAND_DISPLAY is unset (falling back to wayland-0) Note: XDG_RUNTIME_DIR is set to /run/user/1000 Please check whether /run/user/1000/wayland-0 socket exists and is accessible.The system has both wayland and X11 environments installed, but it is currently running an X11 environment via Qtile. Is autoconf detecting wayland and automatically building for it despite the
--without-waylandflag?
Can you paste the full output of ./configure --without-wayland? Thanks
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today!
You are receiving this because you are subscribed to this thread.
Bones
TerrellAW left a comment (vim/vim#17633)I ran
make distcleanand then I ran these commands:cd src ./configure --without-wayland makeI am still unable to properly copy and paste, if I select text and press
yand then presspto paste, I get this output:Failed to connect to a Wayland server: No such file or directory Note: WAYLAND_DISPLAY is unset (falling back to wayland-0) Note: XDG_RUNTIME_DIR is set to /run/user/1000 Please check whether /run/user/1000/wayland-0 socket exists and is accessible.The system has both wayland and X11 environments installed, but it is currently running an X11 environment via Qtile. Is autoconf detecting wayland and automatically building for it despite the
--without-waylandflag?Can you paste the full output of
./configure --without-wayland? Thanks
configure: creating cache auto/config.cache
checking whether make sets $(MAKE)... yes
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether the compiler supports GNU C... yes
checking whether gcc accepts -g... yes
checking for gcc option to enable C11 features... none needed
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for fgrep... /usr/bin/grep -F
checking for gawk... gawk
checking for strip... strip
checking for sys/wait.h that is POSIX.1 compatible... yes
checking for pkg-config... /usr/bin/pkg-config
checking --enable-fail-if-missing argument... no
checking for clang version... N/A
checking for buggy tools... - sh is 'GNU bash, version 5.3.9(1)-release (x86_64-redhat-linux-gnu)
Copyright (C) 2025 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software; you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.' - probably OK.
checking uname... Linux
checking uname -r... 7.1.4-204.fc44.x86_64
checking uname -m... x86_64
checking for Haiku... no
checking for QNX... no
checking for Darwin (Mac OS X)... no
checking for stdio.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for strings.h... yes
checking for sys/stat.h... yes
checking for sys/types.h... yes
checking for unistd.h... yes
checking for sys/time.h... yes
checking for sys/select.h... yes
checking for sys/socket.h... yes
checking for AvailabilityMacros.h... no
checking for dispatch/dispatch.h... no
checking --with-local-dir argument... Defaulting to /usr/local
checking --with-vim-name argument... Defaulting to vim
checking --with-ex-name argument... Defaulting to ex
checking --with-view-name argument... Defaulting to view
checking --with-global-runtime argument... no
checking --with-modified-by argument... no
checking if character set is EBCDIC... no
checking --disable-smack argument... no
checking for linux/xattr.h... yes
checking for sys/xattr.h... yes
checking for XATTR_NAME_SMACKEXEC in linux/xattr.h... checking for egrep -e... (cached) /usr/bin/grep -E
no
checking --disable-selinux argument... no
checking for is_selinux_enabled in -lselinux... yes
checking for selinux/selinux.h... yes
checking --enable-xattr argument... yes
checking for sys/xattr.h... (cached) yes
checking --with-features argument... Defaulting to huge
checking --with-compiledby argument... no
checking --disable-xsmp argument... no
checking --disable-xsmp-interact argument... no
checking diff feature... enabled
checking --enable-luainterp argument... no
checking --enable-mzschemeinterp argument... no
checking --enable-perlinterp argument... no
checking --enable-pythoninterp argument... no
checking --enable-python3interp argument... no
checking --enable-tclinterp argument... no
checking --enable-rubyinterp argument... no
checking --enable-cscope argument... yes
checking --disable-netbeans argument... no
checking --disable-channel argument... no
checking for socket in -lsocket... no
checking for gethostbyname in -lnsl... no
checking whether compiling with IPv6 networking is possible... yes
checking for inet_ntop... yes
checking --enable-terminal argument... defaulting to yes
checking --enable-autoservername argument... no
checking --enable-multibyte argument... yes
checking --disable-rightleft argument... no
checking --disable-arabic argument... no
checking --enable-xim argument... defaulting to auto
checking --enable-fontset argument... no
checking if shm_open is available... yes
checking --with-wayland argument... checking for xmkmf... no
checking for X... libraries , headers
checking for gethostbyname... yes
checking for connect... yes
checking for remove... yes
checking for shmat... yes
checking for IceConnectionNumber in -lICE... yes
checking if X11 header files can be found... yes
checking for _XdmcpAuthDoIt in -lXdmcp... no
checking for IceOpenConnection in -lICE... yes
checking for XpmCreatePixmapFromData in -lXpm... no
checking if X11 header files implicitly declare return values... no
checking size of wchar_t... 4
checking --enable-gui argument... yes/auto - automatic GUI support
checking whether or not to look for GTK+ 2... yes
checking whether or not to look for GNOME... no
checking whether or not to look for GTK 4... yes
checking whether or not to look for GTK+ 3... yes
checking whether or not to look for Motif... yes
checking --disable-gtktest argument... gtk test enabled
checking for pkg-config gtk+-3.0... found
checking for GTK - version >= 3.0.0... yes; found version 3.24.52
checking ability to compile GTK test program... yes
checking version of Gdk-Pixbuf... OK.
checking for glib-compile-resources... /usr/bin/glib-compile-resources
checking glib-compile-resources... usable.
checking --disable-icon-cache-update argument... not set
checking for gtk-update-icon-cache... /usr/bin/gtk-update-icon-cache
checking --disable-desktop-database-update argument... not set
checking for update-desktop-database... /usr/bin/update-desktop-database
checking for X11/SM/SMlib.h... yes
checking for X11/xpm.h... no
checking for X11/Sunkeysym.h... yes
checking for XIMText in X11/Xlib.h... yes
X GUI selected; xim has been enabled
checking for /proc link to executable... /proc/self/exe
checking for CYGWIN or MSYS environment... no
checking whether toupper is broken... no
checking whether __DATE__ and __TIME__ work... yes
checking whether __attribute__((unused)) is allowed... yes
checking for dirent.h that defines DIR... yes
checking for library containing opendir... none required
checking for sys/wait.h... (cached) yes
checking for waitpid... yes
checking for stdint.h... (cached) yes
checking for stdlib.h... (cached) yes
checking for string.h... (cached) yes
checking for sys/select.h... (cached) yes
checking for sys/utsname.h... yes
checking for termcap.h... yes
checking for fcntl.h... yes
checking for sgtty.h... yes
checking for sys/ioctl.h... yes
checking for sys/time.h... (cached) yes
checking for sys/types.h... (cached) yes
checking for termio.h... no
checking for iconv.h... yes
checking for inttypes.h... (cached) yes
checking for langinfo.h... yes
checking for math.h... yes
checking for unistd.h... (cached) yes
checking for stropts.h... no
checking for errno.h... yes
checking for sys/resource.h... yes
checking for sys/systeminfo.h... no
checking for locale.h... yes
checking for sys/stream.h... no
checking for termios.h... yes
checking for libc.h... no
checking for sys/statfs.h... yes
checking for poll.h... yes
checking for sys/poll.h... yes
checking for pwd.h... yes
checking for utime.h... yes
checking for sys/param.h... yes
checking for sys/ptms.h... no
checking for libintl.h... yes
checking for libgen.h... yes
checking for util/debug.h... no
checking for util/msg18n.h... no
checking for frame.h... no
checking for sys/acl.h... no
checking for sys/access.h... no
checking for sys/sysinfo.h... yes
checking for wchar.h... yes
checking for wctype.h... yes
checking for sys/ptem.h... no
checking for sys/sysctl.h... no
checking for pthread_np.h... no
checking for strings.h... (cached) yes
checking if strings.h can be included after string.h... yes
checking for an ANSI C-conforming const... yes
checking for working volatile... yes
checking for mode_t... yes
checking for off_t... yes
checking for pid_t... yes
checking for size_t... yes
checking for uid_t... yes
checking for gid_t... yes
checking for uint32_t... yes
checking for ino_t... yes
checking for dev_t... yes
checking whether byte ordering is bigendian... no
checking for inline... inline
checking for rlim_t... yes
checking for stack_t... yes
checking whether stack_t has an ss_base field... no
checking --with-tlib argument... empty: automatic terminal library selection
checking for tgetent in -ltinfo... yes
checking whether we talk terminfo... yes
checking what tgetent() returns for an unknown terminal... zero
checking whether termcap.h contains ospeed... yes
checking whether termcap.h contains UP, BC and PC... yes
checking whether tputs() uses outfuntype... no
checking whether del_curterm() can be used... yes
checking whether sys/select.h and sys/time.h may both be included... yes
checking for /dev/ptc... no
checking for SVR4 ptys... yes
checking for ptyranges... don't know
checking for struct sigcontext... yes
checking getcwd implementation is broken... no
checking for fchdir... yes
checking for fchown... yes
checking for fchmod... yes
checking for fsync... yes
checking for getcwd... yes
checking for getpseudotty... no
checking for getpwent... yes
checking for getpwnam... yes
checking for getpwuid... yes
checking for getrlimit... yes
checking for gettimeofday... yes
checking for localtime_r... yes
checking for lstat... yes
checking for memset... yes
checking for mkdtemp... yes
checking for nanosleep... yes
checking for opendir... yes
checking for putenv... yes
checking for qsort... yes
checking for readlink... yes
checking for select... yes
checking for setenv... yes
checking for getpgid... yes
checking for setpgid... yes
checking for setsid... yes
checking for sigaltstack... yes
checking for sigstack... yes
checking for sigset... yes
checking for sigsetjmp... no
checking for sigaction... yes
checking for sigprocmask... yes
checking for sigvec... no
checking for strcasecmp... yes
checking for strcoll... yes
checking for strerror... yes
checking for strftime... yes
checking for stricmp... no
checking for strncasecmp... yes
checking for strnicmp... no
checking for strpbrk... yes
checking for strptime... yes
checking for strtol... yes
checking for tgetent... yes
checking for towlower... yes
checking for towupper... yes
checking for iswupper... yes
checking for tzset... yes
checking for usleep... yes
checking for utime... yes
checking for utimes... yes
checking for mblen... yes
checking for ftruncate... yes
checking for unsetenv... yes
checking for posix_openpt... yes
checking for clock_gettime... yes
checking for sync... yes
checking types of arguments for select... int,fd_set *,struct timeval *
checking for declarations of fseeko and ftello... yes
checking for option for large files... none needed
checking --enable-canberra argument... Defaulting to yes
checking for libcanberra... no; try installing libcanberra-dev
checking --enable-libsodium argument... Defaulting to yes
checking for libsodium... no; try installing libsodium-dev
checking for st_blksize... yes
checking for timer_create without -lrt... yes
checking if timer_create works... yes
checking whether stat() ignores a trailing slash... no
checking for nanoseconds field of struct stat... st_mtim.tv_nsec
checking for iconv_open()... yes
checking for nl_langinfo(CODESET)... yes
checking for strtod in -lm... yes
checking for isinf()... yes
checking for isnan()... yes
checking --disable-acl argument... no
checking for acl_get_file in -lposix1e... no
checking for acl_get_file in -lacl... no
checking for POSIX ACL support... no
checking for acl_get in -lsec... no
checking for Solaris ACL support... no
checking for AIX ACL support... no
checking for pango_shape_full... yes
checking --enable-gpm argument... yes
checking for gpm... no
checking --disable-sysmouse argument... no
checking for sysmouse... no
checking for FD_CLOEXEC... yes
checking for rename... yes
checking for dirfd... yes
checking for flock... yes
checking for sysctl... not usable
checking for sysinfo... yes
checking for sysinfo.mem_unit... yes
checking for sysinfo.uptime... yes
checking for sysconf... yes
checking for _SC_SIGSTKSZ via sysconf()... yes
checking size of int... 4
checking size of long... 8
checking size of time_t... 8
checking size of off_t... 8
checking uint32_t is 32 bits... ok
checking whether memmove handles overlaps... yes
checking whether X_LOCALE needed... no
checking whether Xutf8SetWMProperties() can be used... yes
checking for _xpg4_setrunelocale in -lxpg4... no
checking how to create tags... ctags -I INIT+,INIT2+,INIT3+,INIT4+,INIT5+ --fields=+S
checking how to run man with a section nr... man -s
checking --disable-nls argument... no
checking for msgfmt... msgfmt
checking for NLS... gettext() works
checking for bind_textdomain_codeset... yes
checking for dgettext... yes
yes
checking for _nl_msg_cat_cntr... yes
checking if msgfmt supports --desktop... yes
checking if msgfmt supports --no-convert... yes
checking for dlfcn.h... yes
checking for dlopen()... yes
checking for dlsym()... yes
checking for setjmp.h... yes
checking for GCC 3 or later... yes
checking whether we need -D_FORTIFY_SOURCE=1... yes
checking whether we need to force -D_FILE_OFFSET_BITS=64... no
checking linker --as-needed support... yes
configure: updating cache auto/config.cache
configure: creating auto/config.status
config.status: creating auto/config.mk
config.status: creating auto/config.h
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today!
You are receiving this because you are subscribed to this thread.
Foxe Chen
64-bitman left a comment (vim/vim#17633)This output you gave:
Failed to connect to a Wayland server: No such file or directory
Note: WAYLAND_DISPLAY is unset (falling back to wayland-0)
Note: XDG_RUNTIME_DIR is set to /run/user/1000
Please check whether /run/user/1000/wayland-0 socket exists and is accessible.
Is the message that wl-clipboard gives when it cannot connect to the Wayland compositor. can you show output of 'clipmethod' option, v:clipmethod, and :version?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today!
You are receiving this because you are subscribed to this thread.
Bones
TerrellAW left a comment (vim/vim#17633)I'm not sure how to get the clipmethod information. In my .vimrc I did set clipboard=unnamedplus if that helps. This used to be all I needed.
Here is the :version info:
VIM - Vi IMproved 9.2 (2026 Feb 14, compiled Jul 27 2026 13:28:15)
Included patches: 1-858
Compiled by mr-bones@fedora
Huge version with GTK3 GUI. Features included (+) or not (-):
+acl +clientserver +dialog_con_gui +float +image_sixel +localmap +mouse_urxvt +popupwin +smartindent -tag_old_static +vartabs +windows
+arabic +clipboard +diff +folding +insert_expand -lua +mouse_xterm +postscript +socketserver -tcl +vertsplit +writebackup
+autochdir +clipboard_provider +digraphs -footer +ipv6 +menu +mouseshape +printer -sodium +termguicolors +vim9script +X11
+autocmd +cmdline_compl +dnd +fork() +job +mksession +multi_byte +profile -sound +terminal +viminfo +xattr
-autoservername +cmdline_hist -ebcdic +gettext +jumplist +modify_fname +multi_lang -python +spell +terminfo +virtualedit -xfontset
+balloon_eval +cmdline_info +emacs_tags -hangul_input +keymap +mouse -mzscheme -python3 +startuptime +termresponse +visual +xim
+balloon_eval_term +comments +eval +iconv +lambda +mouse_dec +netbeans_intg +quickfix +statusline +textobjects +visualextra -xpm
+browse +conceal +ex_extra +image +langmap -mouse_gpm +num64 +reltime -sun_workshop +textprop +vreplace +xsmp_interact
++builtin_terms +cryptv +extra_search +image_cairo +libcall -mouse_jsbterm +packages +rightleft +syntax +timers -wayland +xterm_clipboard
+byte_offset +cscope -farsi -image_gdi +linebreak +mouse_netterm +path_extra -ruby +tabpanel +title -wayland_clipboard -xterm_save
+channel +cursorbind +file_in_path -image_gdk +lispindent +mouse_sgr -perl +scrollbind -tag_any_white +toolbar +wildignore
+cindent +cursorshape +find_in_path +image_kitty +listcmds -mouse_sysmouse +persistent_undo +signs +tag_binary +user_commands +wildmenu
system vimrc file: "$VIM/vimrc"
user vimrc file: "$HOME/.vimrc"
2nd user vimrc file: "~/.vim/vimrc"
3rd user vimrc file: "~/.config/vim/vimrc"
user exrc file: "$HOME/.exrc"
system gvimrc file: "$VIM/gvimrc"
user gvimrc file: "$HOME/.gvimrc"
2nd user gvimrc file: "~/.vim/gvimrc"
3rd user gvimrc file: "~/.config/vim/gvimrc"
defaults file: "$VIMRUNTIME/defaults.vim"
system menu file: "$VIMRUNTIME/menu.vim"
fall-back for $VIM: "/usr/local/share/vim"
Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK -I/usr/include/gtk-3.0 -I/usr/include/pango-1.0 -I/usr/include/cloudproviders -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/glycin-2 -I/usr/include/at-spi2-
atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/atk-1.0 -I/usr/lib64/pkgconfig/../../include/dbus-1.0 -I/usr/lib64/pkgconfig/../../lib64/dbus-1.0/include -I/usr/include/fribidi -I/usr/include/libxml2 -I/usr/include/pixman-1 -I/usr/include
/harfbuzz -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/sysprof-6 -g -O2 -D_REENTRANT -U_FORTI
FY_SOURCE -D_FORTIFY_SOURCE=1
Linking: gcc -L/usr/local/lib -Wl,--as-needed -o vim -lgtk-3 -lgdk-3 -lpangocairo-1.0 -lcairo-gobject -lgdk_pixbuf-2.0 -latk-1.0 -lpango-1.0 -lcairo -lharfbuzz -lgio-2.0 -lgobject-2.0 -lglib-2.0 -lz -lSM -lICE -lXt -lX11 -lSM -lICE -lm -lt
info -lselinux
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today!
You are receiving this because you are subscribed to this thread.
Foxe Chen
64-bitman left a comment (vim/vim#17633)I mean show the output of :set 'clipmethod'? and also output of :echo v:clipmethod
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today!
You are receiving this because you are subscribed to this thread.
Bones
TerrellAW left a comment (vim/vim#17633)You have the
-wayland_clipboarddisabled, so maybe the issue is due to your config? DId you run Vim with--clean? Thanks
The output of :set clipmethod is clipmethod=wayland,x11 and the output og :echo v:clipmethod is x11.
My config doesn't have any plugins for wayland and only has set clipboard=unnamedplus relating to the clipboard.
It turns out I have wl-clipboard installed, I uninstalled to see what would happen and I get this output: /bin/bash: line 1: wl-paste: command not found. I think you're right about this issue being unrelated to vim, something is forcing vim to use wl-copy and wl-paste despite them not being set in my .vimrc. I really don't know what is going on, I think I need to switch off of Fedora 44.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today!
You are receiving this because you are subscribed to this thread.
Foxe Chen
64-bitman left a comment (vim/vim#17633)I think this an issue with Fedora's version of Vim. wl-paste is not called in any of the default Vim runtime files
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today!
You are receiving this because you are subscribed to this thread.
Bones
TerrellAW left a comment (vim/vim#17633)I think this an issue with Fedora's version of Vim.
wl-pasteis not called in any of the default Vim runtime files
I built vim from source to avoid using Fedora's version. This is really strange.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today!
You are receiving this because you are subscribed to this thread.
Foxe Chen
64-bitman left a comment (vim/vim#17633)I think this an issue with Fedora's version of Vim.
wl-pasteis not called in any of the default Vim runtime filesI built vim from source to avoid using Fedora's version. This is really strange.
Are you using the runtime files from the vim compiled from source, or the runtime files from the fedora repository? Maybe its an issue with your .bashrc (or equivalent) possibly
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today!
You are receiving this because you are subscribed to this thread.
Bones
TerrellAW left a comment (vim/vim#17633)Its possible Fedora's vim wasn't fully uninstalled and that its messing things up, or some other vim-related package. I really don't know, thank you both for the help. I think my best option is to switch distros at this point.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today!
You are receiving this because you are subscribed to this thread.
Bones
TerrellAW left a comment (vim/vim#17633)Sorry guys, it was a problem with my .vimrc after all. Yesterday I decided to merge my two dotfile branches I keep on GitHub, I didn't properly check to make sure the changes would only have x11 stuff.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today!
You are receiving this because you are subscribed to this thread.