There are numerous examples where "comment selection" could be handy, IMHO.
Have a look at the Geanyembrace plugin, its purpose is to "embrace" the selection by inserting specified text before/after it. IIUC its original purpose is HTML marking up. Not sure if it is already configured for comments. Its not documented on the website but has a readme.html.
Fair enough. But I'd prefer context-sensitive commenting before that :)
i.e. when you have a script that is a mix of script types (HTML, CSS, PHP or VBScript, JavaScript) it would be nice if comments worked on the appropriate language for the selected block.
Right now, if you have an ASP and the mode is HTML, any CSS, JavaScript, or VBScript you try to comment out gets <!-- and -->
And similarly, HEREDOC HTML you have in PHP gets /* and */
I don't know how to solve that one, and have yet to peek at the codez for it. But I reckon it is a bigger problem.
Only slightly smaller problem than world peace :-)
There is nothing in Geany that considers the possibility of embedded languages, Geany is based on the paradigm of the filetype, ie one type for the whole file.
The Scintilla HTML lexer does recognise embedded scripts JS, PHP, Python etc, not sure about CSS I didn't check. But there is no way of passing that information back to Geany so it could possibly change the filetype for different segments of the file.
So first you have to find a hack for passing back the language segments from Scintilla or you have to provide them with a patch to include an official way of doing that (or be very persuasive to get them to do it for you).
Then you can change Geany's central paradigm to allow multiple filetypes per file.
Patches welcome :-).
Cheers Lex
-- Ross McKay, Toronto, NSW Australia "Nobody ever rioted for austerity" - George Monbiot _______________________________________________ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel