From: Tim Johnson <tim@akwebsoft.com>
To: MLEmacs <Help-gnu-emacs@gnu.org>
Subject: Re: No Help Window from *Packages* - No Package Specified Error
Date: Tue, 18 Feb 2020 11:40:18 -0900 [thread overview]
Message-ID: <283ec781-943d-97d2-e019-a4cb17c7d629@akwebsoft.com> (raw)
In-Reply-To: <efe70184-c152-4b0c-a5cc-d08f67839f52@default>
On 2/18/20 10:36 AM, Drew Adams wrote:
>>> When I run emacs with init.el and then invoke list-packages, the help
>>> window does not show for a package, regardless of mouse click or using
>>> keystroke "?"
> Did you mean only that a particular package is not listed?
>
> Or did you mean that if you use a particular package the help window
> (buffer `*Packages*') is not shown?
>
>>> This is not a problem when I start emacs with -q.
>>> I'm loading a lot of stuff in init.el, so I would welcome any ideas as
>>> to what I have 'require'd or configured.
>> After much tinkering, I have found that the following code in init.el
>> (require 'dired+)
>> Disables the information component of list-pack
> Again, same question as above.
>
> If you mean only that Dired+ is not listed, then
> I understand: It's not available in an ELPA repo;
> it's available from Emacs Wiki.
>
> But if you mean that requiring Dired+ prevents
> `list-packages' from displaying, then I don't
> see that. I use Dired+, and `list-packages'
> works for me.
>
> Or maybe there's more to the problem than just
> that `list-packages' doesn't display `*Packages*'?
>
> A priori, I don't think dired+.el should have
> any effect on `list-packages'.
By loading emacs as emacs -q ;; no init file
Adding the path to dired+ to the load-list via *Scratch*
Then loading dired+ with
(require 'dired+) ;; in *Scratch*
The *Help* window for any package is displayed as it should.
This suggest to me that some other configuration in init.el has a side
effect that is not apparent 'til dired+ is loaded. I.E. dired+ doesn't
trigger that problem so much as it is interacting with something else.
This is going to take me some time to track down, with my limited skill
set, I'll just have to play around with disabling certain features with
dired+ loaded and see what happens.
l8tr
--
Tim
tj49.com
next prev parent reply other threads:[~2020-02-18 20:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-17 23:26 No Help Window from *Packages* - No Package Specified Error Tim Johnson
2020-02-18 19:10 ` Tim Johnson
2020-02-18 19:36 ` Drew Adams
2020-02-18 20:40 ` Tim Johnson [this message]
2020-02-18 22:40 ` Tim Johnson
[not found] ` <f9dbc69d-8fc6-47ab-b738-a1ba8340dfcd@default>
2020-02-19 0:30 ` Tim Johnson
2020-02-19 1:05 ` Tim Johnson
2020-02-19 1:23 ` Drew Adams
2020-02-19 19:25 ` Tim Johnson
2020-02-24 18:21 ` solved[]Re: " 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=283ec781-943d-97d2-e019-a4cb17c7d629@akwebsoft.com \
--to=tim@akwebsoft.com \
--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).