Community
Participate
Working Groups
Build Identifier: 20110916-0149 If code has a very long string with an invalid escape sequence, it becomes difficult to find the exact escape sequence that is causing the error. Please make life easier by underlining only the escape sequence that is causing the problem and not the entire string. Steps to Reproduce ------------------ Expected Behavior ----------------- Only the escape sequence in the string should be underlined. Reproducible: Always Steps to Reproduce: 1. Add the following string to a Java file "C:\Bug" 2. Wait for an error to underline with a red squiggle 3. Notice that the entire string is underlined and not the offending escape sequence
I agree, it would be nice to see the invalid escape sequence. @JDT Core: Note that we currently only report one error even if there are multiple invalid escape sequences and in this case, the problem description is wrong as it is still singular.
Will consider, time permitting. Not expecting for 3.8
Shankha, please take a look
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. -- The automated Eclipse Genie.
The problem still exists.
