On Dienstag, 5. Oktober 2010, Igor Mitrenko wrote:
> Oh, sorry.
> I mean comment/uncomment functions in eric. They works with python code,
> but in other cases (such as html, js, css) they don't. Actually, they
> work, but make wrong things - just add or remove python-style comment
> symbol '#', when it's expected to add content-specific comments like "<!--
> -->" pair in html, "//" or "/* */" in js source, and "/* */" in css.
> Finally, it's worth to mention django template comments "{# <commented
> text> #}" and "{% comment %}{% endcomment %}". So, it would be great if
> you implement such functions. I would implement them by myself, but I
> don't understand clearly internal architecture of eric.Ok, I got the idea. Actually, eric already has three types of comments. They are all defined in the various lexer classes and are made available via the Edit menu. However, I admit, that some comments might not be defined correctly. I would be very happy to receive a patch. The Django lexer ist part of the Django plug-in. Regards, Detlev > > 2010/10/5 Detlev Offenbach <[email protected]> > > > On Dienstag, 5. Oktober 2010, Igor Mitrenko wrote: > > > Hello. > > > It would be grate if comment/uncomment hotkey work uniformly with > > > > different > > > > > type of content. > > > It is very useful, but there are some pitfalls - when .css or .js file > > > > can > > > > > contain only appropriate content type, in html file could be mixed each > > > > of > > > > > them - html itself, js code and css code. > > > What do you think about that? > > > > I don't quite understand what you mean. Can you be a bit more explicit. > > > > Detlev > > -- > > Detlev Offenbach > > [email protected] -- Detlev Offenbach [email protected] _______________________________________________ Eric mailing list [email protected] http://www.riverbankcomputing.com/mailman/listinfo/eric
