Summary: | Highlighted text behaves strangely. | ||
---|---|---|---|
Product: | [Applications] kate | Reporter: | Georgiy Treyvus <georgiytreyvus> |
Component: | general | Assignee: | KWrite Developers <kwrite-bugs-null> |
Status: | RESOLVED DUPLICATE | ||
Severity: | minor | CC: | cfeck, cullmann |
Priority: | NOR | ||
Version: | 3.10.5 | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Georgiy Treyvus
2013-08-23 22:44:26 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. 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. @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. 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 ;) > 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. *** This bug has been marked as a duplicate of bug 354696 *** |