Re: Something is rotten with end-of-line and move-end-of-line

[David Kastrup <dak@gnu.org>]

lorentey@elte.hu (Lőrentey Károly) writes:

> Thus, the current behaviour is clearly broken.  It is not clear,
> however, what C-a/C-e is supposed to do when point is on a field
> boundary.
>
> * * *
>
> Meanwhile, I found an archived discussion thread which explains the
> intended difference between the two flavours:
>
> 	http://thread.gmane.org/gmane.emacs.devel/34012
>
>         From: Kim F. Storm
>         Subject: move-beginning-of-line
>         Date: 2005-03-01 23:01:16 GMT
> 	Message-ID: <m3fyzfm0n7.fsf@kfs-l.imdomain.dk>
>
> There is a test case given in the discussion that demonstrates the
> original problem:
>
> 	(progn
> 	 (insert "\nab")
> 	 (insert-image-file "../etc/splash.xpm")
> 	 (move-end-of-line 1) 
> 	 (insert "def\n"))
>
> move-b/e-of-line move across the image to the line ending that
> corresponds to what is displayed on the screen, while the builtin
> b/e-of-line variants stop at the hidden newlines embedded in the image
> file.

Correct me if I am wrong, but we move point away from invisible areas
anyway in the keyboard input loop, so there is no necessity to let
move-end-of-line do the deed explicitly in order to get
user-comprehensible behavior, right?

> Funnily enough, on closer inspection the doc string do indicate this
> difference:
>
> ,----[ C-h f move-beginning-of-line RET
> | Move point to beginning of current display line.
> |                                    ^^^^^^^
> `----
>
> ,----[ C-h f beginning-of-line RET
> | Move point to beginning of current line.
> `----
>
> Obviously this needs to be elaborated.

Oh wow.  You can say that again.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum