From: jidanni@jidanni.org
To: ding@gnus.org
Subject: keep Gcc: field in buffer after sending
Date: Wed, 05 Dec 2007 13:03:53 +0800 [thread overview]
Message-ID: <874pex4ts6.fsf@jidanni.org> (raw)
Gentlemen, I note the Gcc: field disappears from the buffer after a
message is sent.
But often I go back to that buffer and make some alterations and send
another similar message, only later to discover a copy was not saved
on disk.
There ought to be a variable to stop this senseless abduction of the
Gcc: field upon message-send-and-exit, etc.
next reply other threads:[~2007-12-05 5:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-05 5:03 jidanni [this message]
2007-12-11 16:31 ` Ted Zlatanov
2007-12-11 19:02 ` jidanni
2007-12-11 23:01 ` Ted Zlatanov
2007-12-12 8:27 ` jidanni
2007-12-12 12:45 ` Ted Zlatanov
2007-12-12 13:16 ` Miles Bader
2007-12-12 13:26 ` Ted Zlatanov
2007-12-12 19:44 ` Reiner Steib
2007-12-12 20:46 ` Ted Zlatanov
2007-12-11 22:08 ` Reiner Steib
2007-12-11 23:10 ` Ted Zlatanov
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=874pex4ts6.fsf@jidanni.org \
--to=jidanni@jidanni.org \
--cc=ding@gnus.org \
/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).