unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Lars Magne Ingebrigtsen <larsi@gnus.org>
Cc: 9296-done@debbugs.gnu.org
Subject: bug#9296: 24.0.50; next-line/prev-line on lines with images
Date: Sun, 14 Aug 2011 19:52:32 +0300	[thread overview]
Message-ID: <83wregue9b.fsf@gnu.org> (raw)
In-Reply-To: <m34o1k3wpp.fsf@stories.gnus.org>

> From: Lars Magne Ingebrigtsen <larsi@gnus.org>
> Cc: 9296@debbugs.gnu.org
> Date: Sun, 14 Aug 2011 16:16:02 +0200
> MailScanner-NULL-Check: 1313936207.48825@iYqLddN/OGrzFGkFNPyD2A
> 
> (url-retrieve
>  "http://quimby.gnus.org/circus/jukebox.php?image=thumbnail.png&group=Various&album=Bossa%20Nova%20and%20the%20Rise%20of%20Brazilian%20Music%20in%20the%201960s%20%281%29"
>  (lambda (status)
>    (goto-char (point-min))
>    (search-forward "\n\n")
>    (let ((data (buffer-substring (point) (point-max))))
>      (pop-to-buffer "*image*")
>      (setq truncate-lines t)
>      (let ((image (create-image data 'png t)))
>        (dotimes (i 50)
> 	 (insert-image image)
> 	 (insert " Bossa Nova and the Rise of Brazilian Music in the 1960s (1) -> Various/Bossa Nova and the Rise of Brazilian Music in the 1960s (1)\n"))))))

Thanks for the test case.  This problem exists in Emacs 23 as well, so
it's not new.  I suggest to file a separate bug for it.  For now,
being not worse than Emacs 23.3 is good enough for me.

In general, the DWIM-ish operation of next/previous-line, especially
its ideas of what exactly is the goal column, is darn hard to get
right, and it certainly has its surprises.  If you look at the
convoluted code in move_it_in_display_line_to, you will understand
why.





  parent reply	other threads:[~2011-08-14 16:52 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-13 20:56 bug#9296: 24.0.50; next-line/prev-line on lines with images Lars Ingebrigtsen
2011-08-14  7:17 ` Eli Zaretskii
2011-08-14 11:13   ` Eli Zaretskii
2011-08-14 14:16     ` Lars Magne Ingebrigtsen
2011-08-14 14:19       ` Lars Magne Ingebrigtsen
2011-08-14 16:52       ` Eli Zaretskii [this message]
2011-08-14 17:00         ` Lars Magne Ingebrigtsen
2011-08-14 19:33           ` Eli Zaretskii
2011-08-14 19:37             ` Lars Magne Ingebrigtsen
2011-08-14 20:02               ` Eli Zaretskii
2011-08-14 20:23                 ` Lars Magne Ingebrigtsen
2011-08-14 20:50                   ` Eli Zaretskii
2011-08-14 21:12                     ` Lars Magne Ingebrigtsen
2011-08-15  6:47                       ` Eli Zaretskii
     [not found]                         ` <m362lyvrt6.fsf@stories.gnus.org>
     [not found]                           ` <83aabavq9k.fsf@gnu.org>
2011-08-15 12:06                             ` Lars Magne Ingebrigtsen
2011-08-14 17:10         ` Lars Magne Ingebrigtsen
2011-08-14 19:39           ` Eli Zaretskii
2011-08-14 21:43           ` Johan Bockgård
2011-08-15  6:48             ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83wregue9b.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=9296-done@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).