Summary: | [syntax highlighting] Syntax highlighting Based Upon Regexp Pattern | ||
---|---|---|---|
Product: | [Eclipse Project] Platform | Reporter: | Greg Felice <greg.felice> |
Component: | Text | Assignee: | Platform-Text-Inbox <platform-text-inbox> |
Status: | ASSIGNED --- | QA Contact: | |
Severity: | enhancement | ||
Priority: | P3 | CC: | antoine, daniel_megert, flyguy, remy.suen, robert.elves, samuel, thatnitind |
Version: | 3.0 | Keywords: | helpwanted |
Target Milestone: | --- | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: |
Description
Greg Felice
2003-09-04 12:58:52 EDT
To me this request sounds like a syntax coloring feature and not code formatting. Do you want to format the code or just display it in a different way? Waiting for more input. Hello, I think my last comments got lost by the system. Sorry. I was thinking that this feature, as you mentioned, does not really involve formatting as in indentation, but onyl font style (color, italic, bold). The feature would allow you to define a regexp to match against (e.g. m/log.debug/), and the font style to be applied to that match. Again, the rationale for for this is greying out and italicizing huge volumes of debug code that have nothing to do with the logic of a method. Thanks Greg Felice More details on this: The typical regexp to be used in this situation would be m/log.debug*;/g or something like that, where I'm matching on log.debug and all chars up to the terminating semicolon. The regexp/font capability would then display the matched line in grey italics, or whatever. Thanks Greg Felice Changed to reopened. Adapted summary. *** Bug 30531 has been marked as a duplicate of this bug. *** *** Bug 112094 has been marked as a duplicate of this bug. *** *** Bug 204828 has been marked as a duplicate of this bug. *** This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. |