Description of problem: When I run "vimx", it launches in a terminal same as "vim" Version-Release number of selected component (if applicable): vim-X11-8.1.1790-1.fc30.x86_64 How reproducible: always Steps to Reproduce: 1.run "vimx" in a terminal 2. 3. Actual results: vim opens in terminal mode Expected results: vim opens in X11 mode Additional info: this is confusing because "/usr/bin/vimx" is just a symlink to "/usr/bin/gvim", which works properly.
Hi Jonathan, thank you for reporting the issue! I was able to reproduce and debugged a little - it is like this because Vim checks the first char of binary name and turn on/off GUI according to it. Then I made a little research - it seems vimx is meant to be without GUI, only in terminal - so Vim is behaving correctly, but vimx is link to bad binary.
I fixed it in RAWHIDE now, but it will bubble down with the newest upstream commit in the future.
"Will be fixed in rawhide", when rawhide will be working after F31 branching again...
According the the man page (man vimx) it is supposed to work like this" vimx Starts gvim in "Vi" mode similar to "vim", but with additional features like xterm clipboard support
Ok, thank you for letting me know! The part of manpage is outdated and does not reflect current state... But just to be sure, I asked on vim_dev if someone knows how vimx should behave.
(In reply to Zdenek Dohnal from comment #5) > Ok, thank you for letting me know! The part of manpage is outdated and does > not reflect current state... > > But just to be sure, I asked on vim_dev if someone knows how vimx should > behave. "vimx" seems to be a Redhat/Fedora invention. The difference if copy-past using the mouse should be handled by vim itself or by the terminal emulator. For example, in "vimx" you can paste from the yank buffer using the middle click. In "vim", paste with middle click pastes from the currently selected text.
I think this is not a bug, and the [fix provided] breaks the current usage of vimx. The man page is correct, vimx being a symbolic link to gvim, will cause gvim to run in "Vi" mode (ie: 'gvim -v'), which means running in the terminal with X11 and clipboard support enabled. One can try this by creating any symbolic link to pointing to /usr/bin/gvim and running it. Pointing vimx to /usr/bin/vim causes clipboard and X11 support to be dropped, because vim is built without support for these. I.e: one won't be able to use the system clipboard when yanking or pasting. Furthermore the fix moves vimx from the vim-X11 package to vim-enhanced, which brakes current usage when upgrading vim-X11 to 2:8.1.1890-1.fc30 (vimx suddenly becomes unavailable). [fix provided]: https://src.fedoraproject.org/rpms/vim/c/ae324f20e3b673a5c648e2434b5e960f7deda3a4?branch=f30
I'm sorry I was confused by two different interpretations how vimx should work - and I do not use so, I did not know how it should work correctly... The commit which puts it back https://src.fedoraproject.org/rpms/vim/c/478d29445ff0aee6b9acfa0279c011af32c7f70d?branch=master .
FEDORA-2019-e574f1bcad has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-e574f1bcad
(In reply to Hunor Csomortáni from comment #7) > > > Pointing vimx to /usr/bin/vim causes clipboard and X11 support to be > dropped, because vim is built without support for these. I.e: one won't be > able to use the system clipboard when yanking or pasting. > > To be more specific: "+p will paste in the contents from the clipboard, and "*p will paste in from the select buffer.
vim-8.1.1912-1.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-e574f1bcad
*** Bug 1744927 has been marked as a duplicate of this bug. ***
vim-8.1.1912-1.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report.