From: Steven L Baur <steve@miranova.com>
Subject: Re: Killing *mail* and *postnews* buffers
Date: 30 Jan 1996 09:26:21 -0800 [thread overview]
Message-ID: <m2ag35oapu.fsf@miranova.com> (raw)
In-Reply-To: Kai Grossjohann's message of 30 Jan 1996 05:47:09 -0800
>>>>> "Kai" == Kai Grossjohann <grossjoh@charly.informatik.uni-dortmund.de> writes:
>>>>> On 30 Jan 1996 12:38:05 +0100, abraham@dina.kvl.dk (Per
>>>>> Abrahamsen) said:
Per> The drafts system is nice, but it has made it more difficult if
Per> you decide not to post/mail anyway. I used just to kill the
Per> buffer with `C-x k RET'. [...]
Kai> I still do that. Am I doing something terribly wrong?
By doing that you can end up with a lot of unfinished, partially saved,
unuseful draft articles.
--
steve@miranova.com baur
Unsolicited commercial e-mail will be proofread for $250/hour.
next prev parent reply other threads:[~1996-01-30 17:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-01-30 11:38 Per Abrahamsen
1996-01-30 13:47 ` Kai Grossjohann
1996-01-30 16:38 ` Per Abrahamsen
1996-01-30 17:26 ` Steven L Baur [this message]
1996-01-30 18:20 ` Thomas Neumann
1996-01-30 15:01 ` Jack Vinson
1996-01-31 17:35 ` David L Jackson
1996-01-31 20:46 ` Lars Magne Ingebrigtsen
1996-01-31 20:56 ` Stainless Steel Rat
1996-01-31 21:05 ` Stainless Steel Rat
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=m2ag35oapu.fsf@miranova.com \
--to=steve@miranova.com \
/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).