From: tsugutomo.enami@jp.sony.com
To: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: 18813-done@debbugs.gnu.org
Subject: bug#18813: 25.0.50; gnus start fails unless image.el is loaded in advance.
Date: Mon, 27 Oct 2014 10:57:54 +0900 [thread overview]
Message-ID: <tkrvbn6clzx.fsf@sigxcpu.sm.sony.co.jp> (raw)
In-Reply-To: <b4mbnoy1hm4.fsf@jpl.org> (Katsumi Yamaoka's message of "Mon, 27 Oct 2014 09:28:03 +0900")
Katsumi Yamaoka <yamaoka@jpl.org> writes:
> Well, I have another doubt. Did you mean image.elc is not loaded
> only if the display type is not graphical?
Loading image.el won't fail and it works. I wonder if it is really
necessary to setup image when display is not capable of displaying it.
> Does the error happen in both 24.0.50 (you seem to use) and 25.0.50
> (labeled in the bug subject)?
# 24.0.50 is currentl my main mail environment. As I was asked to
# prepare patch against emacs trunk in bug#18728, I've prepared 25.0.50
# on temporary machine and found this bug#18813 while testing on it.
This bug#18813 doesn't occur on 24.0.50, since image.el is loaded while
gnus-art.el is loaded (gnus-image-type-available-p defined in
gnus-ems.el calls image-type-available-p).
On 25.0.50, tests in gnus-image-type-available-p are reordered and now
control returns before calling image-type-available-p when
display-images-p returns nil (it is in my case). So, image.el is not
loaded.
Hmm, why are they reordered? I guess it is to avoid loading unnecessary
library.
enami.
next prev parent reply other threads:[~2014-10-27 1:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-24 6:32 bug#18813: 25.0.50; gnus start fails unless image.el is loaded in advance enami tsugutomo
2014-10-24 8:35 ` Katsumi Yamaoka
2014-10-26 23:03 ` tsugutomo.enami
2014-10-27 0:28 ` Katsumi Yamaoka
2014-10-27 1:57 ` tsugutomo.enami [this message]
2014-10-27 3:31 ` Katsumi Yamaoka
2014-10-27 3:52 ` Katsumi Yamaoka
2014-10-27 3:41 ` Eli Zaretskii
2014-10-27 3:56 ` Katsumi Yamaoka
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=tkrvbn6clzx.fsf@sigxcpu.sm.sony.co.jp \
--to=tsugutomo.enami@jp.sony.com \
--cc=18813-done@debbugs.gnu.org \
--cc=yamaoka@jpl.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).