From: Drew Adams <drew.adams@oracle.com>
To: Tim Johnson <tim@tj49.com>, 39682@debbugs.gnu.org
Subject: bug#39682: 26.3; Help window for list-packages disabled
Date: Thu, 20 Feb 2020 17:47:28 -0800 (PST) [thread overview]
Message-ID: <9953a4e1-23c8-417f-ad27-98fd2a66ebc0@default> (raw)
In-Reply-To: <1c501888-2bf4-8c45-ae49-4d1e64ea114f@tj49.com>
> describe-package works fine when I invoke
> emacs -q and then load el-get only.
What's needed is a minimal recipe, which involves only the one (or perhaps two) libraries that repro the problem.
Maybe the problem is only in help-fns+.el. Or maybe it's only in dired+.el. Or maybe it was only in an old byte-compiled help-fns+.el.
The point is that as long as multiple things are loaded it's hard to know what's going on, especially at a distance.
Ideally, it would be narrowed down to a single library, and even to just some of the code in that library.
My guess now, based on the fact that help-fns+.el redefines `describe-package' (to add a cross-reference to the manuals), is that help-fns+.el alone is probably causing (or probably caused) the problem.
And if the problem was only with an older help-fns+.elc (byte-compiled) then that's probably the explanation. The library has two different definitions of `describe-package', depending on which Emacs version you have (because they changed the vanilla code for it, on which the library's code is based).
If your older Emacs version was prior to Emacs 24.4 then the older definition of `describe-package' was used in the byte-compiled file. And that likely won't work with Emacs 24.4 or later.
It would be good to know for sure that that was the problem. But if you no longer have the old help-fns+.elc (byte-compiled before Emacs 24.4) then there's probably no way to reproduce the problem anymore.
---
Anyway, I see now that Noam has replied more or less the same thing, and has closed the bug report.
Thanks for reporting the problem and trying to track it down. Sorry to all for the trouble.
> >> I have much snow to shovel here - may not check email for several hours.
> > That'll probably keep you healthy. Good shoveling.
> Starting now ...
Just don't overdo it. ;-) Good luck.
next prev parent reply other threads:[~2020-02-21 1:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-19 22:23 bug#39682: 26.3; Help window for list-packages disabled Tim Johnson
2020-02-20 0:47 ` Noam Postavsky
2020-02-20 1:50 ` Drew Adams
2020-02-20 2:01 ` Noam Postavsky
2020-02-20 16:52 ` Tim Johnson
2020-02-20 17:12 ` Drew Adams
2020-02-20 17:53 ` Noam Postavsky
2020-02-20 20:12 ` Tim Johnson
2020-02-20 20:22 ` Noam Postavsky
2020-02-20 21:16 ` Tim Johnson
2020-02-20 21:30 ` Noam Postavsky
2020-02-20 23:14 ` Tim Johnson
2020-02-20 23:38 ` Tim Johnson
2020-02-21 0:02 ` Drew Adams
2020-02-21 1:25 ` Noam Postavsky
[not found] ` <1c501888-2bf4-8c45-ae49-4d1e64ea114f@tj49.com>
2020-02-21 1:47 ` Drew Adams [this message]
2020-02-21 2:07 ` Noam Postavsky
2020-02-21 3:27 ` Drew Adams
2020-02-21 18:20 ` Tim Johnson
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=9953a4e1-23c8-417f-ad27-98fd2a66ebc0@default \
--to=drew.adams@oracle.com \
--cc=39682@debbugs.gnu.org \
--cc=tim@tj49.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 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).