unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Tim Johnson <tim@akwebsoft.com>
To: Drew Adams <drew.adams@oracle.com>, MLEmacs <Help-gnu-emacs@gnu.org>
Subject: Re: No Help Window from *Packages* - No Package Specified Error
Date: Tue, 18 Feb 2020 15:30:07 -0900	[thread overview]
Message-ID: <ad585d79-10fd-2c75-e198-d44fe5118666@akwebsoft.com> (raw)
In-Reply-To: <f9dbc69d-8fc6-47ab-b738-a1ba8340dfcd@default>


On 2/18/20 2:31 PM, Drew Adams wrote:
> Hi Tim,
>
> Could you try bisecting either dired+.el or el-get.el (commenting out 1/2,... etc.), to see which part of either (or both) is causing the problem?

Began commenting out below the stack of required expressions. With 
el-get again being required/loaded from init.el, the list-packages help 
window was disabled with the "No package specified" error message 
regardless of the section disabled

Then I commented out all of the required expressions at the top of 
el-get.el and the error went away. Began uncommenting and found that the 
error shows again where

(require 'el-get-methods)

is executed.

May I conclude that it is coming from el-get-methods?

> I'm guessing it's something more general, something used in one or both of those libraries that is not particularly uncommon/bizarre, but that doesn't work well with package.el.  If so, it would be good to know what, and maybe report it to Emacs as a bug, if it's something that should be normal.
>
> (Alternatively, maybe it's something in package.el.)
>
> BTW, is this a new problem, e.g. started happening with a recent version of one or more of the 3 libraries (dired+, el-get, package)?

I use list-packages very infrequently. I also install new versions from 
source regularly as they are introduced as being stable - as in : 
./configure; make; make install

I don't recall what was previous to 26.3 because it has been overwritten 
as /usr/local/bin but it was at that version that I first noticed it.

thanks

>
> Thx - Drew
>
>> It appears to me that the following two packages:
>> (require 'package)
>> (require 'el-get)
>> are causing the problem.
>>
>> So, with dired+ loaded and the two packages above loaded, I do not get a
>> *Help* window when I click on a link to a package in the *Packages*
>> window, which is invoked from Alt-x list-packages.
>>
>> With (require 'dired+) commented out, I will get the *Help* window.
>>
>> With dired+ loaded; package el-get disabled I will get the *Help* window.
>>
>> So, I guess I will go with dired+ enabled, 'packages and 'el-get
>> disabled and the issue appears to be solved.

-- 
Tim
tj49.com




  parent reply	other threads:[~2020-02-19  0:30 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
2020-02-18 22:40       ` Tim Johnson
     [not found]         ` <f9dbc69d-8fc6-47ab-b738-a1ba8340dfcd@default>
2020-02-19  0:30           ` Tim Johnson [this message]
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=ad585d79-10fd-2c75-e198-d44fe5118666@akwebsoft.com \
    --to=tim@akwebsoft.com \
    --cc=Help-gnu-emacs@gnu.org \
    --cc=drew.adams@oracle.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.
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).