This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 227106 - syntax coloring not available when opening file type for which module has to be loaded on demand
Summary: syntax coloring not available when opening file type for which module has to ...
Alias: None
Product: editor
Classification: Unclassified
Component: Painting & Printing (show other bugs)
Version: 7.3
Hardware: PC Windows XP
: P3 normal (vote)
Assignee: Miloslav Metelka
: 232003 (view as bug list)
Depends on:
Reported: 2013-03-06 14:23 UTC by olehoppe
Modified: 2016-07-07 07:26 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

IDE log (52.57 KB, text/plain)
2013-03-06 14:23 UTC, olehoppe

Note You need to log in before you can comment on or make changes to this bug.
Description olehoppe 2013-03-06 14:23:39 UTC
Product Version = NetBeans IDE 7.3 (Build 201302132200)
Operating System = Windows XP version 5.1 running on x86
Java; VM; Vendor = 1.7.0_10
Runtime = Java HotSpot(TM) Client VM 23.6-b04

When module loading on demand is activated, and double-clicking on a file type (e.g. .jsp) that the corresponding module has not been loaded for yet, after loading module file opens, but no syntax coloring is applied. Only after restart syntax coloring is done.
Comment 1 olehoppe 2013-03-06 14:23:43 UTC
Created attachment 132268 [details]
IDE log
Comment 2 Jaroslav Tulach 2013-06-04 06:23:25 UTC
If true, then more a bug in editor. FoD does not do anything special with editors, FoD just activates the necessary modules. Maybe the change in colorings is not picked properly up? May I pass it to editor guys for investigation?
Comment 3 Jan Lahoda 2013-07-15 08:56:11 UTC
I'll try to take a look (based on my experience with bug #227106, its going to be quite difficult, though).
Comment 4 Jan Lahoda 2013-07-15 08:57:58 UTC
*** Bug 232003 has been marked as a duplicate of this bug. ***
Comment 5 Miloslav Metelka 2013-08-27 13:00:36 UTC
I guess that change at least of Language for the lexer in a MimeLookup is not actively listened to. It's a question of what to do in such case whether TokenHierarchy should be deactivated and reactivated with a new language probably so. It will likely not be easy to resolve this.
Comment 6 Martin Balin 2016-07-07 07:26:05 UTC
This old bug may not be relevant anymore. If you can still reproduce it in 8.2 development builds please reopen this issue.

Thanks for your cooperation,
NetBeans IDE 8.2 Release Boss