Gnus development mailing list
 help / color / mirror / Atom feed
From: paul stevenson <spaul@mail.phy.ornl.gov>
Subject: displaying message/rfc822 inline (patch included)
Date: 27 Feb 1999 13:50:25 -0500	[thread overview]
Message-ID: <m3u2w7llzi.relay@the003.phy.ornl.gov> (raw)

When displaying an article with a MIME-included message (like a forward,
say). The article may be displayed inline (Content-Disposition:
inline). In this case pressing 't' to expand the headers only expands
the headers of the article, not the included message. This is how it
should be, I think. However subsequent pressing of 't' gets fooled by
the fact there are still hidden headers in the buffer (belonging to the
included message) and doesn't think it needs to hide them.

The following patch fixes this by narrowing to the article's headers
when checking for hidden header lines. 

(this leaves the question of how to examine the headers of the included
message more neatly than C-u g)

*** gnus-sum.el.orig	Sat Feb 27 13:41:26 1999
--- gnus-sum.el	Sat Feb 27 13:41:30 1999
***************
*** 7029,7037 ****
      (save-restriction
        (let* ((buffer-read-only nil)
  	     (inhibit-point-motion-hooks t)
! 	     (hidden (gnus-article-hidden-text-p 'headers))
  	     e)
  	(goto-char (point-min))
  	(when (search-forward "\n\n" nil t)
  	  (delete-region (point-min) (1- (point))))
  	(goto-char (point-min))
--- 7029,7042 ----
      (save-restriction
        (let* ((buffer-read-only nil)
  	     (inhibit-point-motion-hooks t)
! 	     (hidden)
  	     e)
  	(goto-char (point-min))
+ 	(when (search-forward "\n\n" nil t)
+ 	  (save-restriction 
+ 	    (narrow-to-region (point-min) (point))
+ 	    (setq hidden (gnus-article-hidden-text-p 'headers)))
+ 	  (goto-char (point-min)))
  	(when (search-forward "\n\n" nil t)
  	  (delete-region (point-min) (1- (point))))
  	(goto-char (point-min))


                 reply	other threads:[~1999-02-27 18:50 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=m3u2w7llzi.relay@the003.phy.ornl.gov \
    --to=spaul@mail.phy.ornl.gov \
    /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).