Bug 433434 - Code colorization broken
Summary: Code colorization broken
Status: RESOLVED UPSTREAM
Alias: None
Product: kdevelop
Classification: Applications
Component: All editors (other bugs)
Version First Reported In: 5.6.2
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: kdevelop-bugs-null
URL:
Keywords:
: 433974 434672 (view as bug list)
Depends on:
Blocks:
 
Reported: 2021-02-22 17:25 UTC by zvova7890
Modified: 2021-03-21 20:37 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description zvova7890 2021-02-22 17:25:41 UTC 
SUMMARY
Type C/C++ code(not checked on another languages), add new line - all code or part of it will be uncolorized. Only helps if press F5(update source)


STEPS TO REPRODUCE
1. Open C/C++ code
2. Insert new line 
3. Part of code will be uncolorized for all time unless code will be updated(F5)

OBSERVED RESULT
Random parts of code will be uncolorized

EXPECTED RESULT
Recolorized in time

SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 5.21.0
KDE Frameworks Version: 5.79.0
Qt Version: 5.15.2
Kernel Version: 5.10.9-arch1-1
OS Type: 64-bit
Graphics Platform: X11
Processors: 8 × Intel® Core™ i7-3630QM CPU @ 2.40GHz
Memory: 15.5 ГиБ of RAM
Graphics Processor: Mesa DRI Intel® HD Graphics 4000
Comment 1 Francis Herne 2021-02-22 18:11:41 UTC 
This is caused by a bug in KTextEditor, introduced in 5.79.0 and fixed by the linked commit:

https://invent.kde.org/frameworks/ktexteditor/-/commit/686da7797105a93035cfbc7edbf2a8e8f8adf0ec

This should be fixed in KDE Frameworks 5.80 (or 5.79.1 if there is one).
Comment 2 zvova7890 2021-02-22 20:14:43 UTC 
Wow, thank you for fast reply. I will check that patch
Comment 3 Francis Herne 2021-03-04 23:51:13 UTC 
*** Bug 433974 has been marked as a duplicate of this bug. ***
Comment 4 Milian Wolff 2021-03-21 20:37:03 UTC 
*** Bug 434672 has been marked as a duplicate of this bug. ***