Gnus development mailing list
 help / color / mirror / Atom feed
From: Robert Bihlmeyer <robbe@orcus.priv.at>
Subject: Entering forwards with C-d
Date: 03 Feb 1998 13:34:57 +0100	[thread overview]
Message-ID: <wspvl4989a.fsf@orcus.priv.at> (raw)

[-- Attachment #1: Type: text/plain, Size: 725 bytes --]

Hi,

I was made aware, that you could "enter" digests and forwards with C-d 
from the summary buffer.

This does not work with mimified forwards (multipart/mixed with a
message/rfc822 part). Gnus itself produces (with TM, if that matters)
such forwards, so it should probably understand them as well. I fixed
this by adding recognition of "multipart/mixed" as a possible
mime-"digest".

Still, the undigested result did not have the right headers (i.e. mime 
headers instead of rfc822 headers), so I added another line. Now
headers are in the right place, which makes replying to
message/rfc822-parts possible. Sadly, the digest-group-summary still
shows nothing useful (e.g. "[(none)]: (none)").

A patch is below.

	Robbe


[-- Attachment #2: Type: text/plain, Size: 1332 bytes --]

diff -c qgnus/lisp/nndoc.el~ qgnus/lisp/nndoc.el
*** qgnus/lisp/nndoc.el~	Tue Feb  3 13:34:03 1998
--- qgnus/lisp/nndoc.el	Tue Feb  3 13:34:03 1998
***************
*** 465,479 ****
  	boundary-id b-delimiter entry)
      (when (and
  	   (re-search-forward
! 	    (concat "^Content-Type: *multipart/digest;[ \t\n]*[ \t]"
  		    "boundary=\"\\([^\"\n]*[^\" \t\n]\\)\"")
  	    nil t)
! 	   (match-beginning 1))
!       (setq boundary-id (match-string 1)
  	    b-delimiter (concat "\n--" boundary-id "[\n \t]+"))
        (setq entry (assq 'mime-digest nndoc-type-alist))
        (setcdr entry
  	      (list
  	       (cons 'head-end "^ ?$")
  	       (cons 'body-begin "^ ?\n")
  	       (cons 'article-begin b-delimiter)
--- 465,480 ----
  	boundary-id b-delimiter entry)
      (when (and
  	   (re-search-forward
! 	    (concat "^Content-Type: *multipart/\\(digest\\|mixed\\);[ \t\n]*[ \t]"
  		    "boundary=\"\\([^\"\n]*[^\" \t\n]\\)\"")
  	    nil t)
! 	   (match-beginning 2))
!       (setq boundary-id (match-string 2)
  	    b-delimiter (concat "\n--" boundary-id "[\n \t]+"))
        (setq entry (assq 'mime-digest nndoc-type-alist))
        (setcdr entry
  	      (list
+ 	       (cons 'head-begin "^ ?$")
  	       (cons 'head-end "^ ?$")
  	       (cons 'body-begin "^ ?\n")
  	       (cons 'article-begin b-delimiter)

[-- Attachment #3: Type: text/plain, Size: 140 bytes --]


-- 
Robert Bihlmeyer	reads: Deutsch, English, MIME, Latin-1, NO SPAM!
<robbe@orcus.priv.at>	<http://stud2.tuwien.ac.at/~e9426626/sig.html>

             reply	other threads:[~1998-02-03 12:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-02-03 12:34 Robert Bihlmeyer [this message]
1998-02-08 15:58 ` Lars Magne Ingebrigtsen
1998-02-09 19:22   ` Gnus and MIME Matt Armstrong
1998-02-09 20:17     ` Lars Magne Ingebrigtsen
1998-02-10  6:28       ` Per Abrahamsen
1998-02-10 10:18         ` Lars Magne Ingebrigtsen
1998-02-10 14:23           ` William M. Perry
1998-02-10  4:34     ` Nils Goesche

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=wspvl4989a.fsf@orcus.priv.at \
    --to=robbe@orcus.priv.at \
    /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).