From: prj@po.cwru.edu (Paul Jarc)
Subject: Re: typo in gnus-start.el?
Date: Sat, 08 Sep 2001 15:59:03 -0400 [thread overview]
Message-ID: <m37kv9bgiq.fsf@multivac.cwru.edu> (raw)
In-Reply-To: <vafu1yem05o.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "Sat, 08 Sep 2001 12:45:07 +0200")
Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) wrote:
> gnus-outgoing-message-group is older. One difference that I could
> find is that a gcc-self parameter for a group means that Gnus does not
> insert the Gcc header from gnus-message-archive-group, but it still
> inserts the Gcc header from gnus-outgoing-message-group.
>
> Another difference is that gnus-message-archive-group defaults to the
> archive server if no server is specified, whereas
> gnus-outgoing-message-group requires you to specify a server.
>
> I thought that the older feature would go away, but Lars told me no.
> But maybe the older feature should be excised anyway, and the new one
> repaired?
I'd almost prefer to get rid of gnus-message-archive-*, as they seem
more error-prone. The regexp-alist functionality could be added to
g-o-m-g; then the only difference would be the default-method stuff
(whence errors) and the gcc-self stuff (which could be dealt with in a
g-o-m-g function, though perhaps not very conveniently).
paul
prev parent reply other threads:[~2001-09-08 19:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-07 5:13 Bill White
2001-09-07 6:43 ` ShengHuo ZHU
2001-09-08 0:49 ` Dan Christensen
2001-09-08 10:45 ` Kai Großjohann
2001-09-08 19:59 ` Paul Jarc [this message]
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=m37kv9bgiq.fsf@multivac.cwru.edu \
--to=prj@po.cwru.edu \
/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).