On Sun, 5 Jul 2009 16:47:23 +0200 Enrico Tröger <[email protected]> wrote: > It *should* that but it doesn't do yet :(. > Have a look at src/templates.c make_comment_block() and remove the > case for Haxe.
OK, I see. > I guess blackdog preferred the // style when we added > the filetype. Not sure what's best as the default. Not sure either. I thought multiline comments with /**/ were more common ... > We should rewrite this function so that it uses the > comment_open/comment_close settings Definitely. Then you can choose yourself. > but there is still the lack for > the line_prefix information. You mean tabs or spaces at the beginning of the lines? That would have been my next request :-) > We could either add line_prefix to the > filetype definition files or magically guess it. But I don't like both > ways that much. Not sure what to do best. I'd prefer magically. There might be different line_prefixes depending on the place of the comment. Another thing that would be nice to have is filling function name and params automagically function declarations :-) I think I saw that once in Eclipse ... -- Mockey _______________________________________________ Geany-devel mailing list [email protected] http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
