21–30 of 125 posts
I know, I know... But when you were newly in "love" with textmate I'm sure if I said you need to switch to vim you'd say no way. Skip vim and go right to the best there is, Emacs.
Don't lose another four years before blogging about how you finally switched to emacs from vim and bite the bullet now. Emacs is to vim as vim is to textmate IF you are a hard core software developer. Vim is best for sysadmins, simple, quick non-complex editing. I know, I know... But when you were newly in "love" with textmate I'm sure if I said you need to switch to vim you'd say no way. Skip vim and go right to the…
If you're a vim user on a mac, try ViKing. It lets you use vi-like navigation throughout OSX. It's still in beta and I would love some feedback. http://vikingapp.com @vikingapp
So far there's a Vim plugin or mod for: Emacs, Firefox, Chrome/Chromium, Opera, Eclipse, and now even OS X. What others are there?
If you're a vim user on a mac, try ViKing. It lets you use vi-like navigation throughout OSX. It's still in beta and I would love some feedback. http://vikingapp.com @vikingapp
The main reason I don't use ViKing is that the hotkeys all end up shadowing something useful or being very awkward.
If I choose Ctrl I shadow Ctrl+H.
If I choose Cmd I shadow lots of stuff, like Cmd+L in a browser.
If I choose Alt (ViKing doesn't do that right now, but I'll assume it could be added) it's quite awkward (unless I remap capslock to Alt, but I've already got capslock-as-Ctrl in my fingers).
I don't have a solution to this, but would desperately love to find one.
Earlier quoted context omitted.
Exactly. Case in point: I just found out about ending the backupdir with two slashes to include the full path in the filename by reading your .vimrc. Thanks!
Replying to myself because I can't seem to reply to sigzero: Yeah, I definitely need to get around to reading :h filetype. I mentioned Snipmate in the article, so I know about it :)
which shares the exact same title.
Interesting article. I found it a bit strange that he didn't link to or reference this: http://weblog.jamisbuck.org/2008/10/10/coming-home-to-vim which shares the exact same title.
I'll add a link to it now.
Don't lose another four years before blogging about how you finally switched to emacs from vim and bite the bullet now. Emacs is to vim as vim is to textmate IF you are a hard core software developer. Vim is best for sysadmins, simple, quick non-complex editing. I know, I know... But when you were newly in "love" with textmate I'm sure if I said you need to switch to vim you'd say no way. Skip vim and go right to the…
Seriously, can we not start yet another Emacs vs. vi argument? Neither is perfect, they both have ardent fans, pick either, get really proficient with it, and don't look back.
(Emacs user who loves Emacs's extensibility and multi-buffer design but prefers vi's modal keyboard ui. And yes, I know about viper, etc.)
For a free, cross-platform (and excellent) alternative to PeepOpen, try Command-T I used to use FuzzyFinder_TextMate, but that's stopped development, and the creator recommends you use Command-T instead. https://wincent.com/products/command-t
Earlier quoted context omitted.
Replying to myself because I can't seem to reply to sigzero: Yeah, I definitely need to get around to reading :h filetype. I mentioned Snipmate in the article, so I know about it :)
This is not vim-related, but the reason you couldn't reply is that HN doesn't let you reply to a comment until after a certain amount of time has passed. This amount of time depends on how deep the comment is in the tree. (I believe the restriction is there to help prevent excessively deep comment trees that are just people arguing back and forth.)