From: Eli Zaretskii <eliz@gnu.org>
To: David Masterson <dsmasterson@gmail.com>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: use-package documentation
Date: Fri, 06 Jan 2023 09:43:51 +0200 [thread overview]
Message-ID: <83y1qgumyw.fsf@gnu.org> (raw)
In-Reply-To: <SJ0PR03MB545574B53ABA0D5EC786C2F2A2FB9@SJ0PR03MB5455.namprd03.prod.outlook.com> (message from David Masterson on Thu, 05 Jan 2023 22:03:57 -0800)
> From: David Masterson <dsmasterson@gmail.com>
> Cc: emacs-devel@gnu.org
> Date: Thu, 05 Jan 2023 22:03:57 -0800
>
> Richard Stallman <rms@gnu.org> writes:
>
> 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.
This is no longer a theoretical argument: use-package is now shortly
described in both core manuals as I thought it should be, with a
cross-reference to the full manual that came with use-package. So
please review what's in the manuals now, and if you have concrete
suggestions for changes or improvements, please post such specific
suggestions wrt the existing text in the manuals.
prev parent reply other threads:[~2023-01-06 7:43 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
2023-01-06 7:06 ` Ihor Radchenko
2023-01-06 7:43 ` Eli Zaretskii [this message]
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=83y1qgumyw.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=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).