From: Katsumi Yamaoka <yamaoka@jpl.org>
To: Stephen Berman <Stephen.Berman@gmx.net>
Cc: emacs-pretest-bug@gnu.org, ding@gnus.org, emacs-devel@gnu.org
Subject: Re: 23.0.60; Gnus gives wrong-type-argument with text/HTML
Date: Sat, 09 Feb 2008 20:09:48 +0900 [thread overview]
Message-ID: <b4mr6fmpern.fsf@jpl.org> (raw)
In-Reply-To: <87prv79g7v.fsf@escher.local.home>
>>>>> Stephen Berman <Stephen.Berman@gmx.net> wrote:
> results in "require: Wrong type argument: arrayp, nil".
Please try rebuilding emacs-w3m using the latest Emacs CVS.
Cf. http://article.gmane.org/gmane.emacs.w3m/7355
next prev parent reply other threads:[~2008-02-09 11:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <873as3boc9.fsf@escher.local.home>
2008-02-08 18:02 ` Reiner Steib
2008-02-08 21:47 ` Stephen Berman
2008-02-08 23:01 ` Reiner Steib
2008-02-08 23:32 ` Stephen Berman
2008-02-09 11:09 ` Katsumi Yamaoka [this message]
2008-02-11 14:47 ` Stephen Berman
2008-02-12 23:57 ` [emacs-w3m:10006] " 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b4mr6fmpern.fsf@jpl.org \
--to=yamaoka@jpl.org \
--cc=Stephen.Berman@gmx.net \
--cc=ding@gnus.org \
--cc=emacs-devel@gnu.org \
--cc=emacs-pretest-bug@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.
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).