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: Tue, 23 Jul 2019 12:01:26 -0700 [thread overview]
Message-ID: <875zns4ltl.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <CAEK1CZHFDvd+G76p77oJs=-07LJLnnDfLOkbwCGrmd5X3uaVfA@mail.gmail.com>
paul poulsen <physiculus@gmail.com> writes:
> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>>
>> Okay, I see that the Gnus manual tells users to put this call directly
>> in their gnus.el files, so your config here has no problems. The problem
>> is in how the function does the update -- it should probably be delayed
>> until Gnus has been started up. I'm going to file this as a bug, with a
>> proposed solution, and hopefully we'll have this sorted out soon.
>>
>> Thanks for the report,
>> Eric
>
> Thanks a lot!
> Do you communicate the solution here?
Not only that, I'll ask you to test it first! :)
> PS: Until now i'm not able to switch my splitting to fancy-splitting.
> Is it possible, that this problem is related?
It could be. First of all, you're trying to do splitting with imap,
right?
The first call to `gnus-group-split-update' would fail in your case, but
you also passed the AUTO-UPDATE flag, so it should be getting called
again afterwards, each time you get new mail.
On the other hand, with auto-update, the function is added to the
`nnmail-pre-get-new-mail-hook', which is run for all backends that
support splitting *except* nnimap, which doesn't call
`nnmail-get-new-mail', but calls `nnmail-split-incoming' directly.
So it probably wouldn't work for nnimap no matter what. I'm just
thinking out loud here.
Let's do this the other way: would you remove this line from your gnus.el
file:
(gnus-group-split-setup t)
And replace it with these two lines:
(setq nnmail-split-methods 'nnmail-split-fancy)
(add-hook 'gnus-startup-hook #'gnus-group-split-update)
And see if that gets fancy splitting working in Gnus? Then we can go
backwards from there.
Thanks,
Eric
_______________________________________________
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-23 19:01 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 [this message]
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
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=875zns4ltl.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).