From: physiculus <physiculus@gmail.com>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: info-gnus-english@gnu.org
Subject: Re: possible bug? gnus in emacs 27; error in hash-table-p
Date: Wed, 24 Jul 2019 18:34:36 +0200 [thread overview]
Message-ID: <87v9vr4cir.fsf@googlemail.com> (raw)
In-Reply-To: <875zns4ltl.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Tue, 23 Jul 2019 12:01:26 -0700")
Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
> 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.
Hello,
i tried your suggestions, but with no luck :-(
The following error occured right after first start of gnus.
Debugger entered--Lisp error: (wrong-type-argument hash-table-p nil)
gethash("JensPrivat" nil)
gnus-group-get-parameter("JensPrivat")
gnus-group-find-parameter("JensPrivat")
gnus-group-split-fancy(nil t "mail.misc")
gnus-group-split-update()
run-hooks(gnus-startup-hook)
apply(run-hooks gnus-startup-hook)
gnus-run-hooks(gnus-startup-hook)
#f(compiled-function () #<bytecode 0x15817af83639>)()
gnus-1(nil nil nil)
gnus(nil)
funcall-interactively(gnus nil)
call-interactively(gnus record nil)
command-execute(gnus record)
#f(compiled-function (cmd) #<bytecode 0x15817b0f103d>)("gnus")
ivy-call()
ivy-read("M-x " ("toggle-debug-on-error" "gnus" "restart-emacs" "package-list-packages" "desktop-read" "global-so-long-mode" "so-long-commentary" "desktop-save" "counsel-load-theme" "load-theme" "ivy-avy" "disable-theme" "package-delete" "package-install" "customize-themes" "enable-theme" "customize-group" "desktop-save-mode" "w3m-browse-url" "gnus-group-exit" "counsel-expand-env" "eww-mode" "org-mode" "browse-url" "other-frame" "cd" "tp" "ts" "5x5" "amx" "arp" "dbx" "dig" "erc" "ert" "eww" "ftp" "gdb" "irc" "jdb" "man" "mpc" "pdb" "pwd" "rsh" "sdb" "w3m" "xdb" "bbdb" "calc" ...) :predicate nil :require-match t :history counsel-M-x-history :action #f(compiled-function (cmd) #<bytecode 0x15817b0f103d>) :sort nil :keymap (keymap (67108908 . counsel--info-lookup-symbol) (67108910 . counsel-find-symbol)) :initial-input nil :caller counsel-M-x)
counsel-M-x()
funcall-interactively(counsel-M-x)
call-interactively(counsel-M-x nil nil)
command-execute(counsel-M-x)
Is this helpful?
Regards
Poul
_______________________________________________
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-24 16:34 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 [this message]
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=87v9vr4cir.fsf@googlemail.com \
--to=physiculus@gmail.com \
--cc=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).