all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: "Óscar Fuentes" <ofv@wanadoo.es>
Cc: 38176@debbugs.gnu.org
Subject: bug#38176: 27.0.50; pdf-tools images do not display
Date: Sun, 17 Nov 2019 19:25:34 +0100	[thread overview]
Message-ID: <87tv724axt.fsf@gnus.org> (raw)
In-Reply-To: <87ftimzal8.fsf@telefonica.net> ("Óscar Fuentes"'s message of "Sun, 17 Nov 2019 18:17:23 +0100")

Óscar Fuentes <ofv@wanadoo.es> writes:

> As for pdf-tools requirements, you need gcc + automake + autoconf + make
> and some extra libraries. This commands install the libraries in Debian
> and derivatives:
>
> $ sudo apt install libpng-dev zlib1g-dev
> $ sudo apt install libpoppler-glib-dev
> $ sudo apt install libpoppler-private-dev

Thanks; I got it to work now.

The bug is here:

(defun pdf-view-scroll-up-or-next-page (&optional arg)

[...]

        (when (or (= (window-vscroll) (image-scroll-up arg))

It's comparing the output of window-vscroll (which returns the position
in number-of-lines, not pixels) with the return value of
image-scroll-up, which returns a value in pixels.  It's not documented
at all what the latter function is supposed to return, so it looks like
a bug to me that pdf-tools relies on it.

(The function has changed a bit lately, but I didn't trace whether it's
really changed its return value.)

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2019-11-17 18:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-12  6:19 bug#38176: 27.0.50; pdf-tools images do not display Óscar Fuentes
2019-11-14  5:48 ` Lars Ingebrigtsen
2019-11-14  6:02   ` Óscar Fuentes
2019-11-14  6:28     ` Lars Ingebrigtsen
2019-11-17 10:11       ` Lars Ingebrigtsen
2019-11-17 17:17         ` Óscar Fuentes
2019-11-17 18:25           ` Lars Ingebrigtsen [this message]
2019-11-17 18:29             ` Óscar Fuentes
2019-11-17 18:48             ` Eli Zaretskii
2019-11-17 18:54               ` Lars Ingebrigtsen
2019-11-17 19:00                 ` Eli Zaretskii
2019-11-17 19:02               ` Óscar Fuentes

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

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

  git send-email \
    --in-reply-to=87tv724axt.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=38176@debbugs.gnu.org \
    --cc=ofv@wanadoo.es \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.