Gnus development mailing list
 help / color / mirror / Atom feed
From: Brian May <bmay@csse.monash.edu.au>
Cc: Brian May <bmay@csse.monash.edu.au>
Subject: Forwarding Mail Messages
Date: 24 Nov 1999 11:06:49 +1100	[thread overview]
Message-ID: <84bt8kpxba.fsf@snoopy.apana.org.au> (raw)

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 <bmay@csse.monash.edu.au>


             reply	other threads:[~1999-11-24  0:06 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-11-24  0:06 Brian May [this message]
1999-12-01 19:47 ` Lars Magne Ingebrigtsen
1999-12-02  0:42   ` Nevin Kapur
1999-12-02  1:19     ` What now? (was: Forwarding Mail Messages) Lars Magne Ingebrigtsen
1999-12-02  2:59       ` What now? Brian May
1999-12-02 16:23         ` Colin Marquardt
1999-12-02 16:56         ` Jody M. Klymak
1999-12-06  4:26           ` Lars Magne Ingebrigtsen
1999-12-06  5:31             ` Brian May
1999-12-07  5:36               ` William M. Perry
1999-12-07  5:59                 ` Brian May
1999-12-07 16:09                   ` William M. Perry
1999-12-08  8:02                     ` nnimap URLs? (Was: What now?) Steinar Bang
1999-12-08 16:08                       ` William M. Perry
1999-12-08 18:02                         ` Simon Josefsson
1999-12-08 18:23                           ` William M. Perry
1999-12-08 17:26                       ` Simon Josefsson
1999-12-10 16:07                         ` William M. Perry
1999-12-08 22:51                     ` What now? Brian May
1999-12-06 17:36             ` Jody M. Klymak
1999-12-06 20:34               ` Bruce Stephens
1999-12-06 22:38               ` Kai Großjohann
1999-12-03 19:12       ` What now? (was: Forwarding Mail Messages) Jody M. Klymak
1999-12-04 17:05         ` Hrvoje Niksic
1999-12-04 22:53           ` Jody M. Klymak
2000-04-21 21:13         ` Lars Magne Ingebrigtsen
2000-04-21 21:05           ` William M. Perry
2000-04-21 21:16             ` Arcady Genkin
2000-04-21 23:32               ` William M. Perry
2000-04-22  9:36             ` Hans de Graaff
1999-12-05 21:46       ` Kai Großjohann
1999-12-05 21:51       ` Kai Großjohann
1999-12-06  1:27       ` Richard Hoskins
1999-12-02  1:48   ` Forwarding Mail Messages Brian May
1999-12-06  4:12     ` Lars Magne Ingebrigtsen

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=84bt8kpxba.fsf@snoopy.apana.org.au \
    --to=bmay@csse.monash.edu.au \
    /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).