Coming Home to Vim
stevelosh.com
Coming Home to Vim
1–10 of 125 posts
Re: Coming Home to Vim
#2One of the things I love about Vim is that every time I read though a post like this or look at someone's .vimrc I learn something new about what it can do or get another insight about how its features can make my life easier.
My (semi-commented) .vimrc is on GitHub if anyone wants another example: http://github.com/samdk/vimconf/blob/master/dotvimrc
I've also found StackOverflow's list of most-voted questions tagged vim to be a very useful source of little tidbits: http://stackoverflow.com/questions/tagged/vim?sort=votes&...
And there've been several HN .vimrc posts that I also found very useful. This is one of the best: http://news.ycombinator.com/item?id=856051
This is another excellently commented and extensive .vimrc that (I think) is mentioned in one of the above links, but deserves its own specific mention here: http://www.vi-improved.org/vimrc.php
And this is another I found completely by accident a while ago that includes some excellent examples of vimscript macros: http://fingelrest.silent-blade.org/uploads/Main/vimrc.html
Re: Coming Home to Vim
#3One of the things I love about Vim is that every time I read though a post like this or look at someone's .vimrc I learn something new about what it can do or get another insight about how its features can make my life easier. My (semi-commented) .vimrc is on GitHub if anyone wants another example: http://github.com/samdk/vimconf/blob/master/dotvimrc I've also found StackOverflow's list of most-voted questions tagged…
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!
Re: Coming Home to Vim
#4This is an excellent vim tutorial. Unlike others I've read, it makes me want to be vim power user by clearly spelling out the benefits of various tricks and commands.
Re: Coming Home to Vim
#5One of the things I love about Vim is that every time I read though a post like this or look at someone's .vimrc I learn something new about what it can do or get another insight about how its features can make my life easier. My (semi-commented) .vimrc is on GitHub if anyone wants another example: http://github.com/samdk/vimconf/blob/master/dotvimrc I've also found StackOverflow's list of most-voted questions tagged…
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!
syntax on
filetype on
filetype plugin on
filetype indent on
You do not want "filetype off"
Also, check out snipMate as it gives you easy to use TextMate type snippets.
In Vim:
:h filetype
Re: Coming Home to Vim
#6One of the things I love about Vim is that every time I read though a post like this or look at someone's .vimrc I learn something new about what it can do or get another insight about how its features can make my life easier. My (semi-commented) .vimrc is on GitHub if anyone wants another example: http://github.com/samdk/vimconf/blob/master/dotvimrc I've also found StackOverflow's list of most-voted questions tagged…
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 :)
Re: Coming Home to Vim
#7Earlier 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 :)
HN has a speed-limiter in place to prevent flamefests. If you find yourself in the position of not being able to reply due to the previous comment being made too recently, you can click the "link" link and reply on the resulting page.
Re: Coming Home to Vim
#8Entirely agree on the aesthetics, one of the things holding me back from switching is that I love vibrant ink in textmate. I just can't seem to find a theme that is quite as bright (vividchalk was pretty close). Any suggestions?
Re: Coming Home to Vim
#9Earlier 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 :)
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.)
Re: Coming Home to Vim
#10Earlier 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 :)
HN has a speed-limiter in place to prevent flamefests. If you find yourself in the position of not being able to reply due to the previous comment being made too recently, you can click the "link" link and reply on the resulting page.
Ah, neat, I didn't know that. Thanks!