From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: info-gnus-english@gnu.org
Subject: Re: possible bug? gnus in emacs 27; error in hash-table-p
Date: Fri, 26 Jul 2019 10:36:32 -0700 [thread overview]
Message-ID: <87a7d0elzz.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87pnlwvi3w.fsf@googlemail.com>
physiculus <physiculus@gmail.com> writes:
> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>>> Why is it working?
>>
>> The only question harder to answer than "Why isn't it working?" is "Why
>> IS it working?" :)
>>
>> Your imap servers have a nnimap-split-methods value of 'default, which
>> means each one will use the value of nnmail-split-methods.
>> nnmail-split-methods is set to the symbol 'nnmail-split-fancy, so all
>> servers should use the value of that variable.
>>
>> The gnus-group-split-update function sets nnmail-split-fancy to a split
>> made from group parameters.
>>
>> In your config, you've got nnmail-split-methods set to an actual split.
>> But when gnus-group-split-update runs, it should completely override
>> that config with a split made from group parameters.
>>
>> So my question is: have you set to-list/to-address parameters on your
>> groups? Because if you haven't, I don't know how any splitting is
>> happening. Can you show the value of nnmail-split-fancy after Gnus is
>> done starting up?
> I try to understand what you wrote.
> Because i'm not sure what to-list parameter means here is one server
> configuration complete.
Okay, that answers that question :)
So the mail splitting is happening according to your value of
`nnmail-split-methods'? I guess if it ain't broke, we won't fix it!
I'll push a change to master in a day or two that changes the hook. You
can either rebuild then, or tbh could just leave your config the way it
is now.
Eric
_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english
prev parent reply other threads:[~2019-07-26 17:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-20 17:57 physiculus
2019-07-20 18:45 ` Eric Abrahamsen
[not found] ` <87k1cbe2j6.fsf@googlemail.com>
[not found] ` <87k1ca1xtp.fsf@ericabrahamsen.net>
[not found] ` <87muh6xazc.fsf@googlemail.com>
[not found] ` <87pnm26ixg.fsf@ericabrahamsen.net>
[not found] ` <87r26hxqkx.fsf@googlemail.com>
2019-07-23 9:32 ` paul poulsen
2019-07-23 19:01 ` Eric Abrahamsen
2019-07-24 16:34 ` physiculus
2019-07-24 17:04 ` Eric Abrahamsen
2019-07-26 5:33 ` physiculus
2019-07-26 15:35 ` Eric Abrahamsen
2019-07-26 17:08 ` physiculus
2019-07-26 17:36 ` Eric Abrahamsen [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=87a7d0elzz.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=info-gnus-english@gnu.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).