-
Notifications
You must be signed in to change notification settings - Fork 256
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
fix multiline highlighting was ~add ci test for non optional build~ #594
Conversation
I encountered a similar problem when I tried debugging my changes. In that case it was impossible to build hotspot without |
Nice, the ci found the first bug already |
c14b27f
to
a3b2909
Compare
dammit, it broke the disassembler |
a3b2909
to
c76fd1c
Compare
now it is working correctly |
Nice work! the PR's title may should be adjusted, or the changes split into two PRs (I don't think that's necessary as long as it is split in the commits) |
f13a9e2
to
f5aef07
Compare
I split the ci change off into its own pr |
I do wonder if not resetting the highlighter has any performance impact |
It has. Until this patch the Highlighter was called on demand. Now it is called once for the whole file. |
c76fd1c
to
411d7b9
Compare
I guess that's good to go after solving the merge conflict. |
411d7b9
to
df3e5bd
Compare
Just wondering: Is there anything blocking the pull here? |
Milians high workload. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can you also add a test for this please? otherwise feel free to merge as-is for now already
If the state is reset every line KSyntaxHighlighter will be unable to highlight multi line comments (for example). This patch changes that by highlighting everyting at once.
df3e5bd
to
9f76aac
Compare
This commit adds a ci build to build hotspot without optional dependencies. This should prevents bugs like #575 (fails to build without qcustomplot).