[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: possible bug? gnus in emacs 27; error in hash-table-p
From: |
physiculus |
Subject: |
Re: possible bug? gnus in emacs 27; error in hash-table-p |
Date: |
Wed, 24 Jul 2019 18:34:36 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) |
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
- possible bug? gnus in emacs 27; error in hash-table-p, physiculus, 2019/07/20
- Re: possible bug? gnus in emacs 27; error in hash-table-p, Eric Abrahamsen, 2019/07/20
- Message not available
- Message not available
- Message not available
- Message not available
- Message not available
- possible bug? gnus in emacs 27; error in hash-table-p, paul poulsen, 2019/07/23
- Re: possible bug? gnus in emacs 27; error in hash-table-p, Eric Abrahamsen, 2019/07/23
- Re: possible bug? gnus in emacs 27; error in hash-table-p,
physiculus <=
- Re: possible bug? gnus in emacs 27; error in hash-table-p, Eric Abrahamsen, 2019/07/24
- Re: possible bug? gnus in emacs 27; error in hash-table-p, physiculus, 2019/07/26
- Re: possible bug? gnus in emacs 27; error in hash-table-p, Eric Abrahamsen, 2019/07/26
- Re: possible bug? gnus in emacs 27; error in hash-table-p, physiculus, 2019/07/26
- Re: possible bug? gnus in emacs 27; error in hash-table-p, Eric Abrahamsen, 2019/07/26