From: Katsumi Yamaoka <yamaoka@jpl.org>
To: ding@gnus.org
Subject: Re: gnus-shr-put-image: Wrong number of arguments
Date: Wed, 17 Jul 2013 08:36:09 +0900 [thread overview]
Message-ID: <b4mvc4at6vq.fsf@jpl.org> (raw)
In-Reply-To: <87vc4anwc3.fsf@micropit.couberia.selfip.net>
Peter Münster wrote:
> User-Agent: Gnus/612.570008 (真 Gnus v0.8) Emacs/24.2 (gnu/linux)
^^^^^^^^^^
There might be something bad in your Gnus installation. ;)
> I got a message, that could not be displayed. Instead, I got this
> message:
> gnus-shr-put-image: Wrong number of arguments: #[(data alt)
> ...binary... [image alt
> display-graphic-p nil (shr-rescale-image data) ((error)) 0 image-size
> t 400 ...] 5 ("/usr/share/emacs/24.2/lisp/gnus/shr.elc" . 13300)], 3
If that shr.elc is that of Emacs 24.2, it cannot be used with
the most recent 真 Gnus, since the arguments spec of
`gnus-shr-put-image' was changed afterward. (Emacs 24.2 was
released at 2012-08-24. The change in question was done at
2012-02-01 in 真 Gnus, but it was not merged to Emacs 24.2.)
Moreover, shr.el and also shr-color.el and eww.el was moved from
真 Gnus to the Emacs Bzr trunk (a.k.a. Emacs 24.3.50) at 2013-06-23.
So, if you wish to keep keeping track of 真 Gnus, the best way
will be to use the Emacs trunk. I don't think we should have a
copy of those modules in 真 Gnus.
> Here the message: http://pmrb.free.fr/tmp/shr-problem.txt
No problem here.
next prev parent reply other threads:[~2013-07-16 23:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-16 19:22 Peter Münster
2013-07-16 23:36 ` Katsumi Yamaoka [this message]
2013-07-17 2:42 ` Dave Goldberg
2013-07-17 4:48 ` Katsumi Yamaoka
2013-07-18 3:46 ` Dave Goldberg
2013-07-18 10:04 ` Peter Münster
2013-07-18 11:03 ` Katsumi Yamaoka
2013-07-18 11:30 ` Katsumi Yamaoka
2013-07-19 11:25 ` Dave Goldberg
2013-07-18 10:01 ` Peter Münster
2013-07-18 11:03 ` Katsumi Yamaoka
2013-07-18 11:49 ` Peter Münster
2013-07-19 9:11 ` Katsumi Yamaoka
2013-07-19 14:16 ` Andreas Schwab
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=b4mvc4at6vq.fsf@jpl.org \
--to=yamaoka@jpl.org \
--cc=ding@gnus.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.
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 NNTP newsgroup(s).