It's important that keyboard shortcuts for text selection be universally consistent. ⇧+Home/End selects from the current cursor position to the beginning/end of the current line; that shouldn't be overridden here.

However now that I dig into it, I notice that Kate does something similar: the first Home/End press goes to the beginning/end of the current line of a multiline string, but then a second press goes all the way to the beginning/end of the whole multiline string. I think that would be reasonable to do here.

It's about trade off between usability and consistency.
Kate does what it does to be able to select whole, very long line.

Here it can be done in many ways like ctrl+a or shift+Page down/Page up. Changes in this patch were about fine grained selection, getting to the middle of long name faster.

I will remove that part from the diff and leave only bug fix.

I think we may be confusing one another, compounded by the unclear title and summary messages.

https://bugs.kde.org/show_bug.cgi?id=363179 requests that when renaming a file with a long multi-line string, the home/end keys should go to the beginning/end of the whole filename rather than the beginning/end of the line. This should happen whether or not the text is currently selected. That's not the behavior I'm seeing from the patch.

You're welcome, but I think we can probably get some variant of this landed if we put our heads together. :)

The idea is that the home key should always go to the beginning of the filename, and the end key should always go to the end. That's what the bug reporter requested:

When you are renaming such files, you often want to add something to the beginning of file name. But pressing Home button returns cursor to the beginning of last line, not to the beginning of a whole file name.

Steps to Reproduce:

1. Create a file with long name, which will be devided to several lines by dolphin.
2. Select this file and press f2 or choose rename from context menu.
3. Press Home button.
   
   [...]
   
   Expected Results: Cursor should be pointing to start of file name (on first line).

It doesn't matter whether or not the whole filename is currently selected; the keys should always have the same behavior. If you change the patch to do that. I think we can get it into Dolphin.

It doesn't matter whether or not the whole filename is currently selected; the keys should always have the same behavior.

Understood. I don't want to do it because it will brake my usage of End button.

In D20240#444165, @msciubidlo wrote:

It doesn't matter whether or not the whole filename is currently selected; the keys should always have the same behavior.

Understood. I don't want to do it because it will brake my usage of End button.

Well, if you abandon this patch, and I do it myself, then eventually you get broken anyway, right? How about a compromise: we take Kate's behavior and the first press of Home/End goes to the beginning or end of the current line, and then if the cursor is already there, another press moves it all the way to the beginning or end of the whole string. What do you think?

I feel that we are splitting hairs. Do as you think will be best.