Felix Kater wrote:
if you have foliding activated and a C source code with something like
line 1:
line 2: #if 1
[folded]
line 9: ...
and then start to type /* in line 1 to enter a comment: Then the fold
in line 2 is uncollapsed, also all subfolds.
Obviously this happens since the scopus of the newly inserted comment
start ("/*") is not terminated by "*/" and so reaches into the folded
section. However, this should not cause the next fold to uncollaps.
This is quite confusing from the user's viewpoint.
Basically, that's life... ;) It's not clear that there *are* any
other choices for the lexer - Visual Studio does the same thing.
However, this isn't to say that there are not other possibilities...
1) quite a while ago, I adopted a style of entering [/* */] comments
by putting in the text and the */ first, then adding the /* later
2) SciTE has the Ctrl-Shift-Q operation: enter the text of a comment,
select it, and then do Ctrl-Shift-Q - the text get surrounded with
spaces, and then bracketed by /* and */!
Note that the above is for C/C++ - this is actually controlled by
per-lexer properties settings. Search for "comment.block" in
SciTEDoc.html.
Robert Roessler
[EMAIL PROTECTED]
http://www.rftp.com
_______________________________________________
Scite-interest mailing list
[email protected]
http://mailman.lyra.org/mailman/listinfo/scite-interest
