From mboxrd@z Thu Jan  1 00:00:00 1970
X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/37644
Path: main.gmane.org!not-for-mail
From: prj@po.cwru.edu (Paul Jarc)
Newsgroups: gmane.emacs.gnus.general
Subject: Re: archiving oddness
Date: Thu, 09 Aug 2001 13:37:38 -0400
Organization: What did you have in mind?  A short, blunt, human pyramid?
Message-ID: <m3bslpb0cn.fsf@multivac.cwru.edu>
References: <m3lmktb2tj.fsf@multivac.cwru.edu>
	<vafelql40lu.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de>
NNTP-Posting-Host: coloc-standby.netfonds.no
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
X-Trace: main.gmane.org 1035173020 14899 80.91.224.250 (21 Oct 2002 04:03:40 GMT)
X-Complaints-To: usenet@main.gmane.org
NNTP-Posting-Date: Mon, 21 Oct 2002 04:03:40 +0000 (UTC)
Return-Path: <prj@multivac.cwru.edu>
Return-Path: <prj@multivac.cwru.edu>
Original-Received: (qmail 25214 invoked from network); 9 Aug 2001 17:37:38 -0000
Original-Received: from multivac.student.cwru.edu (HELO multivac.cwru.edu) (261@129.22.96.25)
  by gnus.org with SMTP; 9 Aug 2001 17:37:38 -0000
Original-Received: (qmail 1552 invoked by uid 500); 9 Aug 2001 17:38:00 -0000
Mail-Followup-To: ding@gnus.org
Original-To: ding@gnus.org
Mail-Copies-To: never
In-Reply-To: <vafelql40lu.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de>
 (Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "Thu, 09 Aug 2001
 19:14:21 +0200")
User-Agent: Gnus/5.090004 (Oort Gnus v0.04) Emacs/20.7
Original-Lines: 24
Xref: main.gmane.org gmane.emacs.gnus.general:37644
X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:37644

Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Gro=DFjohann) writes:
> prj@po.cwru.edu (Paul Jarc) writes:
>> This doesn't (do I need to restart Gnus?):
>> (setq gnus-message-archive-method nil) ; Is this wrong?
>> (setq gnus-message-archive-group "nnmaildir:sent")
...
> I have gnus-message-archive-group set to "nnimap:INBOX" but leave
> gnus-message-archive-method at the default value.  That works.

I wonder if this should be changed.  If g-m-a-m is so troublesome,
then maybe people should be able to use g-m-a-g without creating a new
server.  Or maybe not - maybe this is why g-o-m-g isn't going away.

> There is a difference between gnus-message-archive-group and
> gnus-outgoing-message-group: if you set the gcc-self parameter on a
> group, you get two Gcc headers with gnus-outgoing-message-group but
> only one (the gcc-self one) for gnus-message-archive-group.

I suppose one could work around that by setting g-o-m-g to a function
that checks for the gcc-self parameter.  Where would such a function
find the current group name?


paul