Live data from Hacker News

Vim After 11 Years

statico.github.com

31–40 of 254 posts

Re: Vim After 11 Years

#31
post #21

One of Vim’s strengths is that it starts lightning fast, so starting Vim from the terminal is trivial. With a modern, 256-color terminal like iTerm2 or Gnome Terminal, it will even look like gVim. But the best part is that you can drop into the command line at any time with Ctrl-Z, which suspends Vim, and your working directory is where you left off. Is there any reason to do this instead of !sh within Vim to drop in…

IIRC, !sh starts a new shell- so it depends on your context I suppose.

I think this is the explanation, I usually only find myself wanting to temporarily "stop" Vim and do something on the shell for quick one-off commands that are fine in a subshell - not to keep a backgrounded Vim instance around for longer than that. The blog author seems to have a different use in mind.

Re: Vim After 11 Years

#32

I use nvi, and have tried to switch to vim a dozen or so times over the years. But there are so many irritating little quirks and misfeatures and annoyances that I can never manage to fix. Does anyone know of a guide to getting a sane, non-broken vim working with some basic plugins like syntastic? Last time I tried I couldn't bind F-keys for some reason, I couldn't get syntastic's error marking column to stay on inst…

>> Does anyone know of a guide to getting a sane, non-broken vim working with some basic plugins like syntastic

There are a number of vim-setups that are popular. janus (https://github.com/carlhuda/janus), spf13 (https://github.com/spf13/spf13-vim) are pretty popular ones.

>>Last time I tried I couldn't bind F-keys for some reason F keys bind fine for me, using OS X Terminal, and gnome-shell in linux. Are you using an esoteric term?

>> I couldn't get syntastic's error marking column to stay on instead of shifting my text back and forth all the time That is using the SignColumn part of vim. As far as I know, vim doesn't allow you to force the existance of SignColumn. You can open up a bug report at their Google Code repo if you think its worthwhile

>> I couldn't get auto-complete mapped to tab properly Depending on your language, YouCompleteMe (https://github.com/Valloric/YouCompleteMe) is amazing, but if you don't do C based stuff NeoComplCache is great too (http://www.vim.org/scripts/script.php?script_id=2620)

>> the extra functionality of vim ends up being counter-productive when none of it works right To be fair, thats true of any tool.

Re: Vim After 11 Years

#33
post #24

Every time I read an article like this, it's how a power user installs an array of plugins and customizations to really soup up Vim, which to me kind of misses the point. If you want that level whiz-bang, use Coda or Sublime Text 2 or Eclipse or whatever. I don't recall where I saw this, but someone advised disabling syntax coloring in your editor to remove a crutch (and, secondarily, to visually simplify your enviro…

A lot of us do development on remote servers. Using vim in a terminal on the server is a heck of a lot snappier than a local editor over a remote connection. Also makes reconnecting your dev environment as easy as tmux a -d and allows me to do so from multiple machines.

Re: Vim After 11 Years

#37
post #9

Why do people keep suggesting iTerm2? The built-in terminal app on the Mac does Unicode and 256 colors just fine.

Split panes is pretty much the main reason I need iTerm2. That, combined with system-wide hotkey toggling (which I used to get on Terminal with Visor), and Send Commands to All Sessions mode (cmd-ctrl-i, I think) makes me a happy command liner.

Re: Vim After 11 Years

#38
post #8

netrw comes by default. No need to install NERDTree.

I've recently uninstalled NERDTree in favor of netrw and I've been presently surprised at how little I miss NERDTree and how much more productive I am on default vim installations.

I used NERDTree when I was starting Vim, but uninstalling and hating it were essential steps towards Vim nirvana.

Because then I found out about ctrlp.vim and :E, two things that makes NERDTree completely useless to me.

Re: Vim After 11 Years

#39
The author mentioned CtrlP for fuzzy filename matching. Its great because it's in pure Vimscript, but in my experience it becomes unusably slow for moderately sized projects. A month or two ago, I switched back to CommandT (requires Vim to be compiled with Ruby support, engine written in C) and haven't thought twice about it since then.

Re: Vim After 11 Years

#40
Lots of people seem to declare ; or , to be useless keys and remap them. They're two of my most used movement keys in certain circumstances.

I used to have , remapped to but switched back when I realised what I was missing out on. I'd advise anybody else to reconsider if they've made the same mistake I did.

Post reply on HN