all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Jean-Christophe Helary <jean.christophe.helary@traduction-libre.org>
To: Emacs developers <emacs-devel@gnu.org>
Subject: Re: "Emacs Lisp Packages" chapter in the Emacs manual
Date: Sun, 10 May 2020 11:19:47 +0900	[thread overview]
Message-ID: <11AC1ECE-C120-4CBE-93C7-6FD82AF12299@traduction-libre.org> (raw)
In-Reply-To: <75254771-9303-4982-AB60-F92AF7AC6454@traduction-libre.org>

[-- Attachment #1: Type: text/plain, Size: 2820 bytes --]

> On May 10, 2020, at 1:47, Jean-Christophe Helary <jean.christophe.helary@traduction-libre.org> wrote:
> 
>> On May 10, 2020, at 0:19, Stefan Kangas <stefankangas@gmail.com> wrote:
>> 
>> Jean-Christophe Helary <jean.christophe.helary@traduction-libre.org>
>> writes:
>> 
>>> --- a/doc/emacs/package.texi
>>> +++ b/doc/emacs/package.texi
>>> @@ -13,6 +13,9 @@ Packages
>>> separate Emacs Lisp program, sometimes including other components such
>>> as an Info manual.
>>> 
>>> +  Emacs Lisp programs that are not available through this facility can
>>> +still be loaded by installing them in the Emacs Lisp @dfn{load path}.  @xref{Lisp Libraries}.
>>> +
>>>>  @kbd{M-x list-packages} brings up a buffer named @file{*Packages*}
>>> with a list of all packages.  You can install or uninstall packages
>>> via this buffer.  @xref{Package Menu}.
>> 
>> It's a useful addition, I think, but it seems a bit backwards to add it
>> before even introducing `list-packages'.
>> 
>> I would suggest to move it further down.  It could be the second to last
>> paragraph, for example.
> 
> I'm not the most qualified person to discuss location, but if people think "install", it seems nice to tell them up front that there are 2 ways to do that. 
> 
> In fact, I first thought of something like this:
> 
> ============
> The traditional way to install Emacs Lisp code is to install it in the Emacs Lisp @dfn{load path}.  @xref{Lisp Libraries}.
> 
> Now, Emacs includes a facility that lets you easily download and install
> @dfn{packages} that implement additional features.
> ...
> ============


I think I have a better proposal:

1) add a pointer to the Lisp Librairies section of the manual in package.texi

48 Emacs Lisp Packages
**********************

The traditional way to install Emacs Lisp code is to install it in the
Emacs Lisp "load path".  *Note Lisp Libraries::.

   Now, Emacs includes a facility that lets you easily download and
install "packages" that implement additional features.  Each package is
a separate Emacs Lisp program, sometimes including other components such
as an Info manual.


2) add a reference to "require" in the Features section of the manual in building.texi

   To automatically load code that you have installed in the load path,
you can use `require' in your init file.  *Note Features:
(elisp)Features. For example, here's how to automatically load the
features provided by file `feature.el' installed in your load path:

     (require 'feature)


Is there a better way to give easy access to this information ? In case the proposal above is accepted, I'm attaching the corresponding patch.


Jean-Christophe Helary
-----------------------------------------------
http://mac4translators.blogspot.com @brandelune



[-- Attachment #2: package.texi.200510.diff --]
[-- Type: application/octet-stream, Size: 1742 bytes --]

diff --git a/doc/emacs/building.texi b/doc/emacs/building.texi
index 77a0e807c2..93ff85c600 100644
--- a/doc/emacs/building.texi
+++ b/doc/emacs/building.texi
@@ -1558,11 +1558,18 @@ Lisp Libraries
 @code{help-enable-autoload} to @code{nil}.
 
 @vindex help-enable-completion-autoload
-Automatic loading also occurs when completing names for
+  Automatic loading also occurs when completing names for
 @code{describe-variable} and @code{describe-function}, based on the
 prefix being completed.  To disable this feature, change the variable
 @code{help-enable-completion-autoload} to @code{nil}.
 
+@findex require
+  To automatically load code that you have installed in the load path, you can use @code{require} in your init file.  @xref{Features,,, elisp, the Emacs Lisp Reference Manual}. For example, here's how to automatically load the features provided by file @file{feature.el} installed in your load path:
+
+@example
+(require 'feature)
+@end example
+
 @node Lisp Eval
 @section Evaluating Emacs Lisp Expressions
 @cindex Emacs Lisp mode
diff --git a/doc/emacs/package.texi b/doc/emacs/package.texi
index db3cf317ff..8a342cc0f3 100644
--- a/doc/emacs/package.texi
+++ b/doc/emacs/package.texi
@@ -7,8 +7,9 @@ Packages
 @cindex Package
 @cindex Emacs Lisp package archive
 @cindex Package archive
+The traditional way to install Emacs Lisp code is to install it in the Emacs Lisp @dfn{load path}.  @xref{Lisp Libraries}.
 
-Emacs includes a facility that lets you easily download and install
+  Now, Emacs includes a facility that lets you easily download and install
 @dfn{packages} that implement additional features.  Each package is a
 separate Emacs Lisp program, sometimes including other components such
 as an Info manual.

  reply	other threads:[~2020-05-10  2:19 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 [this message]
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
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=11AC1ECE-C120-4CBE-93C7-6FD82AF12299@traduction-libre.org \
    --to=jean.christophe.helary@traduction-libre.org \
    --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 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.