From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/27187 Path: main.gmane.org!not-for-mail From: Brian May Newsgroups: gmane.emacs.gnus.general Subject: Forwarding Mail Messages Date: 24 Nov 1999 11:06:49 +1100 Sender: owner-ding@hpc.uh.edu Message-ID: <84bt8kpxba.fsf@snoopy.apana.org.au> NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: main.gmane.org 1035164258 23295 80.91.224.250 (21 Oct 2002 01:37:38 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Mon, 21 Oct 2002 01:37:38 +0000 (UTC) Cc: Brian May Return-Path: Original-Received: from bart.math.uh.edu (bart.math.uh.edu [129.7.128.48]) by sclp3.sclp.com (8.8.5/8.8.5) with ESMTP id TAA19116 for ; Tue, 23 Nov 1999 19:11:39 -0500 (EST) Original-Received: from sina.hpc.uh.edu (lists@Sina.HPC.UH.EDU [129.7.3.5]) by bart.math.uh.edu (8.9.1/8.9.1) with ESMTP id SAB17088; Tue, 23 Nov 1999 18:11:24 -0600 (CST) Original-Received: by sina.hpc.uh.edu (TLB v0.09a (1.20 tibbs 1996/10/09 22:03:07)); Tue, 23 Nov 1999 18:11:15 -0600 (CST) Original-Received: from sclp3.sclp.com (root@sclp3.sclp.com [204.252.123.139]) by sina.hpc.uh.edu (8.9.3/8.9.3) with ESMTP id SAA04520 for ; Tue, 23 Nov 1999 18:10:34 -0600 (CST) Original-Received: from snoopy.apana.org.au (postfix@snoopy.apana.org.au [202.12.87.129]) by sclp3.sclp.com (8.8.5/8.8.5) with ESMTP id TAA19101 for ; Tue, 23 Nov 1999 19:10:04 -0500 (EST) Original-Received: by snoopy.apana.org.au (Postfix, from userid 1003) id 5A92E177F; Wed, 24 Nov 1999 11:06:51 +1100 (EST) Original-To: ding@gnus.org X-Home-Page: http://www.csse.monash.edu.au/~bmay/ Original-Lines: 47 User-Agent: Gnus/5.070098 (Pterodactyl Gnus v0.98) XEmacs/20.4 (Emerald) Precedence: list X-Majordomo: 1.94.jlt7 Xref: main.gmane.org gmane.emacs.gnus.general:27187 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:27187 Hello All, There was some concern over my proposal to allow forwarding of mail while entering a message that it might be difficult to implement. Here is a way to implement it that I think would be very simple. However, it requires a different mind set compared with mutt. 1. The user goes to the group buffer, and marks (#) messages that he/she wants to forward. 2. The user pushes special keystroke (to be invented), which invokes a function. This function automatically copies and/or appends entries to the buffer[1][2], in one of three formats: A) reference message number #part type="message/rfc822" group="nnml+private:mail.misc" message=1 #/part B) reference message id #part type="message/rfc822" group="nnml+private:mail.misc" message=<19991119091033.A23706@snoopy.apana.org.au> #/part C) include message #part type=message/rfc822 disposition=inline [...] #/part 3. The use pushes C-y to insert buffer into message. 4. When the message is sent, it is fetched from the appropriate group, as appropriate. This is similar to attaching a file. Which one? A), B), or C)? Personally I prefer one of A) or B). When I forward a message, I don't particular want to edit it, and these methods are more convenient. However, C) would require fewer changes. B) might be slowest, but might also be more convenient if typing in the entry manually. Note: [1] I think the is the correct notation ;-) [2] edited, so I can send it... put < and > at start and end of each entry -- Brian May