Bug 453742 - color coding is offset by number preceding umlauts per line
Summary: color coding is offset by number preceding umlauts per line
Status: RESOLVED DUPLICATE of bug 274430
Alias: None
Product: kdevelop
Classification: Applications
Component: UI: general (show other bugs)
Version: 5.7.211203
Platform: Kubuntu Linux
: NOR minor
Target Milestone: ---
Assignee: kdevelop-bugs-null
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-05-13 14:23 UTC by leokapp44
Modified: 2022-05-14 12:36 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Screenshot of observed result (39.23 KB, image/png)
2022-05-13 14:23 UTC, leokapp44
Details

Note You need to log in before you can comment on or make changes to this bug.
Description leokapp44 2022-05-13 14:23:37 UTC
Created attachment 148796 [details]
Screenshot of observed result

STEPS TO REPRODUCE
1. create a *.c file
2. enter some code that will be color coded and includes umlauts near the beginning of a line. For example:
´´´
#include <stdio.h>

int var;

int main() {
    printf("äää %d\n", var); //asdf
    // if I hover over    ^^^ this section (which is currently in the color of var)
    // I get the Pop Up I would normally get while hovering over var.
    // var itself is displayed in black like printf.
    // the string has the expected color coding.
}
´´´
3. hover over some variable behind the umlauts.

OBSERVED RESULT
See comment in sample code. The color and the hover sensitive range is in the wrong place. (See attachment)

EXPECTED RESULT
var should be green and if I hover over var I should get the popup.


SOFTWARE/OS VERSIONS
Operating System: Kubuntu 22.04
KDE Plasma Version: 5.24.4
KDE Frameworks Version: 5.92.0
Qt Version: 5.15.3
Kernel Version: 5.15.0-27-generic (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz
Memory: 15,4 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620

ADDITIONAL INFORMATION
For all I know, I didn't tweak any color coding settings. I don't know since when this bug exists.
Comment 1 Igor Kushnir 2022-05-14 12:36:37 UTC

*** This bug has been marked as a duplicate of bug 274430 ***