From: Lars Ingebrigtsen <larsi@gnus.org>
To: Alexander Baier <lexi.baier@gmail.com>
Cc: info-gnus-english@gnu.org
Subject: Re: Gcc is ignored when sending mail from emacs lisp
Date: Thu, 26 Dec 2013 01:00:04 +0100 [thread overview]
Message-ID: <87a9fobhx7.fsf@building.gnus.org> (raw)
In-Reply-To: <mailman.1627.1378681833.10748.info-gnus-english@gnu.org> (Alexander Baier's message of "Mon, 09 Sep 2013 01:10:12 +0200")
Alexander Baier <lexi.baier@gmail.com> writes:
> How do I create some kind of temporary group, so I can test, if gnus
> might be moving mail to that directory.
You can create groups by, for instance, copying a message to that group.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog http://lars.ingebrigtsen.no/
next prev parent reply other threads:[~2013-12-26 0:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-10 13:40 Alexander Baier
2013-05-11 19:39 ` W. Greenhouse
2013-05-13 10:59 ` Alexander Baier
[not found] ` <mailman.25652.1368464412.855.info-gnus-english@gnu.org>
2013-08-01 11:53 ` Lars Magne Ingebrigtsen
2013-09-08 23:10 ` Alexander Baier
[not found] ` <mailman.1627.1378681833.10748.info-gnus-english@gnu.org>
2013-12-26 0:00 ` Lars Ingebrigtsen [this message]
2013-12-26 0:13 ` Alexander Baier
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=87a9fobhx7.fsf@building.gnus.org \
--to=larsi@gnus.org \
--cc=info-gnus-english@gnu.org \
--cc=lexi.baier@gmail.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).