From: Stefan Kangas <stefan@marxist.se>
To: Noam Postavsky <npostavs@gmail.com>
Cc: 40923@debbugs.gnu.org, Eduardo Ochs <eduardoochs@gmail.com>
Subject: bug#40923: M-x list-packages -> blah elpa.gnu.org blah: "incomprehensible buffer"
Date: Tue, 1 Sep 2020 08:00:56 -0700 [thread overview]
Message-ID: <CADwFkm=Fbcmp0rgUMVwQxqB4Rm=v2G3Je858nMazqX+DaF=HiA@mail.gmail.com> (raw)
In-Reply-To: <87pnbimwri.fsf@gmail.com> (Noam Postavsky's message of "Tue, 05 May 2020 07:44:33 -0400")
Noam Postavsky <npostavs@gmail.com> writes:
> Eduardo Ochs <eduardoochs@gmail.com> writes:
>
>> If I run `M-x list-packages' - or if I type C-e C-x C-e in the first
>> line - it does not list anything from ELPA and gives this error:
>>
>> error in process sentinel: Error retrieving:
>> https://elpa.gnu.org/packages/archive-contents "incomprehensible
>> buffer"
>
> Oh, sorry, I somehow didn't realize you meant the "incomprehensible
> buffer" part literally until now. Try doing
>
> (setq debug-on-signal t debug-on-error t)
>
> before calling list-packages to stop at the error in the debugger (it's
> possible you could hit some different errors first, in which case press
> 'c' to continue until you get the "incomprehensible buffer" one again).
> Then check the contents of the buffer. You can get the buffer name to
> look at, with
>
> e (current-buffer) RET
>
> in the debugger. The name will probably be " *temp*" (note the leading
> space) possibly with a random number as suffix. Then look at the
> contents, hopefully that will give a clue as to what happened.
(That was 17 weeks ago.)
Did you ever find out anything more about what could cause this?
next prev parent reply other threads:[~2020-09-01 15:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-28 7:52 bug#40923: M-x list-packages -> blah elpa.gnu.org blah: "incomprehensible buffer" Eduardo Ochs
2020-04-28 17:43 ` Noam Postavsky
2020-05-02 8:51 ` Eduardo Ochs
2020-05-05 11:44 ` Noam Postavsky
2020-09-01 15:00 ` Stefan Kangas [this message]
2020-10-26 15:50 ` Lars Ingebrigtsen
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='CADwFkm=Fbcmp0rgUMVwQxqB4Rm=v2G3Je858nMazqX+DaF=HiA@mail.gmail.com' \
--to=stefan@marxist.se \
--cc=40923@debbugs.gnu.org \
--cc=eduardoochs@gmail.com \
--cc=npostavs@gmail.com \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.