From: Michael Heerdegen <michael_heerdegen@web.de>
To: Waleed Yousef <wyousef@fcih.net>
Cc: Lars Ingebrigtsen <larsi@gnus.org>, 42896@debbugs.gnu.org
Subject: bug#42896: 27.1; startup error after un update
Date: Tue, 13 Oct 2020 12:29:26 +0200 [thread overview]
Message-ID: <87v9fepgft.fsf@web.de> (raw)
In-Reply-To: <87v9ffe9c3.fsf@fcih.net> (Waleed Yousef's message of "Mon, 12 Oct 2020 08:46:04 -0700")
Waleed Yousef <wyousef@fcih.net> writes:
> Sorry, can you please guide me how I should provide it?
Sure.
You basically only need to set the variable `debug-on-error' to t,
e.g. with
M-: (setq debug-on-error t) RET
This will make the debugger pop-up for most kinds of errors. Then
reproduce the error with your recipe and post the contents of the
debugger buffer.
Detail: the debugger buffer will have more readable contents if you load
the elisp sources of the related elisp files before. You can get an
idea of which packages are involved by looking for the names of the
called functions in the debugger. Probably loading "gnus-registry.el"
should be good enough. You can use the command `find-library' to find
the source files, and use e.g. `load-buffer', or L from dired, to load
it.
When done, set `debug-on-error' back to nil:
M-: (setq debug-on-error nil) RET
Does that work for you?
TIA,
Michael.
next prev parent reply other threads:[~2020-10-13 10:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-17 1:55 bug#42896: 27.1; startup error after un update Waleed Yousef
2020-08-17 2:31 ` Eli Zaretskii
2020-08-22 21:16 ` Lars Ingebrigtsen
[not found] ` <87blhidfss.fsf@web.de>
[not found] ` <87ft6ut18q.fsf@fcih.net>
[not found] ` <87tuv9r3b0.fsf@web.de>
2020-10-08 18:48 ` Waleed Yousef
2020-10-09 1:18 ` Michael Heerdegen
2020-10-10 0:19 ` Waleed Yousef
2020-10-12 8:19 ` Michael Heerdegen
2020-10-12 15:46 ` Waleed Yousef
2020-10-13 10:29 ` Michael Heerdegen [this message]
2020-10-13 14:00 ` Waleed Yousef
2020-10-13 15:39 ` Robert Pluim
2020-10-13 16:12 ` Michael Heerdegen
2020-10-13 17:10 ` Waleed Yousef
2020-10-13 18:55 ` Basil L. Contovounesios
2020-10-14 3:47 ` 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
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=87v9fepgft.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=42896@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=wyousef@fcih.net \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).