From: Reiner Steib <4.uce.03.r.s@nurfuerspam.de>
Subject: Bug: gnus-article-treat-body-boundary, gnus-with-article-headers
Date: Wed, 15 Oct 2003 20:55:29 +0200 [thread overview]
Message-ID: <v9y8vm5o0u.fsf@marauder.physik.uni-ulm.de> (raw)
Hi,
when I set `gnus-treat-body-boundary' to t, the boundary isn't placed
after the headers, but after the first paragraph of the article body.
I don't know whether it's a bug in `gnus-article-treat-body-boundary',
`gnus-with-article-headers', `article-narrow-to-head' or something
else. When I add "(sit-for 3)" in `gnus-article-treat-body-boundary'
as shown below, I see that the article buffer doesn't contain the
headers (as expected), but the first paragraph of the article.
Any ideas? (I couldn't locate the code where the gnus-treat-*
functions are called.)
Bye, Reiner.
(defun gnus-article-treat-body-boundary ()
"Place a boundary line at the end of the headers."
(interactive)
(when (and gnus-body-boundary-delimiter
(> (length gnus-body-boundary-delimiter) 0))
(gnus-with-article-headers
(sit-for 3) ;; <============================================== ADDED
(goto-char (point-max))
(let ((start (point)))
(insert "X-Boundary: ")
(gnus-add-text-properties start (point) '(invisible t intangible t))
(insert (let (str)
(while (>= (1- (window-width)) (length str))
(setq str (concat str gnus-body-boundary-delimiter)))
(substring str 0 (1- (window-width))))
"\n")
(gnus-put-text-property start (point) 'gnus-decoration 'header)))))
--
,,,
(o o)
---ooO-(_)-Ooo--- PGP key available via WWW http://rsteib.home.pages.de/
next reply other threads:[~2003-10-15 18:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-15 18:55 Reiner Steib [this message]
2003-10-15 22:08 ` Bug: gnus-article-treat-body-boundary, Karl Pflästerer
2003-10-16 14:31 ` Karl Pflästerer
[not found] ` <hhu16a1358.fsf@blah.pl>
2003-10-16 14:56 ` Reiner Steib
2003-10-17 16:56 ` Lars Magne Ingebrigtsen
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=v9y8vm5o0u.fsf@marauder.physik.uni-ulm.de \
--to=4.uce.03.r.s@nurfuerspam.de \
--cc=reiner.steib@gmx.de \
/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).