5 ms·
Unfortunately, the remote features require a GUI version of vim. Personally, I prefer to run vim in a tab of my terminal.
by JoshTriplett 15y ago
Unfortunately, the remote features require a GUI version of vim. Personally, I prefer to run vim in a tab of my terminal.
- Periodic 15y agoUnder Linux I always run vim in a terminal. Part of this is habit because I (in the past) often edit files on remote computers and I like the consistency. On my mac I end up using MacVim mostly so that my Vim and Terminal apps can be considered separate apps for the purpose of things like spaces, and it just seemed to integrate a little better with the Mac infrastructure. But in general I haven't found a reason to prefer a GUI version over a terminal version when a sufficiently capable terminal is available.
- thristian 15y agoThe reasons I run gvim rather than terminal vim are basically all because sufficiently capable terminals do not exist: - The excellent "solarized" colour scheme only works properly with 24-bit color unless you're willing to mess with the terminal palette and break all your other terminal apps. No terminal I know of supports 24-bit color. - I have a handy keybinding that cycles through open windows and tabs, I find it makes the most sense bound to Ctrl-Tab and Ctrl-Shift-Tab. Neither key can be bound in any terminal I know of.
- grn 15y agoI'm using xterm with Solarized and it works pretty well. gvim is indistinguishable from vim in a terminal. I haven't observed any broken apps.
- Periodic 15y agoI've been using urxvt for a few years now. It supports a full color range and I adopted Solarized for a while, but went back to Tango. I haven't had any trouble binding <ctrl>-based combinations. All my window-manager commands are based on <super>, leaving <alt> and <ctrl> open for other things. I assume <ctrl-tab> is conflicting with tab swapping in gnome-terminal or something similar.
- thristian 15y agoNo, it's just the way that terminals work: "Tab" is transmitted as "Ctrl-I", and there's no way to encode "Ctrl" twice in the input stream.
- thristian 15y agoThe remote features require a version of Vim with GUI features compiled in, but you don't have to run vim in GUI mode to use them. The only difference is that when started in console mode, Vim won't register itself as a server unless it's explicitly told to use a particular server name: vim --servername FOO If you start vim in another tab with the same servername, you can open files in the first Vim, no problem: vim --servername FOO --remote-tab ~/.bashrc
- JoshTriplett 15y ago> The remote features require a version of Vim with GUI features compiled in, but you don't have to run vim in GUI mode to use them. You do have to have an X server available though; the client/server communication occurs via X.