From: prj@po.cwru.edu (Paul Jarc)
Subject: Re: gnus-summary-toggle-header fails for body-less, boundary-less articles
Date: Tue, 19 Feb 2002 15:33:42 -0500 [thread overview]
Message-ID: <m3y9hpgqir.fsf@multivac.cwru.edu> (raw)
In-Reply-To: <2neljhp6cg.fsf@zsh.cs.rochester.edu> (ShengHuo ZHU's message of "Tue, 19 Feb 2002 15:25:03 -0500")
ShengHuo ZHU <zsh@cs.rochester.edu> wrote:
> prj@po.cwru.edu (Paul Jarc) writes:
>> For an article which has no body and no empty line marking the end of
>> the header, gnus-summary-toggle-header fails in two ways.
...
> Does the attached patch fix the problem?
I committed a different version with the same behavior which I'd
already written. I just wasn't sure if this behavior was correct, but
I guess we'll hear about it if it isn't.
paul
next prev parent reply other threads:[~2002-02-19 20:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-19 19:28 Paul Jarc
2002-02-19 20:25 ` ShengHuo ZHU
2002-02-19 20:25 ` ShengHuo ZHU
2002-02-19 20:33 ` Paul Jarc
2002-02-19 20:33 ` Paul Jarc [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-02-19 19:28 Paul Jarc
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=m3y9hpgqir.fsf@multivac.cwru.edu \
--to=prj@po.cwru.edu \
/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).