Comments on: recursing vimrc http://morgajel.net/2006/06/21/134/ Stemming the flow of evincible Ignorance. We must try to understand for the sake of understanding. Thu, 21 Aug 2008 23:17:41 +0000 http://wordpress.org/?v=2.6.1 By: Jesse Morgan http://morgajel.net/2006/06/21/134/#comment-1229 Jesse Morgan Fri, 30 Jun 2006 17:43:03 +0000 http://morgajel.net/2006/06/21/134/#comment-1229 forgot to mention- I did end up going with a new filename- .pvimrc I'd like to learn how to do it eventually, but for right now I'm not too concerned. forgot to mention- I did end up going with a new filename- .pvimrc

I’d like to learn how to do it eventually, but for right now I’m not too concerned.

]]> By: Marc http://morgajel.net/2006/06/21/134/#comment-1103 Marc Thu, 22 Jun 2006 00:51:23 +0000 http://morgajel.net/2006/06/21/134/#comment-1103 I like dendrite's suggestion - no reason why they need to be called .vimrc - in fact it might be more confusing. I like dendrite’s suggestion - no reason why they need to be called .vimrc - in fact it might be more confusing.

]]> By: dendrite http://morgajel.net/2006/06/21/134/#comment-1102 dendrite Wed, 21 Jun 2006 22:44:12 +0000 http://morgajel.net/2006/06/21/134/#comment-1102 One way to avoid the recursion issue is to use .pwdvimrc (Or something like that) for the directory specific vim runtime configs. E.g., if filereadable("./.pwdvimrc") ... Note that I just made up the name .pwdvimrc. Could be .AnythingNotMagicallyReadWhenVimLoads One way to avoid the recursion issue is to use .pwdvimrc (Or something like that) for the directory specific vim runtime configs. E.g., if filereadable(”./.pwdvimrc”) … Note that I just made up the name .pwdvimrc. Could be .AnythingNotMagicallyReadWhenVimLoads

]]>