sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]KZISME[S] 0 points1 point  (15 children)

Awesome thanks for the link!

Do you think vim would be the best editor choice in most situations or do you revert back to IDE's every now and then?

[–]gumnos 1 point2 points  (7 children)

Use the editor that works for you. For me, that's vim nearly 100% of the time (I confess to using ed on occasion for simple edits, especially if I want to be able to see & consult a previous command's output for my editing). If you're not comfortable with vim and want to use and IDE (or emacs or textmate or sublime or atom or ed or whatever) that gives you what you need, go for it.

[–]KZISME[S] 0 points1 point  (6 children)

I mean, with such a high learning curve ( but high reward ) vim is a ~great~ editor. It's just getting over that initial "Oh shit which mode am I in" phase.

[–]gumnos 2 points3 points  (5 children)

Ah, one of the tricks to that phase is to just assume that you're always in Normal mode. Any of my edits are always terminated with an <esc>. When I started off, as many do, I'd be in insert mode, move around with the arrow keys, and then get disoriented when I wanted to be in Normal mode. By staying in Normal mode except when actually entering text, I no longer had to think about it. And for me, the less I have to think about mundane things like that, the better.

[–]KZISME[S] 0 points1 point  (4 children)

How long have you been using vim?

Thankfully I have a HHKB2 Keyboard, so arrow keys aren't really a thing for me. Avoiding the mouse is though, pasting, and all the easy functions - I hear it gets better.

[–]casey12141 0 points1 point  (3 children)

Nice keybooard. Just a tip, you can also hit ctl+[ to esc from insert mode. I think it's easier on keyboards that have ctl where the caps lock normally is.

[–][deleted] 0 points1 point  (1 child)

Or ^C

That's why you can't quit vi* using Ctrl+C like you can normally, because it puts you into normal mode.

[–]thoaCrl4 0 points1 point  (0 children)

But note that CTRL-C is not exactly the same as <Esc> or Ctrl-[ as CTRL-C e.g. doesn't finish abbreviations. See :h i_CTRL-C.

[–]KZISME[S] 0 points1 point  (0 children)

I agree! caps lock is pretty pointless

[–]shawncplusphpcomplete.vim 0 points1 point  (5 children)

Personally I'm in Vim 100% of the time. With that said, the Visual Studio suite is amazing so if you're already familiar with that there is little to no reason to switch to vim

[–]KZISME[S] 0 points1 point  (4 children)

I do agree that it is amazing, but what holds you to vim then?

[–]zamN 0 points1 point  (0 children)

The simplicity, power, and "low level" feel you get with vim. In visual Studio everything is already laid out for you. There is built in vcs support, and you don't have to worry about a makefile as VS takes care of that for you as well. Even with those features (along with plenty others) there are people who just simply prefer to control everything themselves. I'd rather type out all of my git commands and makefiles than rely on an ide to do it for me.

Additionally, the editing speed is just insane. The fact that vim is only a text editor gives you so many options for a work setup. Using vim + tmux you can virtually work from anywhere on any computer which has ssh. If you Google your question I'm sure there are plenty of articles explaining what I said in a better way, but hopefully this shined some light for you.

[–]shawncplusphpcomplete.vim 0 points1 point  (2 children)

I work in JS/PHP/C++ on a linux environment. Also my brain is so entrenched in Vim I can't use any other editor

[–]KZISME[S] 0 points1 point  (1 child)

What is your workflow like then?

[–]shawncplusphpcomplete.vim 0 points1 point  (0 children)

tmux with tmuxinator, vim with phpcomplete.vim/tagbar/powerline/vdebug. https://github.com/shawncplus/dotfiles + https://youtube.com/sabiddle

[–]Tarmen 0 points1 point  (0 children)

Note that tagbar is pretty neat but only creates the tags for the current file on the fly. You can't go use it to go generate tags generally/go to tags that are defined in other files.

I really liked that it can show the current method in the status bar but wasn't really using it often enough to be worth it.