One thing I've missed to report for a while now...
With 0.20, the user folding marks doesn't work anymore. For C/C++, I've changed all my code to use "//{{{" and "//}}}" a while ago. Now, these marks can't be used for folding.
Is it possible to enable folding of these marks again?
Regards
Le 05/04/2011 10:57, Joerg Desch a écrit :
One thing I've missed to report for a while now...
With 0.20, the user folding marks doesn't work anymore. For C/C++, I've changed all my code to use "//{{{" and "//}}}" a while ago. Now, these marks can't be used for folding.
Is it possible to enable folding of these marks again?
Yes. Just set the lexer property fold.cpp.comment.explicit to 1 (see the manual [1] for the details).
Cheers, Colomban
[1] http://www.geany.org/manual/current/index.html#lexer-properties-section
On Tue, 05 Apr 2011 14:13:40 +0200 Colomban Wendling lists.ban@herbesfolles.org wrote:
fold.cpp.comment.explicit
That fixes my problem. Thanks.
By the way...
Does this mean the geany defaults has changed? In my case, I haven't had a local filetypes.c yet.
On Tue, 5 Apr 2011 14:34:44 +0200 Joerg Desch jd.vvd@web.de wrote:
fold.cpp.comment.explicit
That fixes my problem. Thanks.
By the way...
Does this mean the geany defaults has changed? In my case, I haven't had a local filetypes.c yet.
Yes. Commenting a brace and getting a new fold point can be confusing, so it's off by default.
Regards, Nick
Le 05/04/2011 14:43, Nick Treleaven a écrit :
On Tue, 5 Apr 2011 14:34:44 +0200 Joerg Desch jd.vvd@web.de wrote:
fold.cpp.comment.explicit
That fixes my problem. Thanks.
By the way...
Does this mean the geany defaults has changed? In my case, I haven't had a local filetypes.c yet.
Yes. Commenting a brace and getting a new fold point can be confusing, so it's off by default.
BTW Nick, wouldn't it be better to move the property default to the filetypes.* rather than in the code? It'd remove a hard-coded default and would probably be easier for people to find it out.
What do you think?
Cheers, Colomban
On 04/05/11 05:49, Colomban Wendling wrote:
Le 05/04/2011 14:43, Nick Treleaven a écrit :
On Tue, 5 Apr 2011 14:34:44 +0200 Joerg Deschjd.vvd@web.de wrote:
fold.cpp.comment.explicit
That fixes my problem. Thanks.
By the way...
Does this mean the geany defaults has changed? In my case, I haven't had a local filetypes.c yet.
Yes. Commenting a brace and getting a new fold point can be confusing, so it's off by default.
BTW Nick, wouldn't it be better to move the property default to the filetypes.* rather than in the code? It'd remove a hard-coded default and would probably be easier for people to find it out.
What do you think?
+1
Also new explicit fold start and end strings too (maybe commented out or with a less confusing default?).
Cheers, Matthew Brush