From: Jean-Christophe Helary <jean.christophe.helary@traduction-libre.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>,
Emacs developers <emacs-devel@gnu.org>
Subject: Re: "Emacs Lisp Packages" chapter in the Emacs manual
Date: Wed, 13 May 2020 11:27:00 +0900 [thread overview]
Message-ID: <B3986838-7981-4CEF-9B0B-4C0371F9AC0A@traduction-libre.org> (raw)
In-Reply-To: <928a354d-e458-4221-b00b-419d52dce2f8@default>
> On May 13, 2020, at 11:05, Drew Adams <drew.adams@oracle.com> wrote:
>
>>> I don't quite understand this part of your diff:
>>>
>>> +The traditional way to install Emacs Lisp code is to either install it
>>> +in the Emacs Lisp @dfn{load path} or to add the path to the code to
>>> +the load path list.
>>>
>>> What does it mean to "install" code in `load-path'?
>>> And how does that differ from adding the directory or
>>> file of the code to `load-path' (IOW, why the "or")?
>>
>> I'm just using the wording that's found in other parts of the manual.
>> Not trying to be fancy here :)
>>
>> Emacs manual:
>> "If an Emacs Lisp file is installed in the Emacs Lisp load path
>> (defined below), you can load it by typing M-x load-library, instead of
>> using M-x load-file."
>
> OK, so my question is for whomever wrote that, I guess.
:)
>> My understanding is that "install in the load path" means put the file
>> in a path that Emacs already knows vs "add the path to load path" means
>> make Emacs know about that new path.
>
> Maybe. Not for me to say. But if that's it then I
> think your text doesn't really say that, I think.
> I don't see anything in your text that suggests a
> path that Emacs already knows.
+The traditional way to install Emacs Lisp code is to either install it
+in the Emacs Lisp @dfn{load path}
*** or to add the path to the code to
+the load path list.***
@xref{Lisp Libraries}. Then, the user should
+follow the instructions given by the code author.
Isn't the *** part *** covering that ?
>>> [BTW, for GNU Emacs, "path" means something different.
>>> What you mean here is presumably the absolute file
>>> name (of the directory or the file itself).]
>>
>> I'm pretty sure I don't know the difference.
>
> For Emacs (and GNU, I think), a "path" is the kind of
> thing you have as the value of your environment
> variable PATH: a list of directories.
Ok, so that was close enough to my understanding. Thank you.
Jean-Christophe Helary
-----------------------------------------------
http://mac4translators.blogspot.com @brandelune
next prev parent reply other threads:[~2020-05-13 2:27 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-09 15:02 "Emacs Lisp Packages" chapter in the Emacs manual Jean-Christophe Helary
2020-05-09 15:19 ` Stefan Kangas
2020-05-09 16:47 ` Jean-Christophe Helary
2020-05-10 2:19 ` Jean-Christophe Helary
2020-05-10 14:17 ` Stefan Monnier
2020-05-10 15:05 ` Jean-Christophe Helary
2020-05-10 16:49 ` Stefan Monnier
2020-05-10 17:13 ` Jean-Christophe Helary
2020-05-10 19:28 ` Drew Adams
2020-05-11 1:02 ` Jean-Christophe Helary
2020-05-10 19:35 ` Stefan Monnier
2020-05-11 1:08 ` Jean-Christophe Helary
2020-05-11 1:51 ` Drew Adams
2020-05-11 3:26 ` Stefan Monnier
2020-05-11 4:23 ` Drew Adams
2020-05-11 4:40 ` Stefan Monnier
2020-05-11 6:57 ` Jean-Christophe Helary
2020-05-11 15:09 ` Stefan Monnier
2020-05-11 15:23 ` Drew Adams
2020-05-12 0:59 ` Jean-Christophe Helary
2020-05-12 3:21 ` Stefan Monnier
2020-05-12 3:50 ` Jean-Christophe Helary
2020-05-12 15:46 ` Drew Adams
2020-05-13 1:43 ` Jean-Christophe Helary
2020-05-13 2:05 ` Drew Adams
2020-05-13 2:27 ` Jean-Christophe Helary [this message]
2020-05-13 2:33 ` Drew Adams
2020-05-13 2:46 ` Stefan Monnier
2020-05-13 3:02 ` Jean-Christophe Helary
2020-05-16 10:23 ` Eli Zaretskii
2020-05-16 12:39 ` Jean-Christophe Helary
2020-05-16 14:38 ` Eli Zaretskii
2020-05-16 15:20 ` Jean-Christophe Helary
2020-05-12 15:46 ` Drew Adams
2020-05-11 15:13 ` Drew Adams
2020-05-12 3:18 ` Richard Stallman
2020-05-11 3:23 ` Stefan Monnier
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=B3986838-7981-4CEF-9B0B-4C0371F9AC0A@traduction-libre.org \
--to=jean.christophe.helary@traduction-libre.org \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.