Hi Gary! On Di, 12 Okt 2010, Gary Johnson wrote:
> On 2010-10-12, Gary Johnson wrote: > > On 2010-10-12, Bee wrote: > > > Benjamin R. Haskell wrote: > > > > On Tue, 12 Oct 2010, Bee wrote: > > > > > > > > > What keeps clearing my spellcapcheck? > > > > > > > > What does this return? > > > > > > > > :verbose set spellcapcheck? > > > > > > In the first buffer opened it returns: > > > spellcapcheck=[.?!]\_[\])'"^I ]\+ > > > > > > When switching to another buffer: > > > spellcapcheck= > > > > > > What would cause it to be cleared on buffer switch? > > > Both files are the same type xxx.txt > > > Each opened by itself spellcapcheck is ok! > > > > Looks like a bug to me. I can replicate the problem like this. > > > > $ vim -u NONE > > :verbose set spellcapcheck? > > spellcapcheck=[.?!]\_[\])'"^I ]\+ > > :new > > :verbose set spellcapcheck? > > spellcapcheck= > > :wincmd w > > :verbose set spellcapcheck? > > spellcapcheck= > > > > Note that after switching to the new buffer, the option was cleared > > even in the original buffer. > > Sorry--forgot to report the version info. I tested that using > vim-7.3 on Cygwin on Windows XP and vim-7.3.3 on RHEL4. > > Also, I retested with vim in 'nocompatible' mode with slightly > different results in that 'spellcapcheck' retained its default value > in the original buffer. > > $ vim -N -u NONE > :verbose set spellcapcheck? > spellcapcheck=[.?!]\_[\])'"^I ]\+ > :new > :verbose set spellcapcheck? > spellcapcheck= > :wincmd w > :verbose set spellcapcheck? > spellcapcheck=[.?!]\_[\])'"^I ]\+ But that is ok, isn't it? spellcapcheck isn't supposed to work in compatible mode and I don't see an error for non-compatible mode. regards, Christian -- You received this message from the "vim_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
