Folding is different depending on whether the line after a sub is properly indented, whether there's a blank line, or whether it's improperly indented.
(screenshots from SciTE 5.5.5 with fold.symbols=3 to make folding more obvious)
Properly Indented (folds correctly):
Sub NameHere()
Set HelpBookP = 5
Set HelpBookQ = 5
if a=b then
Set HelpBookQ = 9
end if
Range("K1:K5")
End Sub
Blank line between (fold symbols not showing, but does fold if you click the missing boxed-+):
Sub NameHere()
Set HelpBookP = 5
Set HelpBookQ = 5
if a=b then
Set HelpBookQ = 9
end if
Range("K1:K5")
End Sub
=> 
Bad indentation (start-of-fold moves to the unindented Set instead of starting at the Sub where it belongs)
Sub NameHere()
Set HelpBookP = 5
Set HelpBookQ = 5
if a=b then
Set HelpBookQ = 9
end if
Range("K1:K5")
End Sub
Visual Basic does not apply meaning to leading/trailing whitespace (unlike Python), so the way it's folded should not be dependent on whitespace. But this experiment strongly implies that LexVB is considering whitespace when deciding on where/how to fold.
(this bug report comes from this Notepad++ Community discussion)
Folding is different depending on whether the line after a sub is properly indented, whether there's a blank line, or whether it's improperly indented.
(screenshots from SciTE 5.5.5 with
fold.symbols=3to make folding more obvious)Properly Indented (folds correctly):
Blank line between (fold symbols not showing, but does fold if you click the missing boxed-
+):Bad indentation (start-of-fold moves to the unindented
Setinstead of starting at theSubwhere it belongs)Visual Basic does not apply meaning to leading/trailing whitespace (unlike Python), so the way it's folded should not be dependent on whitespace. But this experiment strongly implies that LexVB is considering whitespace when deciding on where/how to fold.
(this bug report comes from this Notepad++ Community discussion)