https://bugs.kde.org/show_bug.cgi?id=439529
Kurt Hindenburg changed:
What|Removed |Added
Version Fixed In||21.08
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=439529
Kurt Hindenburg changed:
What|Removed |Added
Resolution|--- |FIXED
Latest Commit|
https://bugs.kde.org/show_bug.cgi?id=439529
Ahmad Samir changed:
What|Removed |Added
CC||bharadwaj.raju777@protonmai
|
https://bugs.kde.org/show_bug.cgi?id=439529
Nate Graham changed:
What|Removed |Added
CC||n...@kde.org
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=439529
--- Comment #5 from ninj...@gmail.com ---
As for the reason setTerminalDisplay was being called in various places in the
code, Vt102Emulation::sendKeyEvent() uses it to know if the session is
read-only, and to call TerminalDisplay::scrollScreenWindow().
https://bugs.kde.org/show_bug.cgi?id=439529
Bug Janitor Service changed:
What|Removed |Added
Ever confirmed|0 |1
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=439529
--- Comment #3 from ninj...@gmail.com ---
Moving the mouse shouldn't be a problem for reproducing the problem, as long as
there are no button presses or wheel movement.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=439529
--- Comment #2 from Ahmad Samir ---
I've created https://invent.kde.org/utilities/konsole/-/merge_requests/433
I don't see why setTerminalDisplay was being called in various places in the
code, there is a reason, I just don't see it...
--
You are
https://bugs.kde.org/show_bug.cgi?id=439529
Ahmad Samir changed:
What|Removed |Added
CC||a.samir...@gmail.com
--- Comment #1 from Ahmad
