From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: use-package documentation
Date: Sun, 01 Jan 2023 10:39:35 +0200 [thread overview]
Message-ID: <831qoe4piw.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmkFxSW_q=-+_dffppLR52PyjE4DF816O0hzrQ3n06tzTw@mail.gmail.com> (message from Stefan Kangas on Sat, 31 Dec 2022 12:28:57 +0100)
> From: Stefan Kangas <stefankangas@gmail.com>
> Date: Sat, 31 Dec 2022 12:28:57 +0100
> Cc: rms@gnu.org, emacs-devel@gnu.org
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > I think we should perhaps mention it in both manuals, and leave it as
> > a separate manual.
>
> Agreed.
>
> However, while I think it makes sense to mention it in the emacs
> manual, I don't currently see where it would fit in the elisp manual.
> Perhaps it'd be enough to mention it in the emacs manual.
I think I found good places in both manuals, please take a look at the
emacs-29 branch.
next prev parent reply other threads:[~2023-01-01 8:39 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 [this message]
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
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=831qoe4piw.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rms@gnu.org \
--cc=stefankangas@gmail.com \
/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).