[frameworks-syntax-highlighting] [Bug 373092] Add Krita Dark Syntax Schema

2016-12-06 Thread Volker Krause
https://bugs.kde.org/show_bug.cgi?id=373092 Volker Krause <vkra...@kde.org> changed: What|Removed |Added Assignee|vkra...@kde.org |kwrite-bugs-n...@k

[frameworks-syntax-highlighting] [Bug 373286] syntax highlighting wrong for latex with alignat

2016-12-06 Thread Volker Krause
https://bugs.kde.org/show_bug.cgi?id=373286 Volker Krause <vkra...@kde.org> changed: What|Removed |Added Assignee|vkra...@kde.org |kwrite-bugs-n...@k

[kmail2] [Bug 367598] Kmail needs to force platform xcb on Linux

2017-07-25 Thread Volker Krause
https://bugs.kde.org/show_bug.cgi?id=367598 Volker Krause <vkra...@kde.org> changed: What|Removed |Added CC||vkra...@kde.org --- C

[kcalutils] [Bug 383890] kcalutils-testincidenceformatter test fails in 17.04/17.08

2017-09-14 Thread Volker Krause
https://bugs.kde.org/show_bug.cgi?id=383890 --- Comment #2 from Volker Krause <vkra...@kde.org> --- Right, it's green in master. Probably needs a backport of f839f4fdaa096adb3011b3deac810a03e91560d0. -- You are receiving this mail because: You are watching all bug changes.

[kcalutils] [Bug 383890] kcalutils-testincidenceformatter test fails in 17.04/17.08

2017-10-04 Thread Volker Krause
https://bugs.kde.org/show_bug.cgi?id=383890 Volker Krause <vkra...@kde.org> changed: What|Removed |Added Status|CONFIRMED |RESOLVED Latest

[kmail2] [Bug 385526] recent changes broke multipart display

2017-10-13 Thread Volker Krause
https://bugs.kde.org/show_bug.cgi?id=385526 Volker Krause <vkra...@kde.org> changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Latest

[kmail2] [Bug 394554] Regression: kMail 5.8.1 Information Leak: kMail loads external references in HTML mails without asking

2018-05-22 Thread Volker Krause
https://bugs.kde.org/show_bug.cgi?id=394554 --- Comment #5 from Volker Krause <vkra...@kde.org> --- That would be a very serious security issue obviously, but I can't reproduce this here either. Besides the global setting, there is a per-folder setting for this (Folder -> Load

[kmail2] [Bug 394554] Regression: kMail 5.8.1 Information Leak: kMail loads external references in HTML mails without asking

2018-05-22 Thread Volker Krause
https://bugs.kde.org/show_bug.cgi?id=394554 --- Comment #7 from Volker Krause <vkra...@kde.org> --- It's in the main menu: Folder > Load External References -- You are receiving this mail because: You are watching all bug changes.

[kmail2] [Bug 394554] Regression: kMail 5.8.1 Information Leak: kMail loads external references in HTML mails without asking

2018-05-24 Thread Volker Krause
https://bugs.kde.org/show_bug.cgi?id=394554 --- Comment #11 from Volker Krause <vkra...@kde.org> --- One thing I noticed during testing this is that once you loaded external references for an email, the next display of HTML content without confirming loading external references can be serve

[kmail2] [Bug 394554] Regression: kMail 5.8.1 Information Leak: kMail loads external references in HTML mails without asking

2018-05-26 Thread Volker Krause
https://bugs.kde.org/show_bug.cgi?id=394554 Volker Krause <vkra...@kde.org> changed: What|Removed |Added Latest Commit||https://commits.kde.o

[kmail2] [Bug 394554] Regression: kMail 5.8.1 Information Leak: kMail loads external references in HTML mails without asking

2018-05-24 Thread Volker Krause
https://bugs.kde.org/show_bug.cgi?id=394554 --- Comment #17 from Volker Krause <vkra...@kde.org> --- Possible fix: https://phabricator.kde.org/D13096 -- You are receiving this mail because: You are watching all bug changes.

[kmail2] [Bug 390069] composer window freezes - probably waiting for gpg-agent/pinentry reply?

2018-02-08 Thread Volker Krause
https://bugs.kde.org/show_bug.cgi?id=390069 Volker Krause <vkra...@kde.org> changed: What|Removed |Added CC||vkra...@kde.org -

[frameworks-syntax-highlighting] [Bug 397719] Alert matching differs from KTextEditor to KSyntaxHighlighting

2018-08-22 Thread Volker Krause
https://bugs.kde.org/show_bug.cgi?id=397719 --- Comment #2 from Volker Krause --- This looks like it's caused by a missing space between the alert keyword and the comment marker. I don't have the old version around to compare, but e.g. "/**TODO" with C++ highlighting also doesn't high

[frameworks-syntax-highlighting] [Bug 397719] Alert matching differs from KTextEditor to KSyntaxHighlighting

2018-08-22 Thread Volker Krause
https://bugs.kde.org/show_bug.cgi?id=397719 --- Comment #4 from Volker Krause --- The difference might be that the new implementation for the keyword rule also checks if there's a word delimiter before the keyword, not just after it? That's at least if I read the old implementation correctly

[frameworks-syntax-highlighting] [Bug 397719] Alert matching differs from KTextEditor to KSyntaxHighlighting

2018-08-22 Thread Volker Krause
https://bugs.kde.org/show_bug.cgi?id=397719 --- Comment #6 from Volker Krause --- Indeed, * is a delimiter, but # isn't. So this explains the Python difference but nothing related to C++. Presumably we would see the issue with other languages using # as a comment character though, like Bash

[frameworks-syntax-highlighting] [Bug 397719] Alert matching differs from KTextEditor to KSyntaxHighlighting

2018-08-22 Thread Volker Krause
https://bugs.kde.org/show_bug.cgi?id=397719 --- Comment #8 from Volker Krause --- Seems reasonable, but I can't estimate the impact of this. Maybe run the unit tests with that and see how much breaks? -- You are receiving this mail because: You are watching all bug changes.

[frameworks-ktexteditor] [Bug 397659] Crash when opening PHP file

2018-08-20 Thread Volker Krause
https://bugs.kde.org/show_bug.cgi?id=397659 Volker Krause changed: What|Removed |Added Product|frameworks-syntax-highlight |frameworks-ktexteditor |ing

[Breeze] [Bug 396626] help-about in both preferences and actions

2018-07-18 Thread Volker Krause
https://bugs.kde.org/show_bug.cgi?id=396626 Volker Krause changed: What|Removed |Added CC||vkra...@kde.org -- You are receiving

[frameworks-kuserfeedback] [Bug 391523] Code improvement: reduce unnecessary switch

2018-03-07 Thread Volker Krause
https://bugs.kde.org/show_bug.cgi?id=391523 --- Comment #2 from Volker Krause <vkra...@kde.org> --- Code-wise I agree with your suggestion, but human languages don't work like this unfortunately ;) In English this is fine, in German however the translation of "this" varies base

[frameworks-kuserfeedback] [Bug 391523] Code improvement: reduce unnecessary switch

2018-03-07 Thread Volker Krause
https://bugs.kde.org/show_bug.cgi?id=391523 Volker Krause <vkra...@kde.org> changed: What|Removed |Added Resolution|--- |WONTFIX

[clazy] [Bug 360374] New: Check for QString::left(1) mis-use.

2016-03-10 Thread Volker Krause via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=360374 Bug ID: 360374 Summary: Check for QString::left(1) mis-use. Product: clazy Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist

[clazy] [Bug 360338] New: qstring-ref check does not trigger for toFloat() calls on string temporaries

2016-03-09 Thread Volker Krause via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=360338 Bug ID: 360338 Summary: qstring-ref check does not trigger for toFloat() calls on string temporaries Product: clazy Version: unspecified Platform: Other OS: Linux

[clazy] [Bug 360374] Check for QString::left(1) mis-use.

2016-04-13 Thread Volker Krause via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=360374 --- Comment #2 from Volker Krause <vkra...@kde.org> --- I haven't found a valid use of left(1) yet, so an unconditional warning would probably be fine. In theory it differs from at(0) in that it returns a QString rather than a QChar, which d

[clazy] [Bug 362063] New: [qobject-macro] False positive when implementing qt_metacall manually

2016-04-22 Thread Volker Krause via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362063 Bug ID: 362063 Summary: [qobject-macro] False positive when implementing qt_metacall manually Product: clazy Version: unspecified Platform: Other OS: Linux

[clazy] [Bug 365940] New: Warn when using non-owning smart pointers as associative container key

2016-07-21 Thread Volker Krause via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=365940 Bug ID: 365940 Summary: Warn when using non-owning smart pointers as associative container key Product: clazy Version: unspecified Platform: Other OS: Linux