From: Lars Ingebrigtsen <larsi@gnus.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 21704@debbugs.gnu.org
Subject: bug#21704: 25.0.50; Package (package.el) doc should mention effects on `load-path'
Date: Sun, 01 May 2016 00:24:30 +0200 [thread overview]
Message-ID: <87inyy7n1d.fsf@gnus.org> (raw)
In-Reply-To: <489dac34-2cb6-416d-9ef2-301884dd31d8@default> (Drew Adams's message of "Sun, 18 Oct 2015 07:24:19 -0700 (PDT)")
Drew Adams <drew.adams@oracle.com> writes:
> Apparently (at least from searching package.el and (emacs) `Packages'
> and its subnodes), nowhere do we tell users the effect of using the
> package system on `load-path'. (Variable `load-path' is mentioned in a
> couple of doc strings, but only for "internal-only" functions.)
>
> There is this comment in the Commentary of `package.el':
>
> ;; At activation time we will set up the load-path and the info path,
> ;; and we will load the package's autoloads. If a package's
> ;; dependencies are not available, we will not activate that package.
>
> I think it is important (helpful) to explicitly make the connection for
> users between `load-path' and the package system. Please consider
> making it clear. Even just a statement such as the one in that comment
> would help.
Do you have a suggestion as to where in the manual we should mention the
load-path impact?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2016-04-30 22:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-18 14:24 bug#21704: 25.0.50; Package (package.el) doc should mention effects on `load-path' Drew Adams
2016-04-30 22:24 ` Lars Ingebrigtsen [this message]
2016-05-01 1:18 ` Drew Adams
2016-06-27 4:45 ` Noam Postavsky
2016-06-27 5:40 ` Drew Adams
2016-06-27 12:30 ` Noam Postavsky
2016-06-27 13:56 ` Drew Adams
2016-06-27 15:37 ` Eli Zaretskii
2016-06-28 3:18 ` Noam Postavsky
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=87inyy7n1d.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=21704@debbugs.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.
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).