From: Eli Zaretskii <eliz@gnu.org>
To: Tassilo Horn <tsdh@gnu.org>
Cc: 13887@debbugs.gnu.org, esabof@gmail.com
Subject: bug#13887: 24.3; doc-view will render blurry images when image-magick is available
Date: Mon, 11 Mar 2013 20:45:39 +0200 [thread overview]
Message-ID: <831ubllqr0.fsf@gnu.org> (raw)
In-Reply-To: <87txohx0g0.fsf@thinkpad.tsdh.de>
> From: Tassilo Horn <tsdh@gnu.org>
> Cc: esabof@gmail.com, monnier@iro.umontreal.ca, 13887@debbugs.gnu.org
> Date: Mon, 11 Mar 2013 19:20:47 +0100
>
> > doc-view-new-window-function seems to be run from a
> > window-configuration-change-hook, right?
>
> No, from `image-mode-new-window-functions'. The functions in there are
> run by `image-mode-winprops' if (and only if) there are no winprops set
> for the image and the current window.
Maybe I'm missing something, but in image-mode.el:
. image-mode-winprops is called by image-mode-reapply-winprops
. image-mode-reapply-winprops is added by image-mode-setup-winprops
to window-configuration-change-hook
Doesn't that mean what I said?
> Basically, this should only ever happen when there's a new window
> showing the buffer with the image.
How's that ensured? Can you walk us through the relevant code?
next prev parent reply other threads:[~2013-03-11 18:45 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-06 3:40 bug#13887: 24.3; doc-view will render blurry images when image-magick is available E Sabof
2013-03-06 8:05 ` Tassilo Horn
2013-03-06 12:13 ` E Sabof
2013-03-06 13:01 ` Tassilo Horn
2013-03-06 14:19 ` E Sabof
2013-03-06 19:43 ` Tassilo Horn
2013-03-07 15:17 ` E Sabof
2013-03-07 15:55 ` Tassilo Horn
2013-03-07 16:15 ` E Sabof
2013-03-07 22:57 ` E Sabof
2013-03-08 7:57 ` Tassilo Horn
[not found] ` <CAEp6DybMJkagHjRaXPiA_ED_dntOk=5USr+P9DfqRPZ_JrrKww@mail.gmail.com>
2013-03-09 7:25 ` bug#13887: Fwd: " E Sabof
2013-03-09 7:26 ` E Sabof
2013-03-11 9:11 ` Tassilo Horn
2013-03-11 16:57 ` Eli Zaretskii
2013-03-11 18:20 ` Tassilo Horn
2013-03-11 18:45 ` Eli Zaretskii [this message]
2013-03-11 20:27 ` Tassilo Horn
2013-03-11 20:59 ` Eli Zaretskii
2013-03-11 22:08 ` E Sabof
2013-03-11 23:41 ` E Sabof
2013-03-12 1:00 ` E Sabof
2013-03-12 8:09 ` Tassilo Horn
2013-03-12 16:50 ` Eli Zaretskii
2013-03-12 18:00 ` Tassilo Horn
2013-03-12 16:52 ` Eli Zaretskii
2013-03-12 17:46 ` E Sabof
2013-03-12 21:11 ` Eli Zaretskii
2013-03-14 3:28 ` E Sabof
2013-03-14 3:56 ` E Sabof
2013-03-14 7:24 ` Tassilo Horn
2013-03-14 15:23 ` E Sabof
2013-03-14 16:48 ` Tassilo Horn
2013-03-14 21:42 ` Tassilo Horn
2013-03-15 1:11 ` E Sabof
2013-03-15 12:52 ` Stefan Monnier
2013-03-15 13:34 ` E Sabof
2013-03-15 17:51 ` Stefan Monnier
2013-03-15 23:26 ` E Sabof
2013-03-16 13:41 ` Stefan Monnier
2013-03-16 23:30 ` E Sabof
2013-03-15 13:55 ` Tassilo Horn
2013-03-15 14:08 ` E Sabof
2013-03-20 15:58 ` E Sabof
2019-09-26 17:16 ` Lars Ingebrigtsen
2019-10-14 6:04 ` Lars Ingebrigtsen
2013-03-14 13:26 ` Stefan Monnier
2013-03-14 15:30 ` Tassilo Horn
2013-03-14 15:53 ` E Sabof
2013-03-14 16:19 ` Stefan Monnier
2013-03-06 18:16 ` Stefan Monnier
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=831ubllqr0.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=13887@debbugs.gnu.org \
--cc=esabof@gmail.com \
--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).