Thread: Re: Saving auto wrap, wrap & line number preferences from GUI
Cream is a free, easy-to-use configuration of the Vim text editor
Brought to you by:
digitect
From: Steve H. <dig...@mi...> - 2005-04-18 14:45:13
|
From: BG - Ben Armstrong, Apr 18, 2005 10:28 AM > > I thought auto wrap, wrap & line number preferences could be saved > from the GUI like color themes. Apparently that's not the case, or > I've missed something. Can it be done? I really don't want to have > to teach my users how to hand-edit cream-conf.vim. Everyone has > different preferences for these settings, so I can't just set it > once in our global cream-conf.vim. These are retained, by default in ~/.cream/views/.viminfo. (The value of &viminfo, usually g:cream_user . "views" .) Do you have a conflicting value in a global config or user file? -- Steve Hall [ digitect mindspring com ] Cream... something good to put in your Vim! http://cream.sourceforge.net |
From: BG - B. A. <BAr...@dy...> - 2005-04-18 14:57:28
|
> These are retained, by default in ~/.cream/views/.viminfo. > (The value of &viminfo, usually g:cream_user . "views" .) > > Do you have a conflicting value in a global config or user file? Yes. But what is considered "conflicting"? I would have thought ~/.cream would take precedence over $VIMRUNTIME/cream/cream-user.vim and cream-conf.vim. I need to be able to establish defaults for everyone in these two files, but allow users to override them to suit their tastes. Ben |
From: Steve H. <dig...@mi...> - 2005-04-18 15:45:23
|
From: BG - Ben Armstrong, Apr 18, 2005 10:57 AM > > > These are retained, by default in ~/.cream/views/.viminfo. (The > > value of &viminfo, usually g:cream_user . "views" .) > > > > Do you have a conflicting value in a global config or user file? > > Yes. But what is considered "conflicting"? I would have thought > ~/.cream would take precedence over $VIMRUNTIME/cream/cream-user.vim > and cream-conf.vim. > > I need to be able to establish defaults for everyone in these two > files, but allow users to override them to suit their tastes. Order of load is as follows: 1. $CREAM . "cream-conf.vim" 2. g:cream_user . "cream-conf.vim" (overwrites 1.) 3. $CREAM . "cream-user.vim" (VimEnter autocmd event) 4. g:cream_user . "cream-user.vim" (VimEnter autocmd event) 5. ~/.cream/views/.viminfo 6. $CREAM . "cream-conf.vim" (BufEnter autocmd event) 7. g:cream_user . "cream-conf.vim" (BufEnter autocmd event.) Any setting or function found early will be active unless a later step overwrites it. Also note that 7 will replace the entire behavior found in 6 since the file is structured as a single function whose name will overwrite the previously existing function of the same name. I'd recommend making the global settings as light as possible. Don't set personal preferences unless they are mandated for all editing. (Like tabstop width.) Even then, a personal preference set within a buffer will override anything else since no autocmd event will intervene. The user's cream-conf also takes precedence. Power to the people! :) -- Steve Hall [ digitect mindspring com ] Cream... something good to put in your Vim! http://cream.sourceforge.net |
From: Matt W. <mat...@go...> - 2005-04-20 21:47:58
|
> Order of load is as follows: ... that nice succinct list would be a good item for the FAQ. -- matt wilkie -------------------------------------------- Geographic Information, Information Management and Technology, Yukon Department of Environment 10 Burns Road * Whitehorse, Yukon * Y1A 4Y9 867-667-8133 Tel * 867-393-7003 Fax -------------------------------------------- |
From: BG - B. A. <BAr...@dy...> - 2005-04-18 17:37:17
|
> I'd recommend making the global settings as light as > possible. Don't set personal preferences unless they are > mandated for all editing. > (Like tabstop width.) Even then, a personal preference set > within a buffer will override anything else since no autocmd > event will intervene. The user's cream-conf also takes precedence. Ah, got it.. I had wanted to set an *initial* default for the wrap, auto & line#, not override it each time. So changing these in cream-conf was the wrong thing to do. I have removed these settings and now it works expected (except without the ability to set the initial default for the first time a new user starts the editor, but that's OK because any choice I make for these settings is going to be arbitrary anyway). Ben |
From: Steve H. <dig...@mi...> - 2005-04-19 01:36:01
|
On Mon, 2005-04-18 at 14:37 -0300, BG - Ben Armstrong wrote: > > Ah, got it.. I had wanted to set an *initial* default for the wrap, > auto & line#, not override it each time. So changing these in > cream-conf was the wrong thing to do. I have removed these settings > and now it works expected (except without the ability to set the > initial default for the first time a new user starts the editor, but > that's OK because any choice I make for these settings is going to > be arbitrary anyway). Cream already initializes default values and retains them when they change. It was one of the first features. To avoid this, use: [login@host ~]$vim :)) -- Steve Hall [ digitect mindspring com ] :: Cream... something good to put in your Vim! :: http://cream.sourceforge.net |
From: Steve H. <dig...@mi...> - 2005-04-20 22:04:55
|
From: Matt Wilkie, Apr 20, 2005 5:46 PM > > > Order of load is as follows: ... > > that nice succinct list would be a good item for the FAQ. Great minds think alike...I put it in CVS a day or two ago. :) -- Steve Hall [ digitect mindspring com ] Cream... something good to put in your Vim! http://cream.sourceforge.net |