-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
code in comment make the highlighting less happy #15
Comments
Hm, that looks pretty off even before the comment... Latest vshaxe? What theme are you using? Can you provide the source to copy-paste for easy testing? |
1.3.3 of VSCode and the theme was a stock dark. With other themes the |
Can you provide the source to copy-paste for easy testing? |
static function refreshSlug(slug: Slug) {
var id = slug.toString(),
url = js.Browser.window.location.href, // '${Loc.msg.site_url}/#${slug.toString()}';
title = js.Browser.document.title;
try {
(untyped __js__("DISQUS")).reset({
reload: true,
config: function () {
var self = js.Lib.nativeThis;
self.page.identifier = id;
self.page.url = url;
self.page.title = title;
}
});
} catch(e: Dynamic) {
haxe.Timer.delay(refreshSlug.bind(slug), 25);
}
} |
Thanks, I can reproduce it. :) I guess you're using the "Dark" theme rather than Dark+, which is why it looked off to me. |
This is actually just about comments (or conditional compilation statements for that matter) not being highlighted in multi-var decls. |
See attached image.
The text was updated successfully, but these errors were encountered: