From: David Engster <deng@randomsample.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Thomas Wiecki <thomas.wiecki@gmail.com>, 14567@debbugs.gnu.org
Subject: bug#14567: Scrolling of large images
Date: Tue, 11 Jun 2013 22:14:47 +0200 [thread overview]
Message-ID: <87bo7cpfpk.fsf@engster.org> (raw)
In-Reply-To: <83ehccromw.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 09 Jun 2013 05:42:15 +0300")
Eli Zaretskii writes:
>> I can't really reproduce the line-move error either in this mode. It
>> does show up occasionally but I haven't figured out how to
>> explicitly trigger it thus far.
>
> I'll try reproducing it here.
I also tried the patch on current trunk. I use the following snippet to
generate a buffer containing large and small images as well as text:
(with-current-buffer (get-buffer-create "test")
(erase-buffer)
(let ((imagelarge (create-image "~/someimage.jpg" 'imagemagick nil :height 2000 :width 1000))
(imagesmall (create-image "~/someimage.jpg" 'imagemagick nil :height 200 :width 100)))
(dotimes (i 20)
(insert "\n*** " (number-to-string i)" ***\nThis is a line of text.\nAnd here's a large image:\n")
(insert-image imagelarge)
(insert "\nAnd a small image:\n")
(insert-image imagesmall))
(goto-char (point-min))))
Obviously, replace "~/someimage.jpg" with something else. Also, Emacs
must be compiled with imagemagick support.
Scrolling using your patch looks already pretty good, but I also get the
'wrong-type-argument' error while scrolling down. I use a maximized
'emacs -Q' on a display with 1366x768 resolution, and here's the backtrace:
Debugger entered--Lisp error: (wrong-type-argument number-or-marker-p nil)
line-move-partial(1 nil nil)
line-move(1 nil nil 1)
#[0 "\302\300@\303\211\301$\207" [(1) 1 line-move nil] 5 "\n\n(fn)"]()
funcall(#[0 "\302\300@\303\211\301$\207" [(1) 1 line-move nil] 5 "\n\n(fn)"])
next-line(1 1)
call-interactively(next-line nil nil)
command-execute(next-line)
This happens during scrolling when point should switch from the first
small image to the following text line containing "*** 1 ***". The
second large image is already visible at the bottom. I can do
screenshots or even a screencast if necessary.
-David
next prev parent reply other threads:[~2013-06-11 20:14 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-06 12:17 bug#14567: Scrolling of large images Thomas Wiecki
2013-06-06 16:42 ` Eli Zaretskii
2013-06-06 17:16 ` Thomas Wiecki
2013-06-06 17:32 ` Eli Zaretskii
2013-06-08 14:19 ` Eli Zaretskii
2013-06-08 15:52 ` Thomas Wiecki
2013-06-08 16:49 ` Eli Zaretskii
2013-06-08 17:51 ` Thomas Wiecki
2013-06-08 18:44 ` Eli Zaretskii
2013-06-08 21:39 ` Thomas Wiecki
2013-06-09 2:42 ` Eli Zaretskii
2013-06-09 9:27 ` Vitalie Spinu
2013-06-11 20:14 ` David Engster [this message]
2013-06-15 8:23 ` Eli Zaretskii
2013-06-15 9:02 ` David Engster
2013-06-15 9:39 ` Eli Zaretskii
2013-06-15 10:08 ` David Engster
2013-06-15 11:13 ` Thierry Volpiatto
2013-06-15 11:26 ` Eli Zaretskii
2013-06-15 12:41 ` Eli Zaretskii
2013-06-16 5:33 ` Thierry Volpiatto
2013-06-16 6:18 ` Thierry Volpiatto
2013-06-16 16:24 ` Eli Zaretskii
2013-06-17 4:57 ` Thierry Volpiatto
2013-06-17 15:14 ` Eli Zaretskii
2013-06-18 11:35 ` Thierry Volpiatto
2013-06-18 16:13 ` Eli Zaretskii
2013-06-19 6:43 ` Thierry Volpiatto
2013-07-06 9:02 ` bug#14567: These changes sometimes break plain text navigation Dima Kogan
2013-07-06 11:02 ` Eli Zaretskii
2013-07-06 16:14 ` Dima Kogan
2013-07-06 17:41 ` Eli Zaretskii
2013-07-06 21:51 ` Dima Kogan
2013-07-07 2:48 ` Eli Zaretskii
2013-07-07 4:46 ` Dima Kogan
2013-07-07 15:51 ` Eli Zaretskii
2013-07-07 18:57 ` Dima Kogan
2013-07-08 17:35 ` Eli Zaretskii
2013-07-08 23:42 ` Dima Kogan
2013-07-09 17:00 ` bug#14598: " Eli Zaretskii
2013-07-10 9:30 ` Stephen Berman
2013-07-10 16:27 ` Eli Zaretskii
2013-07-10 21:33 ` Stephen Berman
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=87bo7cpfpk.fsf@engster.org \
--to=deng@randomsample.de \
--cc=14567@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=thomas.wiecki@gmail.com \
/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).