From: Dan Christensen <jdc@uwo.ca>
To: ding@gnus.org
Subject: Re: gnus-message-archive-group not producing a Gcc header
Date: Thu, 16 Dec 2010 17:29:03 -0500 [thread overview]
Message-ID: <87ipytl5cg.fsf@uwo.ca> (raw)
In-Reply-To: <m3hbed8vby.fsf@quimbies.gnus.org>
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> Dan Christensen <jdc@uwo.ca> writes:
>
>> That function contains
>>
>> ((null gnus-message-archive-method)
>> ;; Ignore.
>> nil)
>>
>> so nothing happens. I don't like having an extra "archive" server
>> in the server buffer, when I just use an existing server for saving
>> outgoing messages.
>
> I'm afraid you'll have to have the archive server set for this to work.
It seems quite odd to need to specify an archive server that is never
used. Why not only check that the archive-method is non-nil when and if
it is needed? Or, why not get rid of the idea of an archive server, and
just require that the archive group be "fully qualified", using an
existing server which is set up like any other server? Think how much
simpler that node in the manual would be.
But at least I found a different clean workaround:
(setq message-default-headers "Gcc: nnimap+rocky:Sent")
I'm not sure why there are two independent ways to achieve what I
want. Should they be merged? If not, the second way could be
mentioned in the manual as an easy, alternate option. In fact,
it should probably be mentioned first, since it is a one-liner.
Dan
next prev parent reply other threads:[~2010-12-16 22:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-06 1:43 Dan Christensen
2010-12-06 14:45 ` Lars Magne Ingebrigtsen
2010-12-06 15:21 ` Julien Danjou
2010-12-06 16:32 ` Dan Christensen
2010-12-16 17:46 ` Lars Magne Ingebrigtsen
2010-12-16 22:29 ` Dan Christensen [this message]
2010-12-17 0:17 ` Dan Christensen
2010-12-17 9:29 ` Julien Danjou
2010-12-17 16:41 ` Lars Magne Ingebrigtsen
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=87ipytl5cg.fsf@uwo.ca \
--to=jdc@uwo.ca \
--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).