Summary: | Syntax highlighting is correct on load but breaks with editing. | ||
---|---|---|---|
Product: | [Applications] kdevelop | Reporter: | Jeremy W. Murphy <jeremy.william.murphy> |
Component: | Language Support: CPP (Clang-based) | Assignee: | kdevelop-bugs-null |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | |
Priority: | NOR | ||
Version: | git master | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: | Bad/weird syntax highlighting. |
Description
Jeremy W. Murphy
2016-09-12 12:40:03 UTC
Created attachment 101054 [details]
Bad/weird syntax highlighting.
Here is an example: file in the left panel is weird/bad, file in the right panel is fine.
can you please give us an example project (i.e. something we can test ourselves) and tell us which file you are editing, how, and where, to reproduce the issue? this is a really important thing to get fixed, but so far we did not find a reliable way to trigger the issue, thus making the bug fixing pretty much impossible at this point I can confirm the issue is still there, I also see it sometimes. (In reply to Milian Wolff from comment #2) > can you please give us an example project (i.e. something we can test > ourselves) and tell us which file you are editing, how, and where, to > reproduce the issue? Best example I can give you is the code that I am working on right now: https://github.com/jeremy-murphy/algorithm/tree/musser-nishanov-search If you check that out, try editing the file musser-nishanov.hpp. Cheers. (In reply to Jeremy W. Murphy from comment #4) > > If you check that out, try editing the file musser-nishanov.hpp. Sorry, that's "musser_nishanov.hpp". Can you please be exact in what you mean with "try editing"? What exactly are you doing? Inserting text (if so, which one, where?) Or are you removing something? Again, what - where? (In reply to Milian Wolff from comment #6) > Can you please be exact in what you mean with "try editing"? What exactly > are you doing? Inserting text (if so, which one, where?) Or are you removing > something? Again, what - where? I don't have exact criteria for you right now, sorry, but I will try to establish some soon. I should have said that you will need at least a trivial CMake project to build a program that uses Boost headers and thus parses them. And by "editing" I really mean anything, even just inserting white-space in the file would corrupt it. I haven't really seen this behaviour for a while, although I haven't been working on the project where I mostly saw it. What about you, Sven? I think this is fixed; I haven't seen it happen for ages. Sorry, didn't see your first question. This is not fixed, it still happens, although very rarely ... I still haven't seen this happen since 2017, so can we please leave this closed until someone sees it again AND uploads a screenshot? Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |