[frameworks-syntax-highlighting] [Bug 488014] Ruby string interpolation ignored in percent literals
https://bugs.kde.org/show_bug.cgi?id=488014
--- Comment #1 from Marián Konček ---
OBSERVED RESULT
The syntax highlighter displays the content inside for example this string
`%W(#{foo})` in string color.
EXPECTED RESULT
The syntax highlighter should color the string `%W(#{foo})` like it would color
this string `"#{foo}"`.
--
You are receiving this mail because:
You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 488014] New: Ruby string interpolation ignored in percent literals
https://bugs.kde.org/show_bug.cgi?id=488014
Bug ID: 488014
Summary: Ruby string interpolation ignored in percent literals
Classification: Frameworks and Libraries
Product: frameworks-syntax-highlighting
Version: 5.115.0
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: syntax
Assignee: kwrite-bugs-n...@kde.org
Reporter: koncek.mar...@gmail.com
CC: walter.von.entfer...@posteo.net
Target Milestone: ---
SUMMARY
Syntax highlighter correctly distinguishes string interpolation in normal
strings like: "#{foo}".
But in Ruby there are more types of string literals, see:
https://docs.ruby-lang.org/en/master/syntax/literals_rdoc.html#label-Percent+Literals
Percent literals which use an uppercase letter allow interpolation whereas
lowercase letter do not:
%w(#{foo}) # no interpolation, string is taken literally
%W(#{foo}) # foo is interpolated.
STEPS TO REPRODUCE
1.
2.
3.
OBSERVED RESULT
EXPECTED RESULT
SOFTWARE/OS VERSIONS
Windows:
macOS:
Linux/KDE Plasma: 6.8.10-200
(available in About System)
KDE Plasma Version: 5.27.11
KDE Frameworks Version: 5.115.0
Qt Version: 5.15.13
ADDITIONAL INFORMATION
--
You are receiving this mail because:
You are watching all bug changes.
[ksysguard] [Bug 481713] New: Allow moving the Name column in the Process Table
https://bugs.kde.org/show_bug.cgi?id=481713 Bug ID: 481713 Summary: Allow moving the Name column in the Process Table Classification: Applications Product: ksysguard Version: 5.22.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: ksysguard Assignee: ksysguard-b...@kde.org Reporter: koncek.mar...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY I would like to be able to move the Name (of the process) column to the right and for example move the PID column to the left of it. It is currently impossible to move the Name column around. I do not see any reason to disallow moving it. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 472456] Laptop wakes up from screen saving mode in full brightness
https://bugs.kde.org/show_bug.cgi?id=472456 Marián Konček changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |CONFIRMED --- Comment #9 from Marián Konček --- I don't think so, I guess I will have to get used to it. Truth is, I opened the bug because I noticed the behaviour changed from what I was used to. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 474283] Dolphin crashes when connecting to Thunderbolt
https://bugs.kde.org/show_bug.cgi?id=474283 Marián Konček changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|BACKTRACE |--- --- Comment #5 from Marián Konček --- The crash reporting daemon does not catch this crash for some reason. I downloaded the debuginfo packages and ran Dolphin in gdb. I will keep the stopped process running for as long as possible, so you can ask about variables and so... -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 474283] Dolphin crashes when connecting to Thunderbolt
https://bugs.kde.org/show_bug.cgi?id=474283 --- Comment #4 from Marián Konček --- Created attachment 163109 --> https://bugs.kde.org/attachment.cgi?id=163109=edit gdb stack trace -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 474283] Dolphin crashes when connecting to Thunderbolt
https://bugs.kde.org/show_bug.cgi?id=474283 --- Comment #2 from Marián Konček --- Created attachment 162177 --> https://bugs.kde.org/attachment.cgi?id=162177=edit Output of journalctl -f Adding the output of journalctl just before plugging the Thunderbolt in. Note the line: okt 09 15:30:25 fedora plasmashell[358272]: KCrash: Application 'dolphin' crashing... -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 474283] Dolphin crashes when connecting to Thunderbolt
https://bugs.kde.org/show_bug.cgi?id=474283 --- Comment #1 from Marián Konček --- There is a typo in the Description, should have been: ``` *a single* instance of Dolphin exits with no crash notification. ``` -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 474283] New: Dolphin crashes when connecting to Thunderbolt
https://bugs.kde.org/show_bug.cgi?id=474283 Bug ID: 474283 Summary: Dolphin crashes when connecting to Thunderbolt Classification: Applications Product: dolphin Version: 23.04.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: koncek.mar...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY Crash happens without a notification. No backtrace available. I am running Fedora 38, KDE, Wayland. I have multiple instances of Dolphin on virtual desktops. When I unplug the Thunderbolt plugin, the screen rearranges, but no crash happens. After plugging the Thunderbolt back in, *a single* instance of Dolphin exists with no crash notification. I tried executing Dolphin from a terminal to see if I could get some standard output, but that instance did not crash. On my docking station I have: mouse, keyboard, Jack headphones, Ethernet, 2 external monitors and the laptop monitor is set to be disabled. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 38 Kernel: 6.4.4-200.fc38.x86_64 (64-bit) (available in About System) KDE Plasma Version: 5.27.7 KDE Frameworks Version: 5.109.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION I haven't noticed any other program exiting like this. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 469838] Regression: Kate LSP client (Rust analyzer) does not autofill arguments and return types
https://bugs.kde.org/show_bug.cgi?id=469838 Marián Konček changed: What|Removed |Added Version Fixed In||23.04.3 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 469838] Regression: Kate LSP client (Rust analyzer) does not autofill arguments and return types
https://bugs.kde.org/show_bug.cgi?id=469838 Marián Konček changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Marián Konček --- This seems to be fixed as of version 23.04.3. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 472456] Laptop wakes up from screen saving mode in full brightness
https://bugs.kde.org/show_bug.cgi?id=472456 Marián Konček changed: What|Removed |Added Ever confirmed|1 |0 Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 473716] New: Incorrect coloring of nested $$() entries of Make files
https://bugs.kde.org/show_bug.cgi?id=473716 Bug ID: 473716 Summary: Incorrect coloring of nested $$() entries of Make files Classification: Frameworks and Libraries Product: frameworks-syntax-highlighting Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: syntax Assignee: kwrite-bugs-n...@kde.org Reporter: koncek.mar...@gmail.com CC: walter.von.entfer...@posteo.net Target Milestone: --- Created attachment 161153 --> https://bugs.kde.org/attachment.cgi?id=161153=edit Example of incorrect coloring SUMMARY Incorrect coloring of nested $$() entries of Make files. STEPS TO REPRODUCE 1. Try to open this file in Kate / Kwrite https://github.com/fedora-java/jurand/blob/663ff198e8478650b82f7f4d31f3c7663ee527c0/rules.mk#L19 OBSERVED RESULT Nested entries like $$() are colored incorrectly (ending parenthesis has different color than the leading parenthesis. EXPECTED RESULT Parentheses should be colored consistently, i. e. $$ should be handled by the syntax parser. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora KDE 38 (available in About System) KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.108.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 472456] Laptop wakes up from screen saving mode in full brightness
https://bugs.kde.org/show_bug.cgi?id=472456 --- Comment #2 from Marián Konček --- My argument is that for some (most ?) Linux laptops, having brightness at 0 % means that the screen is more-less completely black. Waking up the screen from screen saving mode could not be visible to the user. (I am aware that setting "acpi_osi=Windows 2015" kernel parameter changes the range of brighntess settings but I am accustomed to the current behaviour.) Another argument is that the behaviour I was describing was in KDE maybe up until 2-3 years ago. I have wanted to submit this for a long time but got to it only now. I could try to look up some Fedora version for which that was the case... -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 472456] Laptop wakes up from screen saving mode in full brightness
https://bugs.kde.org/show_bug.cgi?id=472456 Marián Konček changed: What|Removed |Added Summary|Windows wakes up from |Laptop wakes up from screen |screen saving mode in full |saving mode in full |brightness |brightness -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 472456] New: Windows wakes up from screen saving mode in full brightness
https://bugs.kde.org/show_bug.cgi?id=472456 Bug ID: 472456 Summary: Windows wakes up from screen saving mode in full brightness Classification: Plasma Product: kwin Version: 5.27.6 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: koncek.mar...@gmail.com Target Milestone: --- SUMMARY When lowering a laptop's brightness to a minimum (i. e. 0 %) by pressing the Fn keys, waiting for the screen saving (which turns off the screen) mode to activate and then moving the mouse to wake the screen, the screen has maximum brightness. It is worth mentioning that changing the brightness with Fn keys behaves as-if the brighntess was at 0 %. I. e. lowering the brightness goes to 0 %, increasing it goes to 5 %. When the brightness is above 0 %, then it wakes up to the correct previous brightness. This behaviour was also different some ~ 2 years ago, when the screen would wake up to the 5 % (?) or some other small value that was not 0 %. STEPS TO REPRODUCE 1. On a laptop, manually lower the screen's brightness to 0 %. (The screen is now almost completely black) 2. Wait for the screen saving mode to turn off the screen (not sleep, not screen dim) 3. Perform any action that wakes up the screen. (e. g. move mouse) OBSERVED RESULT Laptop screen now has 100 % brightness. EXPECTED RESULT Screen should wake up with the minimal **user-visible** screen brightness, i. e. one Fn button press away from 0 %. Which usually is 5 %. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora KDE 38 (available in About System) KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION This issue was observer first time a few years ago. Behaviour is the same on X11 and Wayland. Behaviour is the same no matter whether external monitors are connected. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 469838] New: Regression: Kate LSP client (Rust analyzer) does not autofill arguments and return types
https://bugs.kde.org/show_bug.cgi?id=469838
Bug ID: 469838
Summary: Regression: Kate LSP client (Rust analyzer) does not
autofill arguments and return types
Classification: Applications
Product: kate
Version: 23.04.0
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: kwrite-bugs-n...@kde.org
Reporter: koncek.mar...@gmail.com
Target Milestone: ---
SUMMARY
After and update in Fedora 38, this feature no longer works.
I tried downgrading all rust* + cargo* packages, the issue remained. After
downgrading Kate, the feature worked again.
Version known working: 22.12.3
Version known not working: 23.04.0
STEPS TO REPRODUCE
1. Open and Rust project in Kate with LSP plugin active and rust-analyzer
binary available
2. In the following code:
```
struct S {}
impl Drop for S
{
}
```
press Ctrl + Space to force autocompletion menu.
In Kate version 22.12.3, it would autofill this string `fn drop( self) {`.
In Kate version 23.04.0, it would autofill this string `fn drop(..)`.
OBSERVED RESULT
Arguments and return types of implemented methods are missing.
EXPECTED RESULT
Arguments and return types of implemented methods should be autofilled.
SOFTWARE/OS VERSIONS
Linux: Fedora 38
--
You are receiving this mail because:
You are watching all bug changes.
[kompare] [Bug 465165] New: "Files are identical" should not throw an error
https://bugs.kde.org/show_bug.cgi?id=465165 Bug ID: 465165 Summary: "Files are identical" should not throw an error Classification: Applications Product: kompare Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kompare-de...@kde.org Reporter: koncek.mar...@gmail.com Target Milestone: --- Opening Kompare with 2 files whose content is identical opens up an error popup window. I don't think it should do so, I think it should be a Note window at most. Error window makes the user think something has broken somewhere at the first glance. -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 464134] Internal document viewer does not handle specific XML files
https://bugs.kde.org/show_bug.cgi?id=464134 Marián Konček changed: What|Removed |Added Platform|Other |Fedora RPMs -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 464134] New: Internal document viewer does not handle specific XML files
https://bugs.kde.org/show_bug.cgi?id=464134 Bug ID: 464134 Summary: Internal document viewer does not handle specific XML files Classification: Applications Product: ark Version: 22.12.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: plugins Assignee: elvis.angelac...@kde.org Reporter: koncek.mar...@gmail.com CC: aa...@kde.org, rthoms...@gmail.com Target Milestone: --- Created attachment 155204 --> https://bugs.kde.org/attachment.cgi?id=155204=edit Image how it looks on my machine Steps to reproduce: * Download for example: https://kojipkgs.fedoraproject.org//packages/jakarta-activation1/1.2.2/4.fc38/noarch/jakarta-activation1-1.2.2-4.fc38.noarch.rpm * Open the file in Ark * Open the file "usr/share/maven-metadata/jakarta-activation1.xml" The new window opened by Ark does not do syntax highlighting of XML file. Additionally, the two buttons right to "File" in top left corner display "No Text" as the button name. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460303] wayland: activating an app on another virtual desktop doesn't open a new instance in the current virtual desktop as it does on X11
https://bugs.kde.org/show_bug.cgi?id=460303 --- Comment #3 from Marián Konček --- Yeah, but from X11, I also expect the option to have multiple instances of Kate one per virtual desktop. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460303] New: wayland: opening a text file adds a new tab in a different virtual desktop
https://bugs.kde.org/show_bug.cgi?id=460303 Bug ID: 460303 Summary: wayland: opening a text file adds a new tab in a different virtual desktop Classification: Plasma Product: kwin Version: 5.25.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: koncek.mar...@gmail.com Target Milestone: --- I noticed this issue on wayland: When i open a text file from Dolphin in a virtual desktop, it adds a new tab to a different already running instance of Kate in a different virtual desktop instead of launching a new window in the current one. This is different from X11 which would launch a new window in the current virtual desktop unless there is already a running instance in the current virtual desktop. Note that launching Kate manually does indeed launch a new instance. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460195] The whole screen blinks irregularly
https://bugs.kde.org/show_bug.cgi?id=460195 --- Comment #2 from Marián Konček --- Should i look for some specific logs when this happens? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460195] The whole screen blinks irregularly
https://bugs.kde.org/show_bug.cgi?id=460195 --- Comment #1 from Marián Konček --- It happens often while in Alt + Tab selection but I noticed it also happening when I was just looking at screen. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460195] New: The whole screen blinks irregularly
https://bugs.kde.org/show_bug.cgi?id=460195 Bug ID: 460195 Summary: The whole screen blinks irregularly Classification: Plasma Product: kwin Version: 5.25.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: core Assignee: kwin-bugs-n...@kde.org Reporter: koncek.mar...@gmail.com Target Milestone: --- Info: happens on both Fedora 37 and 38 using X11 KDE Plasma version: 5.25.5 Qt version 5.15.6 >From time to time, like once per several hours the whole screen goes black for about a second then it goes back to normal. It takes a total of about 2 seconds to return. It seems like everything works properly afterwards other than the fact that minimizing any window sets its minimized size to the whole screen instead of what was there previously. I use 2 monitors on both setups where i noticed this. I also noticed this started happening after updating from Fedora 36 or Fedora 35, I am not sure. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 458864] Okular does not render markown documents starting with ##
https://bugs.kde.org/show_bug.cgi?id=458864 --- Comment #2 from Marián Konček --- Just updated Okular and confirm that the document is rendered properly now. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 458864] New: Okular does not render markown documents starting with ##
https://bugs.kde.org/show_bug.cgi?id=458864 Bug ID: 458864 Summary: Okular does not render markown documents starting with ## Product: okular Version: 22.08.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: markdown backend Assignee: okular-de...@kde.org Reporter: koncek.mar...@gmail.com Target Milestone: --- Created attachment 151917 --> https://bugs.kde.org/attachment.cgi?id=151917=edit Example Open the attached example in Okular, it is not rendered as a markdown document. Real world example: https://raw.githubusercontent.com/cbeust/jcommander/master/CHANGELOG.md -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 424423] Keyboard not selected correctly on login
https://bugs.kde.org/show_bug.cgi?id=424423 Marián Konček changed: What|Removed |Added CC||koncek.mar...@gmail.com --- Comment #3 from Marián Konček --- This bug is still present on current Fedora Rawhide. >From what I remember, this problem started occurring since the login screen started using Wayland (?) along with other issues like screen blinking. And from what I remember, the default keyboard layout language was not actually English but Afrikaans, which has the same layout as English and is first in the list of languages. Selecting other languages still does nothing. I consider this a serious issue. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 456434] Okular does not handle markdown comments
https://bugs.kde.org/show_bug.cgi?id=456434 --- Comment #6 from Marián Konček --- (In reply to Marián Konček from comment #2) > Sure, here: > https://github.com/osgi/osgi/blob/4ba3d49d9cc4b71dc1ed65ad8300d93e294601b6/ > README.md > https://github.com/raphw/byte-buddy/blob/ > 94c0a54ca030ad1ae390015373376118e9fd83d5/README.md > > I don't know whether XML is allowed in MD documents but KDE's syntax > highlighter highlights XML nodes in MD documents when the file it opened in > Kate for example. I used a wrong example, i downloaded it with wget, but the whole webpage, not just the document... In any case I do remember other cases where this issue happened as I am a package maintainer and there was some case of such a document present in the sources. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 456434] Okular does not handle markdown comments
https://bugs.kde.org/show_bug.cgi?id=456434 Marián Konček changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #5 from Marián Konček --- No, but neither those are rendered by Okular and contain XML nodes. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 456434] Okular does not handle markdown comments
https://bugs.kde.org/show_bug.cgi?id=456434 --- Comment #4 from Marián Konček --- Created attachment 151144 --> https://bugs.kde.org/attachment.cgi?id=151144=edit Example which doesn't render properly -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 456434] Okular does not handle markdown comments
https://bugs.kde.org/show_bug.cgi?id=456434 Marián Konček changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #2 from Marián Konček --- Sure, here: https://github.com/osgi/osgi/blob/4ba3d49d9cc4b71dc1ed65ad8300d93e294601b6/README.md https://github.com/raphw/byte-buddy/blob/94c0a54ca030ad1ae390015373376118e9fd83d5/README.md I don't know whether XML is allowed in MD documents but KDE's syntax highlighter highlights XML nodes in MD documents when the file it opened in Kate for example. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 456434] New: Okular does not handle markdown comments
https://bugs.kde.org/show_bug.cgi?id=456434 Bug ID: 456434 Summary: Okular does not handle markdown comments Product: okular Version: 21.12.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: markdown backend Assignee: okular-de...@kde.org Reporter: koncek.mar...@gmail.com Target Milestone: --- (Tested on Fedora 35) If a markdown document contains (or at least starts with XML comments in the form of ``, Then it does not render the rest of the document properly. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455314] Icons-only Task Manager resets placement after re-plugging monitors
https://bugs.kde.org/show_bug.cgi?id=455314 --- Comment #2 from Marián Konček --- Tested again on a different laptop with KDE Plasma 5.25 KDE Frameworks: 5.94.0 QT: 5.15.3 (Current Fedora Rawhide) It looks like the issue is still the same, however after attempting it with the newer one, I again plugged in the older one (the one the issue is reported for) and the icons-only task manager stayed on the right this time... I should add that I am using Thunderbolt -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455314] New: Icons-only Task Manager resets placement after re-plugging monitors
https://bugs.kde.org/show_bug.cgi?id=455314 Bug ID: 455314 Summary: Icons-only Task Manager resets placement after re-plugging monitors Product: plasmashell Version: 5.24.4 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: plasma-b...@kde.org Reporter: koncek.mar...@gmail.com Target Milestone: 1.0 I am using a laptop and most of the time I am using 2-monitor setup with my primary monitor being the right one. When I disconnect the monitors and reconnect them, then my Icons-only Task Manager shows up on the left monitor and I have to drag it manually each time to the right. I believe, the task manager should be reset to the monitor that is set as primary and not the leftmost one. I don't know how this would work in Wayland where there is no option to set primary monitor. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora Linux KDE Plasma (available in About System) KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 450878] Regression? highlighting bash code with comments
https://bugs.kde.org/show_bug.cgi?id=450878 --- Comment #6 from Marián Konček --- Created attachment 148574 --> https://bugs.kde.org/attachment.cgi?id=148574=edit Bash variable substitution - image -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 450878] Regression? highlighting bash code with comments
https://bugs.kde.org/show_bug.cgi?id=450878 Marián Konček changed: What|Removed |Added CC||koncek.mar...@gmail.com --- Comment #5 from Marián Konček --- Created attachment 148573 --> https://bugs.kde.org/attachment.cgi?id=148573=edit Bash variable substitution - text -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 437304] New: Add syntax highlighting for .gcov files
https://bugs.kde.org/show_bug.cgi?id=437304 Bug ID: 437304 Summary: Add syntax highlighting for .gcov files Product: frameworks-syntax-highlighting Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: syntax Assignee: kwrite-bugs-n...@kde.org Reporter: koncek.mar...@gmail.com CC: walter.von.entfer...@posteo.net Target Milestone: --- Please add syntax highlighting for files generated by gcov command for executables compiled with coverage mode. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 432146] New: Inconsistent wrap-around for Next / Previous unread article
https://bugs.kde.org/show_bug.cgi?id=432146 Bug ID: 432146 Summary: Inconsistent wrap-around for Next / Previous unread article Product: akregator Version: 5.15.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: koncek.mar...@gmail.com Target Milestone: --- OS: Fedora 33 Version: akregator 5.15.3 (20.08.3) Given a feed with unread articles, pressing "Next / Previous unread article" either via a keyboard shortcut or a button the behaviour of wrapping around the list of articles is inconsistent: * If the current selected article is at the very top of the list, then "Previous unread article" will stay on its position. * If the current selected article is not at the top but above it there are only articles that have been marked as read then pressing "Previous unread article" will wrap-around the list and jump to the last unread article. The same happens with "Next unread article" if the current selected article is / is not at the bottom of the list. I am filling a bug for this inconsistency, personally I would prefer to always wrap around or in the other case give an easy access to the last unread article. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 418220] crash on libclang parsing
https://bugs.kde.org/show_bug.cgi?id=418220 --- Comment #2 from Marián Konček --- To be precise, Kdevelop crashes when I press F5 or simply force reparsing on the .cpp file. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 418220] crash on libclang parsing
https://bugs.kde.org/show_bug.cgi?id=418220 --- Comment #1 from Marián Konček --- Created attachment 126424 --> https://bugs.kde.org/attachment.cgi?id=126424=edit Stack trace (not exactly corresponding to the the source file) -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 418220] New: crash on libclang parsing
https://bugs.kde.org/show_bug.cgi?id=418220 Bug ID: 418220 Summary: crash on libclang parsing Product: kdevelop Version: 5.5.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Language Support: CPP (Clang-based) Assignee: kdevelop-bugs-n...@kde.org Reporter: koncek.mar...@gmail.com Target Milestone: --- Created attachment 126423 --> https://bugs.kde.org/attachment.cgi?id=126423=edit Source file that causes the crash Description of problem: Kdevelop crashes when parsing C++ code using libclang. Version-Release number of selected component (if applicable): kdevelop-5.5.0-1.fc31.src.rpm clang-9.0.0-1.fc31.src.rpm How reproducible: In KDevelop create an empty .cpp file and #include the attached .hpp file. KDevelop then crashes. Additional info: In my case if I have the same code directly in .cpp file it does not crash (but I have disabled background parsing, but KDevelop does parse code when switching tabs). ### imporant lines: 19-30 of the provided source file. Currently clang does not compile code that uses "auto&" as parameters. Note that i am using "auto&" as function parameters on other places within KDevelop and although it doesn't like them, most of the code is parsed anyway. The crash does not happen when: 1) changing the auto& parameter for a proper template typename parameter as in: template static auto static_find(Self& self, const Key_type& key) 2) replacing the structured binding for a single variable initialization. -- You are receiving this mail because: You are watching all bug changes.
