On Thu, 11 Feb 2016, [email protected] wrote:
Date: Thu, 11 Feb 2016 14:34:20
From: [email protected]
Reply-To: [email protected]
To: [email protected]
Subject: Re: another folding bug recently introduced?
On Thu, 11 Feb 2016, Christian Brabandt wrote:
Date: Thu, 11 Feb 2016 00:09:07
From: Christian Brabandt <[email protected]>
Reply-To: [email protected]
To: [email protected]
Subject: Re: another folding bug recently introduced?
Am 2016-02-11 09:04, schrieb [email protected]:
for the following modeline, folds do not work. if i change filetype
to vim, folds do work as expected. for me,the last known working
version was patchlevel 1257. patchlevels 1297-1301 also do not work
as expected. this seems to be platform independent: i've checked osx
10.11.3, mint 17.3, windows 10, ubu 15.10.
the modeline i typically use is:
#-vim-modeline
vim:fenc=utf-8:foldmarker={{{{,}}}}:foldmethod=marker:ft=zsh:nocrb:noscb:nowrap:sw=4:syn=on:ts=4:tw=0:wm=0
i admit to git-ignorance. if someone would be kind enough to give me
a quick command line to pull a specific patchlevel, i volunteer to
find first occurrence of this regression.
can you show a sample file, that isn't workin anymore?
thank you for the reply, christian.
file 1 (3 lines) does fold:
#-vim-modeline vim:foldmarker={{{{,}}}}:foldmethod=marker:ft=vim:syn=on
# info {{{{1
# info }}}}1
file 2 (3 lines) does not fold:
#-vim-modeline vim:foldmarker={{{{,}}}}:foldmethod=marker:ft=zsh:syn=on
# info {{{{1
# info }}}}1
these results were obtained from osx 10.11.3, patchlevel 1301.
both files fold correctly on osx 10.11.3, patchlevel 1257.
i used an identical vim operating environment (plugins, .vimrc, etc) on
each system.
the problem is that somewhere in the initialization routines, foldmethod
is now being forced to syntax. if i manually reset the foldmethod to
marker, all is well. it appears that the modeline is ignored.
