From: Shenghuo ZHU <zsh@cs.rochester.edu>
Subject: Re: view message/rfc822 in separate buffer?
Date: 04 May 2000 17:52:58 -0400 [thread overview]
Message-ID: <2nk8haf0ed.fsf@tiger.jia.vnet> (raw)
In-Reply-To: Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "Thu, 4 May 2000 19:03:07 +0200"
>>>>> "KG" == Kai Großjohann <Kai.Grossjohann@CS.Uni-Dortmund.DE> writes:
KG> I now see that this kind of forward (apparently produced by mutt) is
KG> not in nndoc-type-alist.
Fixed. Now, the forward regexps in nndoc.el and mm-uu.el are the
same.
--
Shenghuo
next prev parent reply other threads:[~2000-05-04 21:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-04 15:30 Kai Großjohann
2000-05-04 15:58 ` Steinar Bang
2000-05-04 15:59 ` Toby Speight
2000-05-08 21:46 ` Kai Großjohann
2000-08-12 18:25 ` Lars Magne Ingebrigtsen
2000-05-04 16:00 ` Karl Kleinpaste
2000-05-04 17:03 ` Kai Großjohann
2000-05-04 21:52 ` Shenghuo ZHU [this message]
2000-05-04 23:07 ` Karl Eichwalder
2000-05-05 4:47 ` Shenghuo ZHU
2000-05-05 5:13 ` Karl Eichwalder
2000-05-05 5:35 ` Shenghuo ZHU
2000-05-05 19:00 ` Karl Eichwalder
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=2nk8haf0ed.fsf@tiger.jia.vnet \
--to=zsh@cs.rochester.edu \
/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).