Entering forwards with C-d

Entering forwards with C-d

[Robert Bihlmeyer]

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

Re: Entering forwards with C-d

[Lars Magne Ingebrigtsen]

Robert Bihlmeyer <robbe@orcus.priv.at> writes:

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

Well, Gnus isn't really (yet) a MIME-aware reader, so these things
don't quite work (yet).

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen

Gnus and MIME

[Matt Armstrong]

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> Well, Gnus isn't really (yet) a MIME-aware reader, so these things
> don't quite work (yet).

Is MIME-awareness in Gnus happening sooner or later?

I ask because I'm wondering whether I want to tackle getting tm to
work on WinNT.  Nobody has yet done a complete port of tm to NT Emacs.


-- 
matta

Re: Gnus and MIME

[Lars Magne Ingebrigtsen]

Matt Armstrong <matta@geoworks.com> writes:

> Is MIME-awareness in Gnus happening sooner or later?

Sooner.  It's the Next Thing I'm going to do.  Perhaps I can use
rmime.el+TM as as starting point.  Dunno.

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen

Re: Gnus and MIME

[Per Abrahamsen]

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> Sooner.  It's the Next Thing I'm going to do.  Perhaps I can use
> rmime.el+TM as as starting point.  Dunno.

I hope you will work together with wmperry to make sure it is usable
in both Gnus and W3.  His mm.el contains some good code as well.

Re: Gnus and MIME

[Lars Magne Ingebrigtsen]

Per Abrahamsen <abraham@dina.kvl.dk> writes:

> > Sooner.  It's the Next Thing I'm going to do.  Perhaps I can use
> > rmime.el+TM as as starting point.  Dunno.
> 
> I hope you will work together with wmperry to make sure it is usable
> in both Gnus and W3.  His mm.el contains some good code as well.

Yup; I'll look into that one as well.

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen

Re: Gnus and MIME

[William M. Perry]

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> Per Abrahamsen <abraham@dina.kvl.dk> writes:
> 
> > > Sooner.  It's the Next Thing I'm going to do.  Perhaps I can use
> > > rmime.el+TM as as starting point.  Dunno.
> > 
> > I hope you will work together with wmperry to make sure it is usable
> > in both Gnus and W3.  His mm.el contains some good code as well.
> 
> Yup; I'll look into that one as well.

  Let me know when you start... I've been keeping my head down lately
because I just relocated to indiana to be near my mother while she dukes it 
out with cancer, and am still in the midst of getting settled, getting my
remote office set up, etc.  So my email-digesting and freeware-coding time
will probably be severely hampered for the next month at least.  I might
not notice if it goes just to the ding list.

-Bill P.

Re: Gnus and MIME

[Nils Goesche]

Matt Armstrong <matta@geoworks.com> writes:

> 
> Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> 
> > Well, Gnus isn't really (yet) a MIME-aware reader, so these things
> > don't quite work (yet).
> 
> Is MIME-awareness in Gnus happening sooner or later?
> 
> I ask because I'm wondering whether I want to tackle getting tm to
> work on WinNT.  Nobody has yet done a complete port of tm to NT Emacs.

Why? I installed tm for xemacs on windows NT. It worked this way:
I unpacked everything, then went to the tm-directory, edited the makefile
so it would use VisualC++ (`cl') as compiler, and typed, from cygnus-bash-
shell, `nmake' and `nmake install'. Everything worked fine, only some paths
were nonsense, so I had to copy around a lot and set some paths, but finally
I got it working without much work. I am using it right now :) öäüßÖÄÜ

-- 
Nils Gösche
My obscure opinions are my very own.

Gnus and Mime

[Ketil Z Malde]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 430 bytes --]


Hi,

just a couple of øre here, but is there any simple way to have W m do
the Mime processing without firing up an xterm to show plain text?
Metamail seems sort of silly for my use - all I want to do is auto-grok
out the occasional word document from messages -- surely I'm not the
only one?

Can't find anything in the faq or net resources...

~kzm
-- 
If I haven't seen further, it is by standing in the footprints of giants

Re: Gnus and Mime

[Kai Grossjohann]

>>>>> Ketil Z Malde writes:

  Ketil> just a couple of øre here, but is there any simple way to
  Ketil> have W m do the Mime processing without firing up an xterm to
  Ketil> show plain text? [...]

Probably it does this for ISO-Latin-1 only.  If this is the case, set
the environment variable MM_CHARSET to iso-8859-1 and be happy 8-)

kai
-- 
Why doesn't the sun come out at night when the light would come in handy?
(Terry Pratchett)

Re: Gnus and Mime

[Steinar Bang]

>>>>> Ketil Z Malde <ketil@imr.no>:

> just a couple of øre here, but is there any simple way to have W m
> do the Mime processing without firing up an xterm to show plain
> text?  Metamail seems sort of silly for my use - all I want to do is
> auto-grok out the occasional word document from messages -- surely
> I'm not the only one?

I've been thinking about merging tm and catdoc, and showing the text
part of an MSWord document MIME message part, inline.

If I could find the time... sometime... 


> Can't find anything in the faq or net resources...

What kind of MIME support are you currently running?

If the answer is none, take a look at 
	<URL:http://bmrc.berkeley.edu/~trey/emacs/mime.html>

I use TM.  I see that you use Xemacs 19.15.  TM comes with Xemacs
19.15.