From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: help-gnu-emacs@gnu.org
Subject: Re: With lavabit, C-u RET is unable to select the Inbox group in gnus
Date: Wed, 31 Jan 2018 13:49:14 -0500 [thread overview]
Message-ID: <87mv0tkgnp.fsf@ericabrahamsen.net> (raw)
In-Reply-To: 877erznxz7.fsf@tuyizere.org
gnuforever <help@tuyizere.org> writes:
> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>> I guess the first thing to do would be M-x debug-on-quit,
>
> Great command! I learn a lot of things here :-)
> I was struggling how to find the logs while the process was hanging.
>
>> That should give you a backtrace that you can provide here.
>
> 1. With this configuration:
>
> (setq gnus-select-method
> '(nnimap "my-email@lavabit.com"
> (nnimap-address "lavabit.com")
> (nnimap-inbox "INBOX")
> ;;(nnimap-split-methods default)
> (nnimap-expunge t)
> (nnimap-stream ssl)
> (nnimap-user "my-email@lavabit.com")))
>
> I get:
>
> Debugger entered--Lisp error: (quit)
> gnus-list-of-unread-articles("Inbox")
> gnus-select-newsgroup("Inbox" (4) nil)
> gnus-summary-read-group-1("Inbox" (4) t nil nil nil)
> gnus-summary-read-group("Inbox" (4) t nil nil nil nil)
> gnus-group-read-group((4) t)
> gnus-group-select-group((4))
> funcall-interactively(gnus-group-select-group (4))
> call-interactively(gnus-group-select-group nil nil)
> command-execute(gnus-group-select-group)
>
> 2. With this one:
>
> (setq gnus-select-method '(nnnil ""))
>
> (setq gnus-secondary-select-methods
> '((nnimap "my-email@lavabit.com"
> (nnimap-address "lavabit.com")
> (nnimap-inbox "INBOX")
> (nnimap-split-methods default)
> (nnimap-expunge t)
> (nnimap-stream ssl)
> (nnimap-server-port 993)
> (nnimap-user "my-email@lavabit.com"))))
>
> I get:
>
> Debugger entered--Lisp error: (quit)
> gnus-uncompress-range((1 . 537842298))
> gnus-articles-to-read("nnimap+my-email@lavabit.com:Inbox" (4))
> gnus-select-newsgroup("nnimap+my-email@lavabit.com:Inbox" (4) nil)
> gnus-summary-read-group-1("nnimap+my-email@lavabit.com:Inbox" (4) t nil nil nil)
> gnus-summary-read-group("nnimap+my-email@lavabit.com:Inbox" (4) t nil nil nil nil)
> gnus-group-read-group((4) t)
> gnus-group-select-group((4))
> gnus-topic-select-group((4))
> funcall-interactively(gnus-topic-select-group (4))
> call-interactively(gnus-topic-select-group nil nil)
> command-execute(gnus-topic-select-group)
Huh. I wonder why the second one isn't getting hung up on
`gnus-list-of-unread-articles'. Anyway, in both cases it seems like the
problem is that Gnus thinks there is a truly enormous number of messages
in your inbox (537,842,298 of them!), and is trying to handle that
quantity. I'm assuming you don't actually have half a billion messages?
How many *do* you have? I can't imagine how Gnus got that confused, but
you might try doing "C-u M-g" on your inbox in the *Group* buffer and
see if that corrects the problem.
Eric
next prev parent reply other threads:[~2018-01-31 18:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-30 5:41 With lavabit, C-u RET is unable to select the Inbox group in gnus gnuforever
2018-01-30 14:30 ` Eric Abrahamsen
2018-01-30 15:54 ` gnuforever
2018-01-31 18:49 ` Eric Abrahamsen [this message]
2018-02-01 19:57 ` gnuforever
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mv0tkgnp.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=help-gnu-emacs@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 read-only IMAP folder(s) and NNTP newsgroup(s).