[ 
https://issues.apache.org/jira/browse/GROOVY-8842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Daniel Sun updated GROOVY-8842:
-------------------------------
    Description: 
Implement a source code highlighter based on Parrot's lexer, the new 
highlighter should be smarter. e.g.

It can show different colors in GString `"abc${'123' + 123}def${a + b}"`

P.S. Currently the new highlighter will render all source code for each 
editing, so it is NOT recommended to be enable for large source code for the 
time being. 
       The new highlighter is NOT enabled by default.  Check the checkbox 
"Enable smart highlighter" in "View" menu to enable the new highlighter




  was:
Implement a source code highlighter based on Parrot's lexer, the new 
highlighter should be smarter. e.g.

It can show different colors in GString `"abc${'123' + 123}def${a + b}"`

P.S. Currently the new highlighter will render all source code for each 
editing, so it is NOT recommended to be enable for large source code for the 
time being(The new highlighter is NOT enabled by default)





> Implement a smart highlighter for groovy console editor
> -------------------------------------------------------
>
>                 Key: GROOVY-8842
>                 URL: https://issues.apache.org/jira/browse/GROOVY-8842
>             Project: Groovy
>          Issue Type: New Feature
>            Reporter: Daniel Sun
>            Assignee: Daniel Sun
>            Priority: Major
>             Fix For: 3.0.0-alpha-4
>
>
> Implement a source code highlighter based on Parrot's lexer, the new 
> highlighter should be smarter. e.g.
> It can show different colors in GString `"abc${'123' + 123}def${a + b}"`
> P.S. Currently the new highlighter will render all source code for each 
> editing, so it is NOT recommended to be enable for large source code for the 
> time being. 
>        The new highlighter is NOT enabled by default.  Check the checkbox 
> "Enable smart highlighter" in "View" menu to enable the new highlighter



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to