Bug 355296 - eportiing to the clipboard shows strange icon after copying into kate
Summary: eportiing to the clipboard shows strange icon after copying into kate
Status: CLOSED NOT A BUG
Alias: None
Product: KEXI
Classification: Applications
Component: Migration/Import/Export (show other bugs)
Version: 2.9.9
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Kexi Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-11-13 15:46 UTC by Albrecht Will
Modified: 2015-11-16 07:18 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
eport into clipboard (37.61 KB, image/png)
2015-11-13 15:46 UTC, Albrecht Will 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Albrecht Will 2015-11-13 15:46:26 UTC 
I exported some rows of a query to the clipboard and inserted the contents into kate. In the right corner appears an unknown icon.

I will upload a screenshot

Reproducible: Always
Comment 1 Albrecht Will 2015-11-13 15:46:58 UTC 
Created attachment 95481 [details]
eport into clipboard
Comment 2 Albrecht Will 2015-11-14 13:46:23 UTC 
Its no bug by kexi but kate!
Sorry
Comment 3 Jarosław Staniek 2015-11-15 22:54:17 UTC 
@Albrecht This is a Scrollbar Minimap feature of Kate - https://docs.kde.org/trunk5/en/applications/katepart/kate-part-scrollbar-minimap.html

Can we close this bug as invalid?
Comment 4 Albrecht Will 2015-11-16 07:06:12 UTC 
Am Sunday 15 November 2015, 22:54:17 schrieben Sie:
> https://bugs.kde.org/show_bug.cgi?id=355296
> 
> Jarosław Staniek <staniek@kde.org> changed:
> 
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
> CC|                            |staniek@kde.org
> 
> --- Comment #3 from Jarosław Staniek <staniek@kde.org> ---
> @Albrecht This is a Scrollbar Minimap feature of Kate -
> https://docs.kde.org/trunk5/en/applications/katepart/kate-part-scrollbar-min
> imap.html
> 
> Can we close this bug as invalid?

Yes.
Albrecht