From: martin rudalics <rudalics@gmx.at>
To: Andreas Politz <politza@hochschule-trier.de>
Cc: Stephen Berman <stephen.berman@gmx.net>, 34138@debbugs.gnu.org
Subject: bug#34138: 27.0.50; Delayed display of PDF file images
Date: Sun, 20 Jan 2019 15:19:56 +0100 [thread overview]
Message-ID: <5C44838C.8070601@gmx.at> (raw)
In-Reply-To: <87a7jvsi7t.fsf@hochschule-trier.de>
> I can reproduce this: Opening a PDF in the latest Emacs version requires
> an extra redisplay for the image to appear, e.g. by entering the
> minibuffer.
Do you have any idea what might be causing it? Excluding
'display-buffer-split-below-and-attach' it should be related to
'image-mode-new-window-functions'.
>> 'display-buffer-split-below-and-attach' calls 'window--display-buffer'
>> with a fifth argument and that has been changed in another commit.
>
> I really wish this function would be part of the public API. Or else,
> what is the best way to implement a function like
> display-buffer-mark-dedicated ?
It will be public soon. Moreove, application will not have to bother
with ‘display-buffer-mark-dedicated’ any more.
>>> In addition, in pdf-view-mode this appears in *Message*:
>>> Error during redisplay: (eval (pdf-misc-size-indication)) signaled
>>> (error "Invalid image specification: nil").
>>
>> This should come from the 'image-display-size' call in
>> 'pdf-view-image-size'. Could you get a backtrace for it?
>
> Right, the function pdf-misc-size-indication assumes the existence of a
> displayed image in the selected window.
What happened here? Did the image not get displayed or did the
selected window change or get another buffer?
martin
next prev parent reply other threads:[~2019-01-20 14:19 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5C44838C.8070601@gmx.at \
--to=rudalics@gmx.at \
--cc=34138@debbugs.gnu.org \
--cc=politza@hochschule-trier.de \
--cc=stephen.berman@gmx.net \
/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.