From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: cross-posting and gnus-group-split
Date: 21 Apr 2000 18:30:58 +0200 [thread overview]
Message-ID: <m31z3zct6l.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <84gnpc$90c$1@quimby.gnus.org>
John Wiegley <johnw@gnu.org> writes:
> In the function `gnus-group-split-update', is there a reason why the
> second argument passed to `gnus-group-split-fancy' is always nil? It
> would seem to make more sense if it followed the value of
> `nnmail-crosspost':
>
> ;;;###autoload
> (defun gnus-group-split-update (&optional catch-all)
> "Computes nnmail-split-fancy from group params.
> It does this by calling \(gnus-group-split-fancy nil nil DEFAULTGROUP)."
> (interactive)
> (setq nnmail-split-fancy
> (gnus-group-split-fancy
> nil (null nnmail-crosspost)
> (or catch-all gnus-group-split-default-catch-all-group)))
> (run-hooks 'gnus-group-split-updated-hook))
I don't know -- could the person that wrote this function say? (The
ChangeLog doesn't say who wrote this...)
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
prev parent reply other threads:[~2000-04-21 16:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-30 22:53 John Wiegley
2000-04-21 16:30 ` Lars Magne Ingebrigtsen [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=m31z3zct6l.fsf@quimbies.gnus.org \
--to=larsi@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).