Live data from Hacker News

VimConf

vimconf.org

41–50 of 55 posts

Re: VimConf

#42
post #35

Earlier quoted context omitted.

I might be wrong here as I'm relatively new to vim and haven't used VS, but I'm pretty sure omnicompletion is the equivalent of intellisense in vim, http://vnfiles.ign.com/ects/css-tricks/VideoCast-101.mov

IntelliSense knows the library, omnicompletion just autocompletes similar words in the current file.

omnicompletion, by default, completes against words in any file currently open in any buffer. But it's also now pretty programmable, though I don't I currently use any of the languages that have good support built out for them.

Re: VimConf

#43

Signed up. Id like to use vim since i like the concept but it seems so damn hard to get into. The post yesterday "learn vim progressively" was interesting though. Not sure i know what it is though. I really like VS debugger and programming in C#, C++ (both with VS). So, what exactly will i give up if i switch to vim?

I recently took the plunge. I had been using e-TextEditor for everything but .NET, and VS for .NET. Now I'm using gVim for the majority of my editing for all languages I am working in. However, I still use Visual Studio with ReSharper for certain things: debugging, intellisense (only when I'm stuck; I'm trying not to rely on it much. you can also use vim plugins or create your own to let you quickly jump to MSDN and…

I'd second ViEmu. The price is a little steep (or was three or four years ago), but I used it through the trial and it was pretty comfortable.

These days I do a lot of my C# coding in Visual Studio, but have a shortcut key to open the current file in GVim to do heavy lifting. For what it's worth, to do that, I added gvim as an external tool with the arguments:

--servername "$(SolutionFileName)" --remote-silent +$(CurLine) "$(ItemPath)"

Which keeps all the files you open from a given solution in the same GVim instance (nice if you edit multiple solutions at once).

Re: VimConf

#44

I've never understood people's obsession with vim. I used it for a few months, then timed myself doing the same tasks with vim and gedit. Gedit was faster by a significant margin.

When you actually master Vim and all its motions it's astoundingly fast.

Re: VimConf

#45
post #39

I've never understood people's obsession with vim. I used it for a few months, then timed myself doing the same tasks with vim and gedit. Gedit was faster by a significant margin.

Do you mind telling what was faster? I'm really curious.

The vim tutorial.

Click-and-type is really quite fast once you try to master it. Double-click to select a token, triple-click to select a line, etc. On a laptop (or on a Kinesis Advantage (awesome ergonomic keyboard) with a center-mounted touchpad) the mouse isn't much of a context switch.

Re: VimConf

#46

I've never understood people's obsession with vim. I used it for a few months, then timed myself doing the same tasks with vim and gedit. Gedit was faster by a significant margin.

When you actually master Vim and all its motions it's astoundingly fast.

I mastered most of the more commonly known motions, including most of the ones on this page (http://yannesposito.com/Scratch/en/blog/Learn-Vim-Progressiv...) and some that aren't on it. It didn't seem to be delivering the promised efficiency improvements, so now I only use it for git commit messages, line editing in zsh, and file processing with macros (which are pretty nice--best way I know of to reformat data; much easier than writing a script). I don't think it was worth it--should have shipped product instead and used nano for my command line editing needs.

Re: VimConf

#48

I've never understood people's obsession with vim. I used it for a few months, then timed myself doing the same tasks with vim and gedit. Gedit was faster by a significant margin.

Try incrementing a number on 500 lines of text. Or stripping trailing whitespace on save. Or fixing the indentation of a large file. Vim is really powerful when it comes to text manipulation.

Re: VimConf

#49
post #16

As far as topics are concerned, I'd really like to see a vim plugin created from start to finish. The tutorials and docs that exist leave a lot to be desired, and this seems like a nice venue to demonstrate (and explain!) the capabilities of the vim plugin system.

While this is an excellent topic for advanced vim users, I suspect that the majority of us would benefit more from a "Beyond the basics" topic.

I'm comfortable with using vim to edit files now and then, but for that role any editor will do. Now I'm willing to invest some time to learn how to harness the full power of vim. Signed up.

Post reply on HN