Gnus development mailing list
 help / color / mirror / Atom feed
From: sigurd@12move.de (Karl Pflästerer)
Subject: Re: Bug: gnus-article-treat-body-boundary,
Date: Thu, 16 Oct 2003 00:08:47 +0200	[thread overview]
Message-ID: <m33cdup3lz.fsf@hamster.pflaesterer.de> (raw)
In-Reply-To: <v9y8vm5o0u.fsf@marauder.physik.uni-ulm.de>

On 15 Oct 2003, Reiner Steib <- 4.uce.03.r.s@nurfuerspam.de wrote:

> 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.

Yes that's right.

> 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'

I'm also not sure but I think we should start with `gnus-display-mime'
There `gnus-treat-article' gets called and that function calls the
functions from the alist `gnus-treatment-function-alist'.

> as shown below, I see that the article buffer doesn't contain the
> headers (as expected), but the first paragraph of the article.

That's because of gnus-display-mime.

	  (save-restriction
	    (article-goto-body)
	    (narrow-to-region (point) (point-max))
	    (gnus-treat-article nil 1 1)
	    (widen)))
	(unless ihandles
	  ;; Highlight the headers.
	  (save-excursion
	    (save-restriction
	      (article-goto-body)
	      (narrow-to-region (point-min) (point))
	      (gnus-treat-article 'head))))))))


Before `gnus-treat-article' is called the buffer is narrowed.  I'm not
sure at the moment why but it seems necessary.  If I comment it out
nothing happens.

> Any ideas?  (I couldn't locate the code where the gnus-treat-*
> functions are called.)

Perhaps that helps a bit.  I couldn't find at the monent the bug either
but I'll try on.



   KP

-- 
If you have nothing to say on a subject, replying with a line such as,
"I agree with this." puts you in the TO:'s for all future messages, and
establishes you as "one who really cares", if not an actual expert, on
the topic at hand.         -- from the Symbolics Guidelines for Sending Mail



  reply	other threads:[~2003-10-15 22:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-15 18:55 Bug: gnus-article-treat-body-boundary, gnus-with-article-headers Reiner Steib
2003-10-15 22:08 ` Karl Pflästerer [this message]
2003-10-16 14:31 ` Bug: gnus-article-treat-body-boundary, 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=m33cdup3lz.fsf@hamster.pflaesterer.de \
    --to=sigurd@12move.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).