From: Katsumi Yamaoka <yamaoka@jpl.org>
Subject: Re: Changes in article-hide-headers break mml-preview
Date: Wed, 09 Jun 2004 07:54:50 +0900 [thread overview]
Message-ID: <b9ypt891wzp.fsf@jpl.org> (raw)
In-Reply-To: <v9pt8ajgfo.fsf@marauder.physik.uni-ulm.de>
Fixed. The error arose when gnus-single-article-buffer is nil.
>>>>> In <v9pt8ajgfo.fsf@marauder.physik.uni-ulm.de>
>>>>> Reiner Steib <4.uce.03.r.s@nurfuerspam.de> wrote:
> On Tue, Jun 08 2004, Katsumi Yamaoka wrote:
>>>>>>> Reiner Steib <4.uce.03.r.s@nurfuerspam.de> wrote:
>>> In my configuration, your changes in article-hide-headers break
>>> mml-preview. edebugging `article-hide-headers' I get...
>>
>>> edebug-signal:
>>> Buffer is read-only: #<buffer *Article nndraft:drafts*>
[...]
> I also use a simple `M-x mml-preview' from the message buffer. But in
> my message buffer, `gnus-article-buffer' is "*Article nndraft:drafts*"
> so (set-buffer gnus-article-buffer) changes to this buffer instead of
> the "*MIME preview of ...*" buffer.
mml-preview sets gnus-article-buffer as "*MIME preview of...*",
however it is set again as "*Article method:group*" in the
existing summary buffer if gnus-single-article-buffer is nil.
>> P.S. I must go home right now, but I will fix it tomorrow...
> Don't worry about it; I'll just use the old defun until you have time
> to fix the problem.
Thanks. I have noticed it in the train to home. :)
--
Katsumi Yamaoka <yamaoka@jpl.org>
next prev parent reply other threads:[~2004-06-08 22:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1BW8iw-0002JZ-00@quimby.gnus.org>
2004-06-08 12:06 ` Changes in article-hide-headers break mml-preview (was: Changes committed gnus/lisp (ChangeLog gnus-art.el)) Reiner Steib
2004-06-08 13:19 ` Changes in article-hide-headers break mml-preview Katsumi Yamaoka
2004-06-08 14:02 ` Reiner Steib
2004-06-08 22:54 ` Katsumi Yamaoka [this message]
2004-06-09 10:07 ` Reiner Steib
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=b9ypt891wzp.fsf@jpl.org \
--to=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.
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).