unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: David Masterson <dsmasterson@gmail.com>
To: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: use-package documentation
Date: Thu, 05 Jan 2023 22:03:57 -0800	[thread overview]
Message-ID: <SJ0PR03MB545574B53ABA0D5EC786C2F2A2FB9@SJ0PR03MB5455.namprd03.prod.outlook.com> (raw)
In-Reply-To: <E1pB6cR-0001Fx-KB@fencepost.gnu.org> (Richard Stallman's message of "Thu, 29 Dec 2022 23:03:43 -0500")

Richard Stallman <rms@gnu.org> writes:

> [[[ 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. ]]]
>
> Should the documentation of use-package be merged into the Emacs Lisp
> Reference Manual?

Question: is it too early to "integrate" use-package documentation in
standard Emacs documents when there are other variants of use-package
(quelpa, straight, etc.) out there that may enhance or replace it?

Personally, I could see use-package (or variant) be the standard tool
for providing a standard structure to an init file and, so, talking
about that structure and how use-package helps facilitate it would
belong in the "Customization" section of the Emacs manual.  This would
be for new users graduating from push button setup (M-x customize) into
the next level of "programming" Emacs to fit the environment they want.
References could point to the Elisp manual to go beyond the basics of
"initialization" (setq, setup functions, etc.) to full programming for
really special customization.

-- 
David Masterson



  parent reply	other threads:[~2023-01-06  6:03 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
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 [this message]
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=SJ0PR03MB545574B53ABA0D5EC786C2F2A2FB9@SJ0PR03MB5455.namprd03.prod.outlook.com \
    --to=dsmasterson@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=rms@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).