91–98 of 98 posts
I created a fork of janus that removes NERDTree from the distribution just for using it with alloy's fork. Also some other nice textmate behavior like quote/brace completion is included. So to get started immediately you can use it too, it is on github: https://github.com/JFrolich/janus
Earlier quoted context omitted.
PeepOpen is the main reason I use MacVim. So excellent.
I have struggled for a while to get PeepOpen and MacVim working together. I can run :PeepOpen, and it will switch to the running peepopen application, but it doesn't load up with the project files. I've tried all sorts of .vimrc config settings that the internet has to offer, but none worked. What's in your config for it?
In MacVim preferences, I set "Open files from applications" to "in the current window / and set the arglist"
Earlier quoted context omitted.
It's only clunky when it isn't second nature. If you invest the time required to use it without thinking, you'll find it's quite elegant.
I can do thousands of other things with that time that are worth infinitely more to me. As it happens, I do. It's a text editor , not a religion.
It's an awesome text editor. Who said anything about religion?
Earlier quoted context omitted.
Unfortunately, the remote features require a GUI version of vim. Personally, I prefer to run vim in a tab of my terminal.
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. 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…
You do have to have an X server available though; the client/server communication occurs via X.
Earlier quoted context omitted.
Under 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 pr…
The 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…
I haven't had any trouble binding -based combinations. All my window-manager commands are based on , leaving and open for other things. I assume is conflicting with tab swapping in gnome-terminal or something similar.
Earlier quoted context omitted.
The 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…
I'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 -based combinations. All my window-manager commands are based on , leaving and open for other things. I assume is conflicting with tab swapping in gnome-terminal or something similar.
I've always been a little puzzled by people who use a file-drawer or file-list or similar addon with Vim, and I now I think I know why: I'm guessing most of these people have Vim open as their One Tool, much like another programmer might have Xcode or Visual Studio open as their One Tool, and they want to get everything done in it. At work, I usually have at least two windows open at all times: Vim full-screen on one…