From: prj@po.cwru.edu (Paul Jarc)
Subject: gnus-summary-toggle-header fails for body-less, boundary-less articles
Date: Tue, 19 Feb 2002 14:28:02 -0500 [thread overview]
Message-ID: <a4u93c$1io$1@quimby2.netfonds.no> (raw)
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. This line
finds the character position before the end of the buffer, instead of
the one at the end:
(setq e (1- (or (search-forward "\n\n" nil t) (point-max))))
This is easy enough to fix:
(setq e (search-forward "\n\n" nil t)
e (if e (1- e) (point-max)))
But it also fails to delete the header, so the added header:
(when (search-forward "\n\n" nil t)
(delete-region (point-min) (1- (point))))
This doesn't try to do anything for the no-boundary case, so I'm
wondering if that's intentional. Anyone know? Or should it just
delete all the way to (point-max) in this case?
paul
next reply other threads:[~2002-02-19 19:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-19 19:28 Paul Jarc [this message]
-- strict thread matches above, loose matches on Subject: below --
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
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='a4u93c$1io$1@quimby2.netfonds.no' \
--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).