From: "Sudish Joseph" <sudish@VNET.IBM.COM>
Cc: ding@ifi.uio.no
Subject: Re: [sgnus-0.89] compose two messages simultaneously?
Date: 21 May 1996 10:30:54 -0400 [thread overview]
Message-ID: <m27mu6nlnl.fsf@galaxy.atlissc.ibm.com> (raw)
In-Reply-To: Manoj Srivastava's message of 21 May 1996 00:45:41 -0400
Manoj Srivastava <srivasta@pilgrim.umass.edu> writes:
> If I remember correctly, VM names the buffer something like
> *reply to somebody@somewhere* (I don't remember whether it has leading
I find this a very useful feature, too. VM's naming convention for
old messages ("sent mail to ..." "resent mail to..." etc.) is very
intuitive and saves you the bother of thinking up a reasonable name
while using rename uniquely.
This is trivial to add, but I dunno how it will go over. I was going
to add it to sendmail.el a long time back and stopped on seeing that
code that did something similar was already there in sendmail.el.
Here's the comment that accompanied the code:
;;; This is commented out because I found it was confusing in practice.
;;; It is easy enough to rename *mail* by hand with rename-buffer
;;; if you want to have multiple mail buffers.
;;; And then you can control which messages to save. --rms.
This was probably because the old code doesn't cleanup/reuse old
buffers (unlike VM).
> but then, I guess it could leave people with zillions of
> unkilled buffers (I don't seem to notice them building up, really)
VM lets you specify how many old buffers you wish to retain; it keeps
a list of all buffers it created and recycles the very oldest one when
it needs a new mail composition buffer.
-Sudish
prev parent reply other threads:[~1996-05-21 14:30 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
1996-05-21 0:35 ` Jack Vinson
1996-05-21 4:45 ` Manoj Srivastava
1996-05-21 14:30 ` Sudish Joseph [this message]
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=m27mu6nlnl.fsf@galaxy.atlissc.ibm.com \
--to=sudish@vnet.ibm.com \
--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).