GNU bug report logs -
#35899
26.1; move-beginning-of-line sometimes does not move to beginning of line
Previous Next
Reported by: Markus Triska <triska <at> metalevel.at>
Date: Sat, 25 May 2019 13:45:02 UTC
Severity: normal
Tags: fixed, patch
Found in version 26.1
Fixed in version 28.1
Done: Lars Ingebrigtsen <larsi <at> gnus.org>
Bug is archived. No further changes may be made.
Full log
Message #14 received at 35899 <at> debbugs.gnu.org (full text, mbox):
> From: Noam Postavsky <npostavs <at> gmail.com>
> Cc: Markus Triska <triska <at> metalevel.at>, 35899 <at> debbugs.gnu.org
> Date: Fri, 21 Jun 2019 06:05:22 -0400
>
> >> (If there’s an image in the line, this disregards newlines
> >> which are part of the text that the image rests on.)
> >>
> >> Hence, I expect this to move to position 1. For comparison, when I press
> >> C-a, it does move to position 1, as expected.
> >
> > "the text that the image rests on" refers to the text which is
> > "covered" by the display property, not the newlines in the binary data
> > that constitutes the image file's data.
>
> If I create an image which rests on some newlines like this:
>
> (let ((img (create-image "bug-35899-hello.png")))
> (insert "abc")
> (insert-image img "foo\nbar\nbaz")
> (insert "def"))
>
> Then with point after "def", move-beginning-of-line stops "inside" the
> image. And I don't see anything in its code which would allow it to
> skip the image. Isn't this just a doc bug?
Sorry, I don't understand the scenario, or cannot reproduce it. For
starters, there's no bug-35899-hello.png, but I guess any image will
do, so I used splash.png. But then (move-beginning-of-line nil) moves
to the beginning of "def", which is not inside the image. What did I
miss?
This bug report was last modified 4 years and 275 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.