GNU bug report logs - #35899
26.1; move-beginning-of-line sometimes does not move to beginning of line

Previous Next

Full log

Message #17 received at 35899 <at> debbugs.gnu.org (full text, mbox):

From: Noam Postavsky <npostavs <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 35899 <at> debbugs.gnu.org, triska <at> metalevel.at
Subject: Re: bug#35899: 26.1;
 move-beginning-of-line sometimes does not move to beginning of line
Date: Sat, 22 Jun 2019 18:54:00 -0400

Eli Zaretskii <eliz <at> gnu.org> writes:

> For starters, there's no bug-35899-hello.png, but I guess any image will do,

Sorry, I meant the "hello.png" attached to the OP (I tend to give
bug-specific names locally), but indeed 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?

Hmm, something a bit funny here: M-x move-beginning-of-line and M-:
(move-beginning-of-line nil) go to the beginning of "def", but C-a
(which is bound to move-beginning-of-line) goes onto the image (same as
C-4 C-b).  I guess the switch to minibuffer affects things somehow?

But neither of these behaviours seems to be "disregarding" the newlines
that the "image rests on", i.e., it's different from what happens
without the newlines:

(let ((img (create-image "splash.png")))
  (insert "abc")
  (insert-image img "foo bar baz")
  (insert "def"))

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.