Le 20/03/2011 00:09, Lex Trotman a écrit :
Agreed. But supporting both single and multiline comments as a filetype setting seems still a good idea.
I think it should go near the top of the to-do list. We have been talking about the technical reasons for using block or line comments, but there is also the local style reasons. Many places *require* that fileheaders and function descriptions be block comments. That means you can't insert nestable comments because there is only one setting.
Done in r5609, I added new filetype setting comment_single, and use it in priority for ^E-style commands, and comment_open/close for templates. I also updated all filetypes.* to use this new setting.
Cheers, Colomban