From: Andrew Eskilsson <mpt95aes@pt.hk-r.se>
Cc: Ding Gnus List <ding@ifi.uio.no>
Subject: Re: [sgnus-0.89] compose two messages simultaneously?
Date: 20 May 1996 23:43:43 +0200 [thread overview]
Message-ID: <lvybmn3trk.fsf@pt.hk-r.se> (raw)
In-Reply-To: Mark Borges's message of Mon, 20 May 1996 15:09:31 -0600
/ Mark Borges <mdb@cdc.noaa.gov> wrote:
|
| I know this functionality was what the draft concept was for, but
| that's gone now, right? Would it be a simple (and safe) thing to put
| in the ability for message mode to use another buffer, e.g.,
| `*message* <2>'?
Hopefully it is on its way back in Red (?), at the moment I use M-x
rename-uniquely if I want to compose two mails.
/andy
--
Don't walk in front of me, I might be unable to follow you.
Don't walk after me, I might be unable to lead you.
Just walk by my side and be my friend.
next prev parent reply other threads:[~1996-05-20 21:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-05-20 21:09 Mark Borges
1996-05-20 21:43 ` Andrew Eskilsson [this message]
1996-05-21 0:35 ` Jack Vinson
1996-05-21 4:45 ` Manoj Srivastava
1996-05-21 14:30 ` Sudish Joseph
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=lvybmn3trk.fsf@pt.hk-r.se \
--to=mpt95aes@pt.hk-r.se \
--cc=ding@ifi.uio.no \
/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).