Bug 323947 - Highlighted text behaves strangely.
Summary: Highlighted text behaves strangely.
Status: RESOLVED DUPLICATE of bug 354696
Alias: None
Product: kate
Classification: Applications
Component: general (show other bugs)
Version: 3.10.5
Platform: Fedora RPMs Linux
: NOR minor
Target Milestone: ---
Assignee: KWrite Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-08-23 22:44 UTC by Georgiy Treyvus
Modified: 2015-11-04 14:17 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Georgiy Treyvus 2013-08-23 22:44:26 UTC
This bug is very similar to https://bugs.kde.org/show_bug.cgi?id=323946 except instead of the highlighted file name causing its highlighted text in Kate's main textarea widget.

Reproducible: Always
Comment 1 Dominik Haumann 2013-08-26 07:48:27 UTC
I do not understand at all what this is about. Please explain step by step the situation and what you expect, if needed with a screen shot.
Comment 2 Christoph Feck 2013-08-27 10:06:22 UTC
Dominik, I fixed bug 323946 in Dolphin, I think reading the patch makes it clear.

I am, however, not sure if the behavior should be identical in Kate. Maybe it should move the cursor to the begin/end of the selection only for selections that do not span multiple lines.
Comment 3 Georgiy Treyvus 2013-08-27 14:41:50 UTC
@Christoph:

The behaviour you're proposing would be just as bizarre as Kate's current behaviour if not more. Other text editors such as Gedit and Leafpad go to the begin/end of the selection however many lines it spans. Test it out for yourself if you don't believe me. I think it's probably best to give Kate the Geditlike behaviour most people are used to.
Comment 4 Christoph Cullmann 2014-09-22 20:32:34 UTC
I don't get what is wanted here.
Either the reporter describes what should be changed for the selection in detail here, or this is invalid.
Besides, the selection behavior is like it is since long and most people seem to like it, therefore any change is unlikely ;)
Comment 5 Christoph Feck 2014-09-22 21:35:16 UTC
> I don't get what is wanted here.

It is described in detail at bug 323946, but the reporter did not clone the description. But to understand it, reading the commit that fixed it (see comment #2) is probably simpler than reading the description.
Comment 6 Christoph Feck 2015-11-04 14:17:44 UTC

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