From: BG - Ben Armstrong <BA<rmstrong@dy...> - 2004-11-02 19:47:31
I tripped on this when trying to fix the "filetype plugin on" setting in
cream-conf.vim so that it will be in effect when the filetype is first
determined (I hope). I talked to Christoph Haas about this file and he
agreed that in the next version he's putting it under /etc so it can be
edited on a Debian system. The problem is, you can't have a system-wide
version of cream-conf.vim when g:cream-user exists!
call Cream_source(g:cream_user . "cream-conf.vim")
call Cream_source($CREAM . "cream-conf.vim")
I think it would be better to do this exactly the same way as
cream-user.vim in cream-lib.vim, that is by loading the system-wide
version first, and then allowing the user to put overrides in their
" load system cream-user
call Cream_source($CREAM . "cream-user.vim")
" load $HOME's cream-user
call Cream_source(g:cream_user . "cream-user.vim")
From: Steve Hall <digitect@mi...> - 2004-11-03 02:34:24
On Tue, 2004-11-02 at 15:33, BG - Ben Armstrong wrote:
> Attached are my patches to fix both loading a system-wide
> cream-conf.vim and to set "filetype plugin on".
These look good, I've pushed both to CVS. Let's keep an eye on the
"plugin" add, I want to be sure there wasn't some ancient reason
this wasn't so.
Steve Hall [ digitect mindspring com ]
Cream... something good to put in your Vim!
From: BG - Ben Armstrong <BA<rmstrong@dy...> - 2004-11-02 20:39:13
Oh, I suppose I ought to mention I tested both patches. I verified
scriptnames now includes the system-wide cream-conf.vim, and verified
that when I edit a file whose filetype can be determined from the file
extension passed on the command-line, the associated ftplugin/ file is
now loaded (perl.vim in my test).
Get latest updates about Open Source Projects, Conferences and News.