https://bugs.documentfoundation.org/show_bug.cgi?id=170942
yarma22 <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |UNCONFIRMED Ever confirmed|1 |0 --- Comment #3 from yarma22 <[email protected]> --- Hi Olivier, thanks for taking the time to review this. > The fact that the cursor is at end of line or beginning of next line is > actually the same logical position in the text. Actually, in the example I provided, pressing `End` then `Home` when the cursor is on a long line moves the cursor to the beginning of the __next__ line, when it should actually move it at the beginning of the __current__ line. > Adding or deleting text from the cursor position will not change the line > contents. In the case I describe, adding/deleting text will alter the __wrong__ line. > Please show an actual use case of these long lines, not an exercise. Beware > that for what it worth, it will be a corner case for text processor, usually > addressed with other tools or techniques. The most common use-case is a line that contains a long URL. See the "Lorem Ipsum example to illustrate the split URL bugs (for bugs #6, #7, #8 and #9)" test file I attached to the parent bug 169477: https://bugs.documentfoundation.org/attachment.cgi?id=204128 Pressing `End` then `Home` when the cursor is on the __first__ line of the URL will move the cursor to the beginning of the __second__ line of the URL, when it should actually move to the beginning of the __first__ line of the URL. I know these seem like corner cases, but I actually heavily rely on simulating key press on `End` and `Home` in some macros—e.g. to select the text of the current line. Since these "long" lines behave differently, this completely breaks the macros. -- You are receiving this mail because: You are the assignee for the bug.
