search

conda-forge / vim-feedstock

A conda-smithy repository for vim.
BSD 3-Clause "New" or "Revised" License
3 stars 11 forks source link

gui support #1615

Open timsnyder opened 2 years ago

timsnyder commented 2 years ago

Solution to issue cannot be found in the documentation.

Issue

My workflow with vim for the past 20+ years been that I'll vim files at the cmdline and if I end up wanting to keep them around for awhile, I use the :gui command to launch the gtk (or whatever gui framework) gui window. I also find that some things like selecting fonts are so much easier with the gui. Finally the :drop command is only available when gui support is built into vim and I use it quite a bit in some custom commands I have, specifically what I map to gsf in Normal mode. My gsf does the same thing as gf (open the filename under the cursor) except that it uses :drop where gf uses :e. :drop splits the file into another window if it isn't already open, otherwise, it just moves the cursor to the window that has the file open (I think it might also work with tabs but I don't use those, they didn't exist when I learned vim). I've never bothered to ask Bram why :drop requires the GUI support. It's a useful command even in terminal-display vim

I understand that the gui support makes the package bigger. I'm proposing that we add a vim-gui version of the package that gets built with gui support and that each version of the package run_constrains the other to avoid conflicting weirdness. The reason for needing to make them mutually exclusive is because the non-gui vim executable knows that it was built with gui support and can do things like :gui or :drop.

I'm happy to provide a PR that would do this. I just wanted to ask @conda-forge/vim whether you'd be willing to accept such a PR before doing the work. I guess I also wonder whether we should make this feedstock a split package to do both or if vim-gui should be made a new feedstock?

Installed packages

doesn't have to do with installing package

Environment info

or my environment
matthiasdiener commented 2 years ago

GUI support would definitely be interesting @timsnyder ! My suggestion is to keep it in this feedstock as a split package as you suggested. Please feel free to open a PR with this.