From: bojohan+news@dd.chalmers.se (Johan Bockgård)
Subject: Re: very quick question about open buffers after sending replies...
Date: Thu, 22 Jun 2006 22:20:53 +0200 [thread overview]
Message-ID: <yoijfyhx54d6.fsf@linus003.dd.chalmers.se> (raw)
In-Reply-To: <ee9rm3-psf.ln1@news.tdc.dk>
hotmail_spam@hotmail.com (Martin Jørgensen) writes:
> Then I write my comments and then I press C-c C-c and the post is
> send. But the buffer isn't closed. [...]
> So is it supposed to work that way?
Yes.
> I don't like having manually to kill those buffers, so is there a
> better method?
(info "(message)Message Buffers")
--
Johan Bockgård
next prev parent reply other threads:[~2006-06-22 20:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-22 19:59 Martin Jørgensen
2006-06-22 20:20 ` Johan Bockgård [this message]
2006-06-24 8:07 ` Martin Jørgensen
2006-06-24 8:16 ` Martin Jørgensen
2006-06-29 23:01 Martin Jørgensen
2006-06-30 11:00 ` Robert D. Crawford
2006-06-30 21:38 ` Martin Jørgensen
2006-06-30 23:36 ` Johan Bockgård
2006-07-01 2:31 ` Robert D. Crawford
2006-07-01 18:21 ` Martin Jørgensen
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=yoijfyhx54d6.fsf@linus003.dd.chalmers.se \
--to=bojohan+news@dd.chalmers.se \
/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).