After a few months of vim use, I did part of the vim tutorial using both vim and a click-and-type editor (gedit) and timed myself. Gedit was significantly faster. Can't say I understand you vim fanatics.
Coming Home to Vim
31–40 of 125 posts
Re: Coming Home to Vim
#32Earlier quoted context omitted.
Convert your textmate theme to vim: http://coloration.sickill.net/
Thanks! macvim here I come :) edit: Many of the most popular textmate schemes have already been converted and can be found at http://github.com/squil/vim_colors
Some are even "improved". I love molokai http://winterdom.com/2008/08/molokaiforvim .
Re: Coming Home to Vim
#33I was getting a bit tired of seeing/reading a blog post by a random convert to vim/emacs every week but this one is very good.
Re: Coming Home to Vim
#34Don'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…
...and once your fingers are raw, bloody stumps from typing with three modifier keys held down, then you can write about coming home to vim again! Bonus! 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…
Have you noticed that all of the recent press seems to be for vim? It seems like every month there's a new "I switched to vim!" post, but never a similar emacs version, or even a mention of emacs in the switch article.
Note: I am not attempting to argue emacs vs. vim.
Re: Coming Home to Vim
#35After a few months of vim use, I did part of the vim tutorial using both vim and a click-and-type editor (gedit) and timed myself. Gedit was significantly faster. Can't say I understand you vim fanatics.
If you say why Gedit was faster perhaps us vim fanatics can help you understand us.
Re: Coming Home to Vim
#36Great read. Among other things it made me dig deep into the heart of my Vista machine and find whatever font was making your site (and others) utterly unreadable. The answer is shitty Palatino fonts installed by HP, presumably as part of a printer driver.
So there you go, if Steve's site makes your eyes bleed then go and kill the HP Palatino fonts on your machine.
Re: Coming Home to Vim
#37Great read. Among other things it made me dig deep into the heart of my Vista machine and find whatever font was making your site (and others) utterly unreadable. The answer is shitty Palatino fonts installed by HP, presumably as part of a printer driver. So there you go, if Steve's site makes your eyes bleed then go and kill the HP Palatino fonts on your machine.
Hmm, perhaps I should change the font stack.
Is your shitty HP font named "Palatino" or "Palatino Linotype"?
If it's "Palatino" I'll need to insert a Windows-only font at the front of the list.
If it's "Palatino Linotype" I'll need to insert a Windows-only font as the second element in the list.
Re: Coming Home to Vim
#38If 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 kevincolyar account does nothing but spam HN with links to his application. I am sick of seeing him post spam each time a VIM article hits the homepage.
Re: Coming Home to Vim
#39Earlier quoted context omitted.
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.)
Cool, thanks! It would be helpful if it mentioned that somewhere...
Addendum: ugh, it's not even in the damn FAQ.
Re: Coming Home to Vim
#40Don'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…
...and once your fingers are raw, bloody stumps from typing with three modifier keys held down, then you can write about coming home to vim again! Bonus! 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…
[deleted]