As stated in the summary, syntax is correctly highlighted when a file is first loaded. But do some editing, and the highlighting quickly falls apart, leaving partially or weirdly highlighted syntax. A co-morbidity is the disappearance of icons from the auto-complete pop-up dialogue. Note that this is the tip of the 5.0 branch, not tip of master. Reproducible: Sometimes Steps to Reproduce: 1. Open a relatively complex project (uses Boost?) 2. Start editing a file. Actual Results: Weird, partial, mostly absent syntax highlighting. Expected Results: Correct syntax highlighting. Portage 2.2.28 (python 3.4.3-final-0, default/linux/amd64/13.0/desktop/plasma, gcc-4.9.3, glibc-2.22-r4, 4.4.19-gentoo x86_64) ================================================================= System Settings ================================================================= System uname: Linux-4.4.19-gentoo-x86_64-Intel-R-_Core-TM-_i5-2540M_CPU_@_2.60GHz-with-gentoo-2.2 KiB Mem: 16313444 total, 5224680 free KiB Swap: 4194300 total, 4194144 free Timestamp of repository gentoo: Mon, 12 Sep 2016 08:15:01 +0000 sh bash 4.3_p42-r1 ld GNU gold (Gentoo 2.25.1 p1.1 2.25.1) 1.11 app-shells/bash: 4.3_p42-r1::gentoo dev-java/java-config: 2.2.0-r3::gentoo dev-lang/perl: 5.20.2::gentoo dev-lang/python: 2.7.10-r1::gentoo, 3.4.3-r1::gentoo dev-util/cmake: 3.5.2-r1::gentoo dev-util/pkgconfig: 0.28-r2::gentoo sys-apps/baselayout: 2.2::gentoo sys-apps/openrc: 0.21.3::gentoo sys-apps/sandbox: 2.10-r1::gentoo sys-devel/autoconf: 2.13::gentoo, 2.69::gentoo sys-devel/automake: 1.11.6-r1::gentoo, 1.14.1::gentoo, 1.15::gentoo sys-devel/binutils: 2.25.1-r1::gentoo sys-devel/gcc: 4.9.3::gentoo, 5.4.0::gentoo sys-devel/gcc-config: 1.7.3::gentoo sys-devel/libtool: 2.4.6::gentoo sys-devel/make: 4.1-r1::gentoo sys-kernel/linux-headers: 4.4::gentoo (virtual/os-headers) sys-libs/glibc: 2.22-r4::gentoo Repositories: gentoo location: /usr/portage sync-type: rsync sync-uri: rsync://rsync.au.gentoo.org/gentoo-portage priority: -1000 Local location: /usr/local/portage masters: gentoo kde location: /var/lib/layman/kde masters: gentoo priority: 0 science location: /var/lib/layman/science masters: gentoo priority: 1 jorgicio location: /var/lib/layman/jorgicio masters: gentoo priority: 2 x11 location: /var/lib/layman/x11 masters: gentoo priority: 3 ACCEPT_KEYWORDS="amd64" ACCEPT_LICENSE="* -@EULA Google-TOS google-talkplugin google-chrome FAH-EULA-2009 Intel-SDP skype-4.0.0.7-copyright" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-O2 -pipe -march=native" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/lib64/libreoffice/program/sofficerc /usr/share/config /usr/share/gnupg/qualified.txt" CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/dconf /etc/env.d /etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release /etc/revdep-rebuild /etc/sandbox.d /etc/terminfo /etc/texmf/language.dat.d /etc/texmf/language.def.d /etc/texmf/updmap.d /etc/texmf/web2c" CXXFLAGS="-O2 -pipe -march=native" DISTDIR="/usr/portage/distfiles" FCFLAGS="-O2 -pipe" FEATURES="assume-digests binpkg-logs config-protect-if-modified distlocks ebuild-locks fixlafiles merge-sync news parallel-fetch parallel-install preserve-libs protect-owned sandbox sfperms strict unknown-features-warn unmerge-logs unmerge-orphans userfetch userpriv usersandbox usersync xattr" FFLAGS="-O2 -pipe" GENTOO_MIRRORS="http://distfiles.gentoo.org" LANG="en_AU.utf8" LDFLAGS="-Wl,-O1 -Wl,--as-needed" MAKEOPTS="-j4" PKGDIR="/usr/portage/packages" PORTAGE_CONFIGROOT="/" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --omit-dir-times --compress --force --whole-file --delete --stats --human-readable --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages --exclude=/.git" PORTAGE_TMPDIR="/var/tmp" USE="X a52 aac aalib acl acpi alsa amd64 ao avahi bash-completion berkdb blas bluetooth branding bzip2 c++0x cairo caps cdda cdr cli consolekit cracklib crypt css cups curl cvs cxx dbus declarative djvu dri dts dv dvd dvdr emboss encode exif expat fam ffmpeg fftw firefox flac fontconfig fortran gd gdbm geoip gif git glamor gmp gnuplot gnutls gphoto2 gpm graphviz gsl gsm gtk hdf5 iconv icu idn ieee1394 imagemagick imlib ipod ipv6 java6 javascript jit jpeg jpeg2k kipi ladspa lame lapack laptop latex lcms ldap libnotify libsamplerate libwww lzma lzo mad matroska mmap mmx mmxext mng modules mp3 mp4 mpeg mtp multilib mysql mysqli ncurses networkmanager nls nptl nsplugin ntfs offensive ogg openal openexr opengl openmp pam pango pch pcre pdf phonon plasma plotutils png policykit postscript ppds qml qt3support qt5 readline samba sasl scanner sdl seccomp semantic-desktop session sharedmem skey smp sndfile sox speex spell sqlite sqlite3 sse sse2 sse3 ssl startup-notification subversion svg syslog szip taglib tcpd theora threads tiff tk truetype udev udisks unicode upnp upower usb v4l vcd vnc vorbis wavpack wayland widgets wifi wmf wxwidgets x264 xattr xcb xcomposite xinerama xml xpm xscreensaver xv xvid zeroconf zlib" ABI_X86="64" ALSA_CARDS="hda-intel" APACHE2_MODULES="authn_core authz_core socache_shmcb unixd actions alias auth_basic authn_alias authn_anon authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache cgi cgid dav dav_fs dav_lock deflate dir disk_cache env expires ext_filter file_cache filter headers include info log_config logio mem_cache mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias" CALLIGRA_FEATURES="kexi words flow plan sheets stage tables krita karbon braindump author" CAMERAS="ptp2" COLLECTD_PLUGINS="df interface irq load memory rrdtool swap syslog" CPU_FLAGS_X86="aes avx mmx mmxext popcnt sse sse2 sse3 sse4_1 sse4_2 ssse3" ELIBC="glibc" GPSD_PROTOCOLS="ashtech aivdm earthmate evermore fv18 garmin garmintxt gpsclock itrax mtk3301 nmea ntrip navcom oceanserver oldstyle oncore rtcm104v2 rtcm104v3 sirf superstar2 timing tsip tripmate tnt ublox ubx" INPUT_DEVICES="evdev synaptics" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LIBREOFFICE_EXTENSIONS="presenter-console presenter-minimizer" LINGUAS="en en_AU en_GB" OFFICE_IMPLEMENTATION="libreoffice" PHP_TARGETS="php5-6" PYTHON_SINGLE_TARGET="python2_7" PYTHON_TARGETS="python2_7 python3_4" RUBY_TARGETS="ruby20 ruby21" USERLAND="GNU" VIDEO_CARDS="intel" XTABLES_ADDONS="quota2 psd pknock lscan length2 ipv4options ipset ipp2p iface geoip fuzzy condition tee tarpit sysrq steal rawnat logmark ipmark dhcpmac delude chaos account" Unset: CC, CPPFLAGS, CTARGET, CXX, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LC_ALL, PORTAGE_BUNZIP2_COMMAND, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS, USE_PYTHON ================================================================= Package Settings ================================================================= dev-util/kdevelop-5.0.9999::kde was built with the following: USE="cmake cxx gdbui handbook ninja okteta plasma qmake -debug -qthelp -test" ABI_X86="64"
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!