From: Bernardo <bb.mail@exemail.com.au>
To: info-gnus-english@gnu.org
Subject: Gnus broken in the latest Emacs build?
Date: Sun, 24 Mar 2019 09:58:37 +1100 [thread overview]
Message-ID: <87h8bttcyq.fsf@pobox.com> (raw)
Greetings,
am i the only one seeing the problem with the latest Emacs build (Git commit
dbd6490ad49b0f088d56cdd5f04178bdd62c806a) ?
launched with:
$ emacs -Q &
after enabling the debuger and accessing the INBOX i get this error:
Debugger entered--Lisp error: (wrong-type-argument vectorp #<hash-table equal 6/6 0x15869e6eae51>)
intern-soft("nnimap+deb:INBOX" #<hash-table equal 6/6 0x15869e6eae51>)
gnus-browse-read-group(no nil)
gnus-browse-select-group(nil)
funcall-interactively(gnus-browse-select-group nil)
call-interactively(gnus-browse-select-group nil nil)
command-execute(gnus-browse-select-group)
--
Rgds, Bernardo
next reply other threads:[~2019-03-23 22:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-23 22:58 Bernardo [this message]
2019-03-24 3:34 ` Eric Abrahamsen
2019-03-25 19:51 ` Clemens Schüller
2019-03-26 13:42 ` Barry Fishman
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=87h8bttcyq.fsf@pobox.com \
--to=bb.mail@exemail.com.au \
--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).