Re: Problems switching from 0.15
Cream is a free, easy-to-use configuration of the Vim text editor
Brought to you by:
digitect
From: Xavier N. <xav...@fr...> - 2002-11-30 22:05:10
|
On Sat, 30 Nov 2002 13:02:47 -0500 Steve Hall <dig...@mi...> wrote: > From: "Xavier Nodet" <xav...@fr...> >> >> I recently tried to switch from 0.15 to 0.17, using Vim 6.1 on >> Windows XP SP1. I noticed several problems. > I'm assuming this is gVim, based on your font selections. Yes, of course. >> [Handling of backspace] > Very good find. I believe the problem is in the cream-keys.vim. > Replace the line (around 115): > vmap <silent> <BS> :call Cream_delete_v()<CR> > with this one: > vmap <silent> <BS> :<C-u>call Cream_delete_v()<CR> > and see if that improves things. Yes! This is perfect, now... Thanks! >> In fact, it seems that when some text is selected, some keys have >> a special effect (something that looks like 'extend the selection up >> to the next occurrence of the pressed key'). > (The status line has a single letter indicator of mode, check and > see if it says "V" rather than "S".) When I press shift-right, shift-left, ctrl-shift-right, or ctrl-shift-left, the display changes from I to V, and the behavior is /not/ correct. When I press shift-up or shift-down, the status bar has an 'S', and the behavior is correct. If I first use shift-up or shift-down to enter select mode, then all the shift-arrow keys work correctly. >> Last problem is that with 0.17 (0.16 is correct here), the font used >> by Vim is not changed when I use >> >> set guifont=Lucida_Console:h8 >> >> in my _vimrc file. I still get the default font. With 0.15, the font >> is correctly changed. > I believe this is happening because Cream uses autocommands to > initialize many settings after it starts. Your setting in vimrc is > being over-ridden by Cream's stored setting. Try using the > Settings.Preferences.Font to control your font. (I see some other > items in your vimrc that may also be conflicting: expandtab, lines, > columns, wrap, syntax, filetype, hlsearch, shiftwidth, tabstop, etc.) You mean that, by using autocommands, Cream resets its settings e.g. maybe when reading a file, and not only at startup. I understand... I removed most of those settings, and things seem to be correct. I'll try to use Cream as it was designed, in the future ;)... Thanks. -- Xavier Nodet "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." - Benjamin Franklin, 1759. |