Re: Using a custom _vimrc with Cream
Cream is a free, easy-to-use configuration of the Vim text editor
Brought to you by:
digitect
From: William M. <wi...@kn...> - 2003-04-11 14:41:46
|
> Your reasoning baffles me. Why should it be a project requirement that > core components be incapacitated while third-party scripts be > perfectly functioning? That has not been my intention. I am simply trying to find a way for my customizations to live with Cream in a way that is logical for a long-time Vim user. However, I'm finally starting to see your point. By allowing personal customizations to overlay Cream's settings, the user ends up with a non-standard environment. This may be what is desired but may also cause confusion for new users. I agree that the system should just work for new users and be configurable for existing users. Part of my problem is that it's taken me awhile to wrap my head around the idea that Cream demands a very specific environment and does not get along easily with personalized settings unless the user takes the appropriate measures. The other part has been that I've also been avoiding the need to learn more about Vim so that I can keep my existing Vim settings and still use Cream. > > So, this is strictly a matter of making Cream usable for existing > > Vim users. > > I assume that existing Vim users know how to make their scripts work > with Cream if that is desired. Primarily, we want a user to be able to > install and use Cream as easily as possible. Well this whole thread has been about an existing Vim user learning how to make my scripts work with Cream. That is *not* an easy task without some level of understanding of both Cream and Vim that has taken me several days and many hours to come around to (despite having read the documentation on your website which is primarily focused towards new users). Based on the lack of feedback from others in the mailing list, I'm guessing that I'm the only one here who is suffering from a Vim mental model or else noone here has ever used Vim without Cream. To help other habituated Vim users and try to solidify my understanding, I have put together a document which describes setting up Cream with a pre-existing Vim setup, ways to overcome some of the obstacles that I encountered and the realization I've had that Cream needs much greater control of my Vim environment than I ever expected. Some of the items in the document should be added to the installation notes to save others the headaches I've encountered and to save you from having to go through another conversation like this one. > > I can keep commenting out that VimEnter autocommand in > > cream-autocmd.vim each time a new release comes out but would like > > to see a long-term solution that addresses the above problems in a > > way that is nice to those of us who have taken the time to build-up > > an arsenal of custom key mappings. > > Again, we have suggested cream-user. We have also added a ToDo item to > have Cream explore some alternative possible locations for this file. > Didn't get any feedback from you on this. I think your suggestion of having a custom $HOME/.cream/cream-user.vim makes sense. This would work fine for Win* users if they set $HOME in their environment as I have under WinNT (in Win9x there are a few more steps as I recall). Now, if that file was present in the $HOME directory, would the $VIM/cream/cream-user.vim file also load, if present? Or would it only load one of the two as Vim does with vimrc? I vote for the latter. > I mostly have personal templates: Thanks for the examples of your cream-user.vim. I'm getting some strange behavior with the Alt+Space key mapping which may be due to my half-baked version of cream-keys-normal.vim. The template substitution works but it removes the next character which, if at the end of the line as is often the case when doing completions, causes the sentence below to jump up. Ever seen this behavior? Regards, William -- Knowmad Services Inc. http://www.knowmad.com |