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 08:35:09 -0700 [thread overview]
Message-ID: <87wog4erma.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87y30lcqcj.fsf@googlemail.com>
physiculus <physiculus@gmail.com> writes:
> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>>
>> Oops, sorry, I should have seen that coming. Would you test instead:
>>
>> (add-hook 'gnus-read-newsrc-el-hook #'gnus-group-split-update)
>>
>> That seems to be the only place to run after the groups have been read,
>> but before unread messages are fetched for the first time.
>>
>> Eric
>
> Wonderful! Now it works.
> Thank you for the help.
>
> One thing i do not understand:
> As far as i read, your lines switch splitting to fancy-splitting,
> right?
> If so, splitting rules have to be in splitting-rule syntax (i read it in
> the manual) and should be inside the server.
> But i didn't change any of my rules and gnus is splitting.
> The rules are outside the server.
> 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?
> Is it better, to put it inside the server?
If you want different rules for different servers, then put the rules in
the individual servers. If you want the same rules for everything, then
you can just set global values.
_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english
next prev parent reply other threads:[~2019-07-26 15:35 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 [this message]
2019-07-26 17:08 ` physiculus
2019-07-26 17:36 ` Eric Abrahamsen
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=87wog4erma.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).