| Summary: | using Mrxvt - editors like gvim do not have focus when opened, affecting usability | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | Sandeep <sandys> |
| Component: | general | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | Keywords: | investigated, triaged |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Unspecified | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Sandeep
2010-04-10 05:58:51 UTC
What's the difference between "commandline" and Konsole? There are window specific rules to change the focus stealing prevention. Have you tried to create a rule for the window? Does that solve your problem? I can't see any issue here. My fair guess is that when started gvim through Konsole it is a child window to the Konsole window and by that get's the focus. This is the expected and correct behaviour. when I refer to commandline, I mean mrxvt - sorry about the confusion. There are no settings specific to mrxvt or to Konsole that I see. The only difference is that Konsole's window has a role of "MainWindow#1" and mrxvt is blank. I'm not sure if something needs to be set specifically for mrxvt, or if it is a bug in mrxvt itself. Another note is that I launch mrxvt from the panel using a quick launch applet, which has /usr/bin/mrxvt as its command. Is this still an issue? (installed mrxvt 0.5.4, launching emacs or any other application did not expose this) The issue has likely been that mrxvt caused sth. that was considered an activity and updated the timestamp after gvim requested the focus hinting "user types here, don#t steal focus") 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 set the bug status 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! Dear Bug Submitter, 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! |