Bug 351453

Summary: "Mark set" notifier will not go away, spams screen when scrolling
Product: [Applications] kate Reporter: missive
Component: generalAssignee: KWrite Developers <kwrite-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal CC: christoph, mail
Priority: NOR    
Version First Reported In: 5.0.0   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description missive 2015-08-18 17:08:15 UTC
Setting a bookmark pops up a small notification button near the bottom right of the screen -- "Mark set: a"

That notification button never disappears, and when I scroll the screen it leaves a trail of copies smeared across the screen.

Just noticed this:

on my regular x-windows system, the button and the smeared copies do eventually fade and disappear;

on my remote x-windows system, the button and the smeared copies never disappear.


Reproducible: Always

Steps to Reproduce:
1. Open a file longer than a single screen
2. Create a bookmark (ctrl-b)
3. Scroll the window


Actual Results:  
"Mark set:" notifier appears
When the window is scrolled, the button smears multiple copies up/down the screen

Expected Results:  
"Mark set" notifier disappears quickly and does not spam the screen,


Ideally for me, the "Mark set" notifier could be disabled completely.

There is already a color change to the line that is being bookmarked which is plenty of notification that the bookmark has been made.
Comment 1 Sven Brauch 2015-10-08 21:16:53 UTC
The notification now only appears when vi mode is on, otherwise it doesn't make sense. The actual bug is still valid, though.
Comment 2 Christoph Cullmann 2015-10-09 14:16:07 UTC
The graphics issue is a driver problem, we can't fix that in kate.
That they are shown in non-vi mode is fixed now, thanks to Sven, more we can't do.
Comment 3 Dominik Haumann 2016-06-15 16:17:24 UTC
Finally we found a proper fix for this, with KTextEditor in upcoming KDE Frameworks 5.24 release. Sorry for the inconvenience.

*** This bug has been marked as a duplicate of bug 363220 ***