unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Philip Kaludercic <philipk@posteo.net>
To: David Masterson <dsmasterson@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Info, dir, and Emacs packages ?
Date: Sat, 11 Mar 2023 10:33:10 +0000	[thread overview]
Message-ID: <87wn3npogp.fsf@posteo.net> (raw)
In-Reply-To: <SJ0PR03MB545575A5029D51FB17962986A2BB9@SJ0PR03MB5455.namprd03.prod.outlook.com> (David Masterson's message of "Fri, 10 Mar 2023 21:14:28 -0800")

David Masterson <dsmasterson@gmail.com> writes:

> I'm missing something.  When and what causes a package directory to get
> added to Info-directory-list? I've constructed a simple .info and dir
> for an existing Emacs package I'm playing with, but, when I copy them to
> the installed package and restart Emacs, it doesn't get added to the
> Info-directory-list, so isn't seen by 'info'.  Any help?

In `package-activate-1' (invoked by `package-activate' (invoked by
`package--activate-all' using `package--alist' (which uses
`package-load-all-descriptors'))) you will find this snippet:

--8<---------------cut here---------------start------------->8---
      ;; Add info node.
      (when (file-exists-p (expand-file-name "dir" pkg-dir))
        ;; FIXME: not the friendliest, but simple.
        (require 'info)
        (info-initialize)
        (add-to-list 'Info-directory-list pkg-dir))
--8<---------------cut here---------------end--------------->8---

So unless the dir or the .info file is broken (and this is an issue
caused by info), it might be that the package is not being detected?

-- 
Philip Kaludercic



  reply	other threads:[~2023-03-11 10:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-11  5:14 Info, dir, and Emacs packages ? David Masterson
2023-03-11 10:33 ` Philip Kaludercic [this message]
2023-03-12  2:36   ` David Masterson

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=87wn3npogp.fsf@posteo.net \
    --to=philipk@posteo.net \
    --cc=dsmasterson@gmail.com \
    --cc=emacs-devel@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.
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).