Summary: | konsole should have a noblink option | ||
---|---|---|---|
Product: | [Applications] konsole | Reporter: | Unknown <null> |
Component: | general | Assignee: | Konsole Developer <konsole-devel> |
Status: | RESOLVED NOT A BUG | ||
Severity: | wishlist | ||
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Other | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
unununium
2000-12-28 02:45:39 UTC
An additional side effect occurs when anti-aliasing is enabled and a non-solid background or transparency is used... Upon each blink refresh, the text gets repainted and all the text "darkens" on each blink. In other words, the anti-aliased text gets anti-aliased again. The blink refresh is also expensive on remote X sessions. Disregard my previous comment... this issue was fixed/closed in #39804. In konsole 1.3, there is an option under configure for 'Blinking cursor'. I would think this (very old) bug can be closed. No, the original reporter is speaking about blinking text parts not blinking cursor. Replaced unununium@openverse.org with null@kde.org due to bounces by reporter This could be closed, its now 4,5 years old.. I think it is best to close this bug as it is six years old now and the internals have changed hugely since the filing. In particular Konsole is now much more conservative about how much gets repainted - so speed should no longer be an issue. If something relevant comes up again I suggest that a new report should be filed. |