Ben Fritz wrote:
> On Feb 4, 5:47=A0pm, Matt Wozniski <[email protected]> wrote:
> >
> > It seems to work fine in my testing. =A0Can you give me an example of a
> > place where it fails?
>
> Hmm, I had thought I tried this before, but I see that on 7.2.348 it
> works fine.
>
> However, with the latest 7.2.356 patch, it does not work.
>
> gvim -N -u NONE -i NONE
> :set rtp-=~/vimfiles
> :set rtp-=~/vimfiles/after
> :filetype plugin indent on
> :syntax on
> :e test.c
> :set fdm=syntax
> :au InsertEnter * let b:oldfdm = &l:fdm | setlocal fdm=manual
> :au InsertLeave * let &l:fdm = b:oldfdm
>
> Now I go into a code block, open the fold, enter insert mode, type
> some text, exit insert mode, and the fold closes up again.
>
> Before I installed the new version, I was able to manually set the
> foldmethod back and forth without affecting the fold level, I was
> unable to do this with the latest version, and the autocmd method is
> as above.
Lech Lorens already mentioned that this patch might reset more info than
actually needed. But it may be very difficult to only reset those folds
that differ from what was already there. It probably require a new flag
"reset level when this fold changes".
--
Some of the well know MS-Windows errors:
ESLEEP Operator fell asleep
ENOERR No error yet
EDOLLAR OS too expensive
EWINDOWS MS-Windows loaded, system in danger
/// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ download, build and distribute -- http://www.A-A-P.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
--
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
