[Powerdevil] [Bug 358588] backlight not restored properly, after it was reduced on inactivity

https://bugs.kde.org/show_bug.cgi?id=358588 Matteo Croce changed: What|Removed |Added CC||rootki...@yahoo.it ---

[Powerdevil] [Bug 357621] Screen cannot be turned on after it has been set to "energy saving" (goes off)

https://bugs.kde.org/show_bug.cgi?id=357621 Matteo Croce changed: What|Removed |Added CC||rootki...@yahoo.it ---

[Powerdevil] [Bug 352497] laptop back light not coming back on after long period of lcd being in dpms power save mode.

https://bugs.kde.org/show_bug.cgi?id=352497 --- Comment #8 from Matteo Croce --- yes, power plug / unplug actually works -- You are receiving this mail because: You are watching all bug changes.

[kate] [Bug 361127] VIM highlighting is different than original VIM

https://bugs.kde.org/show_bug.cgi?id=361127 --- Comment #11 from Matteo Croce --- Here is it: # Vim (dark), Default Item Styles [Default Item Styles - Schema Vim (dark)] Alert=ffbf0303,ffbf0303,1fff7e6e6,-,,--- Base-N Integer=54ff,54ff,1-,-,,---

[kate] [Bug 361127] VIM highlighting is different than original VIM

https://bugs.kde.org/show_bug.cgi?id=361127 --- Comment #9 from Matteo Croce --- Created attachment 99856 --> https://bugs.kde.org/attachment.cgi?id=99856=edit kate makefile highlighting -- You are receiving this mail because: You are watching all bug changes.

[kate] [Bug 361127] VIM highlighting is different than original VIM

https://bugs.kde.org/show_bug.cgi?id=361127 --- Comment #8 from Matteo Croce --- Created attachment 99855 --> https://bugs.kde.org/attachment.cgi?id=99855=edit vim makefile highlighting -- You are receiving this mail because: You are watching all bug changes.

[kate] [Bug 361127] VIM highlighting is different than original VIM

https://bugs.kde.org/show_bug.cgi?id=361127 Matteo Croce changed: What|Removed |Added Attachment #98132|0 |1 is obsolete|

[kate] [Bug 361127] VIM highlighting is different than original VIM

https://bugs.kde.org/show_bug.cgi?id=361127 Matteo Croce changed: What|Removed |Added Attachment #98131|0 |1 is obsolete|

[kate] [Bug 361127] VIM highlighting is different than original VIM

https://bugs.kde.org/show_bug.cgi?id=361127 --- Comment #5 from Matteo Croce --- Now I'm on another PC with Kate 15.12.3 Color scheme is better but still different to vim for C files, but is almost unreadable for shell scripts because of the dark gray "echo" and [] on black

[kate] [Bug 363134] New: The file content is missing in kate

https://bugs.kde.org/show_bug.cgi?id=363134 Bug ID: 363134 Summary: The file content is missing in kate Product: kate Version: 5.0.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: grave

[kate] [Bug 361127] VIM highlighting is different than original VIM

https://bugs.kde.org/show_bug.cgi?id=361127 --- Comment #2 from Matteo Croce --- Created attachment 98132 --> https://bugs.kde.org/attachment.cgi?id=98132=edit vim highlighting -- You are receiving this mail because: You are watching all bug changes.

[kate] [Bug 361127] VIM highlighting is different than original VIM

https://bugs.kde.org/show_bug.cgi?id=361127 --- Comment #1 from Matteo Croce --- Created attachment 98131 --> https://bugs.kde.org/attachment.cgi?id=98131=edit kate highlighting -- You are receiving this mail because: You are watching all bug changes.

[kate] [Bug 361127] New: VIM highlighting is different than original VIM

https://bugs.kde.org/show_bug.cgi?id=361127 Bug ID: 361127 Summary: VIM highlighting is different than original VIM Product: kate Version: 5.0.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity:

[okteta] [Bug 349222] okteta freezes on file browse dialog

https://bugs.kde.org/show_bug.cgi?id=349222 --- Comment #4 from Matteo Croce --- openwrt$ dpkg -l 'libkf5*' |awk '/^ii/{print$2" "$3}' libkf5activities5:amd64 5.15.0-0ubuntu1 libkf5activitiesexperimentalstats1 4:5.4.2-0ubuntu2 libkf5archive5:amd64 5.15.0-0ubuntu1

[okteta] [Bug 349222] okteta freezes on file browse dialog

https://bugs.kde.org/show_bug.cgi?id=349222 --- Comment #3 from Matteo Croce --- (In reply to Friedrich W. H. Kossebau from comment #2) > Hi Matteo, thanks for the report, and also for telling that the problem > finally disappeared again. > > Can you help me a little more