From: paul poulsen <physiculus@gmail.com>
To: info-gnus-english@gnu.org
Subject: possible bug? gnus in emacs 27; error in hash-table-p
Date: Tue, 23 Jul 2019 11:32:47 +0200 [thread overview]
Message-ID: <CAEK1CZHFDvd+G76p77oJs=-07LJLnnDfLOkbwCGrmd5X3uaVfA@mail.gmail.com> (raw)
In-Reply-To: <87r26hxqkx.fsf@googlemail.com>
[-- Attachment #1.1: Type: text/plain, Size: 635 bytes --]
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?
PS: Until now i'm not able to switch my splitting to fancy-splitting.
Is it possible, that this problem is related?
Regards
Poul
[-- Attachment #1.2: Type: text/html, Size: 939 bytes --]
[-- Attachment #2: Type: text/plain, Size: 162 bytes --]
_______________________________________________
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 9:32 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 [this message]
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
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='CAEK1CZHFDvd+G76p77oJs=-07LJLnnDfLOkbwCGrmd5X3uaVfA@mail.gmail.com' \
--to=physiculus@gmail.com \
--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).