Summary: | Add support for ':' as separator for extended color codes; watch out for index off-by-one | ||
---|---|---|---|
Product: | [Applications] konsole | Reporter: | Egmont Koblinger <egmont> |
Component: | emulation | Assignee: | Konsole Developer <konsole-devel> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | justin.zobel, ninjalj |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | 316a386d92a083e235624e9f81df3b6dbbe08bff | Version Fixed In: | v22.08.0 |
Description
Egmont Koblinger
2017-12-14 21:07:41 UTC
Egmont thanks for the information. If this is still an issue, would you be interested in submitting a patch to fix this to https://invent.kde.org/utilities/konsole/-/merge_requests/ 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! > would you be interested in submitting a patch
No, sorry, not.
Let me tell you: I'm honestly disappointed in the attitude I'm seeing in bulk nowadays from Konsole's bugtracker.
First, I don't understand why this question justified the NEEDINFO state. You do not _need_ information from me. You could just go ahead and fix this bug.
There are situations that justify NEEDINFO, e.g. when you cannot reproduce the bug, or don't understand what the reporter says. Apparently this is not the case here. You are not blocked in any way.
Second, this Janitor bot auto-closing bugs.
You, dear KDE developers, often leave a bug unanswered for _years_. You even leave _patches_ lying around for years without commenting on them. I understand, you are all humans, you have finite capacity, you probably all volunteer to do this. I also used to walk in these shoes for a long time, and probably will do again.
But you really should not combine this with giving 45 days for OP to respond. There are hundreds of reasons why the poster does not respond within this time frame, none of those make the bugreport any less accurate.
You should seriously reconsider your workflow.
The current one hardly leads to better quality software in the long run. After all, why wouldn't you want to address bugs whose reporter is no longer here? The reporter is surely not the only person infected. Why wouldn't you want future Konsole developers to find those bugs and potentially address them? Why would you want to close your eyes and pretend that the bug doesn't exist, rather than actually fixing it?
But most importantly, your current workflow is utterly unfair and disrespectful.
... and me submitting a comment doesn't even automatically set back the bug's state to... to what state exactly do _I_ have to _manually_ set it back, to make sure it doesn't fall through the cracks? (In reply to Egmont Koblinger from comment #3) > > would you be interested in submitting a patch > > No, sorry, not. > > > Let me tell you: I'm honestly disappointed in the attitude I'm seeing in > bulk nowadays from Konsole's bugtracker. > > > First, I don't understand why this question justified the NEEDINFO state. > You do not _need_ information from me. You could just go ahead and fix this > bug. > My apologies, I accidentally selected the wrong status for this bug report. > There are situations that justify NEEDINFO, e.g. when you cannot reproduce > the bug, or don't understand what the reporter says. Apparently this is not > the case here. You are not blocked in any way. > > > Second, this Janitor bot auto-closing bugs. > > You, dear KDE developers, often leave a bug unanswered for _years_. You even > leave _patches_ lying around for years without commenting on them. I > understand, you are all humans, you have finite capacity, you probably all > volunteer to do this. I also used to walk in these shoes for a long time, > and probably will do again. > > But you really should not combine this with giving 45 days for OP to > respond. There are hundreds of reasons why the poster does not respond > within this time frame, none of those make the bugreport any less accurate. > > > You should seriously reconsider your workflow. > > The current one hardly leads to better quality software in the long run. > After all, why wouldn't you want to address bugs whose reporter is no longer > here? The reporter is surely not the only person infected. Why wouldn't you > want future Konsole developers to find those bugs and potentially address > them? Why would you want to close your eyes and pretend that the bug doesn't > exist, rather than actually fixing it? Please let me assure you, we are all striving towards better quality software at KDE. We use these products on a daily basis and so are also invested in making sure they are of the highest quality. > But most importantly, your current workflow is utterly unfair and > disrespectful. I'm sorry you feel this way, no disrespect was meant at all. (In reply to Egmont Koblinger from comment #4) > ... and me submitting a comment doesn't even automatically set back the > bug's state to... to what state exactly do _I_ have to _manually_ set it > back, to make sure it doesn't fall through the cracks? Unfortunately this is a limitation in Bugzilla. Many discussions have been taking place recently around moving to a more flexible solution with better workflows. If you can confirm this bug is still plaguing Konsole please change the status to CONFIRMED, then a developer will take a look at the issue and work towards a possible solution. Thanks a lot for the clarification, Justin! Since I'm the original reporter, I don't think it would be fair for me to CONFIRM my own bug, would it? I'd leave this up to you guys. Fair enough, I'm happy to mark is as confirmed as it's affected you through multiple iterations of the application. |