Details
-
Type:
Bug
-
Status:
Resolved
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: 1.5.6
-
Fix Version/s: 2.0.2Release
-
Component/s: Inferencing Engine
-
Labels:None
-
Environment:Eclipse 3.3.2 on Windows Xp pro SP2
-
Number of attachments :
Description
I could not find this reported elsewhere. Here is a regex:
String regExSqlCreate = /create table [a-z".]*($
{table}[\r\n\d\w\s_,();]+)revoke all on [a-z\".]*${table}from "public"/
As the attached picture shows 'create table [a-z' shows in black, and 'public' shows in keyword color.
Issue Links
- is duplicated by
-
GRECLIPSE-251
Slashy strings don't like escaped slash at the end
-
-
GRECLIPSE-248
When using the divide operator '/' every that follows in that line is displayed as String coloring
-
Activity
James E. Ervin
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Assignee | Edward Povazan [ emp ] | Thorsten Kamann [ thorque ] |
Andrew Eisenberg
made changes -
| Assignee | Thorsten Kamann [ thorque ] | Andrew Eisenberg [ werdna ] |
Andrew Eisenberg
made changes -
| Link |
This issue is duplicated by |
Andrew Eisenberg
made changes -
| Link |
This issue is duplicated by |
Andrew Eisenberg
made changes -
| Assignee | Andrew Eisenberg [ werdna ] |
Andrew Eisenberg
made changes -
| Original Estimate | 0 minutes [ 0 ] | |
| Remaining Estimate | 0 minutes [ 0 ] | |
| Assignee | Andrew Eisenberg [ werdna ] |
Andrew Eisenberg
made changes -
| Status | Open [ 1 ] | In Progress [ 3 ] |
Andrew Eisenberg
made changes -
| Status | In Progress [ 3 ] | Resolved [ 5 ] |
| Resolution | Fixed [ 1 ] |
Andrew Eisenberg
made changes -
| Fix Version/s | 2.0.2Release [ 16150 ] |
Andrew Eisenberg
made changes -
| Component/s | Inferencing Engine [ 14687 ] | |
| Component/s | Code Browsing [ 13143 ] |
Fixed now. In the latest dev build, slashy strings are no longer handled by the GroovyTagScanner, but rather by the semantic highlighter. This means that we look at the AST to figure out where the slashy strings are; we don't use a scanner. And as long as the file is parseable, we can be certain that we are only highlighting the correct parts of the text. Unfortunately, if the text is not parseable, then we don't highlight anything. I think this is a reasonable limitation.