From: Eli Zaretskii <eliz@gnu.org>
To: Stephen Berman <stephen.berman@gmx.net>
Cc: 34138@debbugs.gnu.org, politza@hochschule-trier.de, tsdh@gnu.org
Subject: bug#34138: 27.0.50; Delayed display of PDF file images
Date: Wed, 23 Jan 2019 18:26:22 +0200 [thread overview]
Message-ID: <83fttj8hn5.fsf@gnu.org> (raw)
In-Reply-To: <87fttjigx1.fsf@gmx.net> (message from Stephen Berman on Wed, 23 Jan 2019 15:31:54 +0100)
> From: Stephen Berman <stephen.berman@gmx.net>
> Cc: politza@hochschule-trier.de, rudalics@gmx.at, 34138@debbugs.gnu.org, tsdh@gnu.org
> Date: Wed, 23 Jan 2019 15:31:54 +0100
>
> I found that the following patch to pdf-view-goto-page eliminates the
> display of raw PDF and the delay of the image display:
>
> *** /home/steve/.emacs.d/elpa/pdf-tools-20181221.1913/pdf-view.el.orig 2019-01-21 15:56:08.033335212 +0100
> --- /home/steve/.emacs.d/elpa/pdf-tools-20181221.1913/pdf-view.el 2019-01-23 14:54:52.381373638 +0100
> ***************
> *** 624,629 ****
> --- 624,630 ----
> (pdf-view-deactivate-region)
> (force-mode-line-update)
> (run-hooks 'pdf-view-after-change-page-hook))))
> + (switch-to-buffer (current-buffer))
> nil)
>
> (defun pdf-view-next-page (&optional n)
>
> I assume this is only a workaround.
It's a workaround, yes. I believe it works because switching a buffer
causes a more thorough redisplay of the window showing that buffer,
and so the fact that overlay changes in it are not noticed no longer
gets in our way.
next prev parent reply other threads:[~2019-01-23 16:26 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-19 21:13 bug#34138: 27.0.50; Delayed display of PDF file images Stephen Berman
2019-01-20 9:17 ` martin rudalics
2019-01-20 11:04 ` Andreas Politz
2019-01-20 14:19 ` martin rudalics
2019-01-20 11:18 ` Stephen Berman
2019-01-20 14:20 ` martin rudalics
2019-01-20 14:55 ` Stephen Berman
2019-01-20 15:32 ` Eli Zaretskii
2019-01-20 15:51 ` Stephen Berman
2019-01-20 16:08 ` Eli Zaretskii
2019-01-20 16:31 ` Stephen Berman
2019-01-20 16:50 ` Eli Zaretskii
2019-01-20 17:14 ` Stephen Berman
2019-01-20 17:42 ` Eli Zaretskii
2019-01-20 20:45 ` Stephen Berman
2019-01-21 15:58 ` Eli Zaretskii
2019-01-21 16:13 ` Stephen Berman
2019-01-21 16:36 ` Eli Zaretskii
2019-01-21 18:17 ` Stephen Berman
2019-01-21 18:42 ` Eli Zaretskii
2019-01-21 19:14 ` Andreas Politz
2019-01-21 19:47 ` Eli Zaretskii
2019-01-21 22:27 ` Stephen Berman
2019-01-22 16:25 ` Eli Zaretskii
2019-01-22 22:00 ` Stephen Berman
2019-01-23 14:31 ` Stephen Berman
2019-01-23 16:26 ` Eli Zaretskii [this message]
2019-01-23 17:22 ` Stephen Berman
2019-01-23 16:13 ` Eli Zaretskii
2019-01-23 17:21 ` Stephen Berman
2019-01-23 22:20 ` Stephen Berman
2019-01-23 18:27 ` martin rudalics
2019-01-23 18:39 ` Eli Zaretskii
2019-01-24 9:08 ` martin rudalics
2019-01-24 14:26 ` Eli Zaretskii
2019-01-24 19:41 ` Andreas Politz
2019-01-25 9:44 ` martin rudalics
2019-01-26 9:19 ` martin rudalics
2019-01-26 10:52 ` Eli Zaretskii
2019-01-26 15:07 ` martin rudalics
2019-01-26 15:33 ` Stephen Berman
2019-02-02 9:28 ` martin rudalics
2019-02-02 9:38 ` Andreas Politz
2019-02-19 8:47 ` martin rudalics
2019-02-02 12:59 ` Stephen Berman
2019-02-19 8:40 ` martin rudalics
2019-03-30 2:56 ` Noam Postavsky
2019-04-23 9:22 ` martin rudalics
2019-02-02 9:33 ` Andreas Politz
2019-02-02 9:37 ` martin rudalics
2019-01-21 20:33 ` Stephen Berman
2019-01-21 20:35 ` Eli Zaretskii
2019-01-21 20:43 ` Stephen Berman
2019-01-21 21:28 ` Andreas Politz
2019-01-21 18:47 ` martin rudalics
2019-01-21 19:19 ` Andreas Politz
2019-01-21 20:33 ` Stephen Berman
2019-01-20 17:55 ` martin rudalics
2019-01-20 20:45 ` Stephen Berman
2019-01-21 7:52 ` martin rudalics
2019-01-21 15:20 ` Stephen Berman
2019-01-21 6:11 ` Tassilo Horn
2019-01-21 7:52 ` martin rudalics
2019-01-21 15:20 ` 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=83fttj8hn5.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=34138@debbugs.gnu.org \
--cc=politza@hochschule-trier.de \
--cc=stephen.berman@gmx.net \
--cc=tsdh@gnu.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).