You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using js2-mode together with color-identifiers-mode, then there is an ugly flash where every word in the buffer is colored (even in comments) when a new js file is opened. I tracked this down to the use of (setq font-lock-defaults nil) in js2-mode. I think the issue is that this removes all font-lock keywords/comments so color-identifiers-mode thinks that everything is a variable. Is it possible to delay the removal until the initial parsing of the buffer has finished? (so even if it may not be 100% correct, it would be mostly correct until the initial parsing finishes).
Here's how it looks:
The text was updated successfully, but these errors were encountered:
When using
js2-mode
together withcolor-identifiers-mode
, then there is an ugly flash where every word in the buffer is colored (even in comments) when a new js file is opened. I tracked this down to the use of(setq font-lock-defaults nil)
injs2-mode
. I think the issue is that this removes allfont-lock
keywords/comments socolor-identifiers-mode
thinks that everything is a variable. Is it possible to delay the removal until the initial parsing of the buffer has finished? (so even if it may not be 100% correct, it would be mostly correct until the initial parsing finishes).Here's how it looks:
The text was updated successfully, but these errors were encountered: