Yep, that's the problem. ;) They should be styled differently, since they are not entirely equivalent. The use of two colons on the pseudo-elements (and the fact that they need to appear AFTER any pseudo-classes, if they exist) are not handled by Scintilla, so far as I know. Although, the two colons thing wasn't even suggested until CSS3.
But like I said, I wouldn't mind working on the Scintilla side of this one if you guys want to handle Geany's keywords. It just needs pseudo-classes and pseudo-elements separated, and whatever list of missing keywords added for the styling. If you can do all of that in the tag manager, great! I'm not familiar with it.
Jay
Enrico Tröger wrote:
On Thu, 04 Sep 2008 11:40:36 -0700, Jason Oster parasytic@gmail.com wrote:
As the reporter of the bug mentioned, no complaints from me! Although, and this is only slightly related, I haven't noticed any way to identify pseudo-classes and pseudo-elements as separate entities. An example from some CSS I have been using recently:
.sort_asc:hover::after { content: ' \25BE'; /* Black Down-Arrow */ }
Ideally, the :hover pseudo-class and ::after pseudo-element should be lexed and styled differently by Scintilla. If this is a Scintilla issue, (needs double-checking) I would be glad to pick this up and work on it.
After having a short look at it, I'd say the CSS lexer of Scintilla doesn't support pseudo-elements. It seems the "after" is styled the same as the pseudo-class before. But I don't know CSS at all not sure about all this.
Regards, Enrico
Geany mailing list Geany@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany