unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: use-package documentation
Date: Sat, 31 Dec 2022 22:04:23 -0500	[thread overview]
Message-ID: <E1pBoe7-0004rn-C9@fencepost.gnu.org> (raw)
In-Reply-To: <83bknl6zan.fsf@gnu.org> (message from Eli Zaretskii on Fri, 30 Dec 2022 11:01:04 +0200)

[[[ To any NSA and FBI agents reading my email: please consider    ]]]
[[[ whether defending the US Constitution against all enemies,     ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

  > It is a relatively large manual (2K lines of Texinfo), so adding it is
  > somewhat problematic.  It is also half-way between user-level and
  > Lisp-level, so which manual should mention it is not clear.

People expect the Emacs Lisp Reference Manual to tell all about Emacs
Lisp except for things that are somewhat obscure.  People have said
that use-package is much more convenient than `require' for the .emacs
file.  If that is so, we can expect it to become widely used if we
make the community aware of it.

This argues that at least the most important/most widely used features
of `use-package' should be described in the Emacs Lisp Reference
Manual.  The rest of the could be left in a separate manual.

Where in the Emacs Lisp Reference Manual should those aspects of
`use-package' go?  Perhaps in the node, The Init File.  Or in a new
node, added just after that one, to contain "useful things to use in
your init file".

-- 
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)





  parent reply	other threads:[~2023-01-01  3:04 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-30  4:03 use-package documentation Richard Stallman
2022-12-30  9:01 ` Eli Zaretskii
2022-12-31 11:28   ` Stefan Kangas
2023-01-01  8:39     ` Eli Zaretskii
2023-01-01  3:04   ` Richard Stallman [this message]
2023-01-01  6:46     ` Eli Zaretskii
2023-01-04 19:23       ` John Wiegley
2023-01-05 10:36         ` Stefan Kangas
2023-01-05 11:19           ` Eli Zaretskii
2023-01-06  4:37         ` Richard Stallman
2023-01-06  7:13           ` Eli Zaretskii
2022-12-30  9:02 ` Philip Kaludercic
2023-01-06  6:03 ` David Masterson
2023-01-06  7:06   ` Ihor Radchenko
2023-01-06  7:43   ` Eli Zaretskii

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=E1pBoe7-0004rn-C9@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=eliz@gnu.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 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).