Bug 549340 - [code mining] Java files loose syntax colors with code minings in method params
Summary: [code mining] Java files loose syntax colors with code minings in method params
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Text (show other bugs)
Version: 4.13   Edit
Hardware: PC Windows 10
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-Text-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords: ui
Depends on:
Blocks:
 
Reported: 2019-07-17 06:17 EDT by Luis Villa CLA
Modified: 2021-07-07 05:33 EDT (History)
1 user (show)

See Also:

Attachments
First exception thrown (618.57 KB, application/octet-stream)
2019-07-17 06:17 EDT, Luis Villa CLA 		no flags Details
Second exception thrown (618.57 KB, application/octet-stream)
2019-07-17 06:19 EDT, Luis Villa CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Luis Villa CLA 2019-07-17 06:17:29 EDT 
Created attachment 279305 [details]
First exception thrown

With some java files open, sometimes syntax coloring breaks (and all text is in grey) when code minings (only show method parameter names). Everytime I write a letter, two exceptions are launched (attached to this bug).
Comment 1 Luis Villa CLA 2019-07-17 06:19:03 EDT 
Created attachment 279306 [details]
Second exception thrown
Comment 2 Mickael Istria CLA 2019-07-17 06:39:35 EDT 
Can you please share an example file that allows to reproduce the issue?
Comment 3 Luis Villa CLA 2019-07-17 07:09:02 EDT 
After disabling code minings and enabling it again the error is not reproducing (with the same file). When it happens again, I'll attach the java file.
Comment 4 Eclipse Genie CLA 2021-07-07 05:33:37 EDT 
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. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. 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.