From: Eli Zaretskii <eliz@gnu.org>
To: rms@gnu.org
Cc: jporterbugs@gmail.com, philipk@posteo.net,
monnier@iro.umontreal.ca, 65027@debbugs.gnu.org
Subject: bug#65027: 30.0.50; [PATCH] Document .elpaignore behavior in the Emacs Lisp manual
Date: Sat, 05 Aug 2023 09:43:56 +0300 [thread overview]
Message-ID: <83r0oit2dv.fsf@gnu.org> (raw)
In-Reply-To: <E1qS6Z1-00042J-Qk@fencepost.gnu.org> (message from Richard Stallman on Fri, 04 Aug 2023 21:58:43 -0400)
> From: Richard Stallman <rms@gnu.org>
> Cc: monnier@iro.umontreal.ca, eliz@gnu.org, philipk@posteo.net,
> 65027@debbugs.gnu.org
> Date: Fri, 04 Aug 2023 21:58:43 -0400
>
> > Maybe it would make sense to put all the documentation in the Emacs Lisp
> > manual,
>
> That has a drawback: it would make the Emacs Lisp Reference Manual
> substantially bigger. Copies would be less convenient and more
> expensive.
I don't think there's a real danger here. The necessary additions to
what is already in the ELisp manual are small.
The reason the ELisp manual touches on these issues is because it
describes package.el, which is a much more general facility, not
limited to ELPA. The ELPA-specific stuff should not be described
there, only mentioned with a reference to the ELPA README.
next prev parent reply other threads:[~2023-08-05 6:43 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-03 4:56 bug#65027: 30.0.50; [PATCH] Document .elpaignore behavior in the Emacs Lisp manual Jim Porter
2023-08-03 9:02 ` Eli Zaretskii
2023-08-03 13:36 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-03 17:24 ` Jim Porter
2023-08-03 19:09 ` Philip Kaludercic
2023-08-03 21:21 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-03 22:02 ` Jim Porter
2023-08-03 22:41 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-04 3:11 ` Jim Porter
2023-09-03 11:18 ` Stefan Kangas
2023-09-06 1:56 ` Jim Porter
2023-09-06 2:22 ` Corwin Brust
2023-09-19 13:29 ` Corwin Brust
2023-09-19 13:53 ` Protesilaos Stavrou
2023-09-20 10:35 ` Protesilaos Stavrou
2023-09-21 1:37 ` Stefan Kangas
2023-08-04 5:42 ` Eli Zaretskii
2023-08-05 1:58 ` Richard Stallman
2023-08-05 2:36 ` Corwin Brust
2023-08-05 6:03 ` Jim Porter
2023-08-05 6:45 ` Eli Zaretskii
2023-08-05 13:17 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-05 6:43 ` Eli Zaretskii [this message]
2024-01-10 21:49 ` Stefan Kangas
2024-01-11 19:35 ` Jim Porter
2024-01-27 20:34 ` Jim Porter
2024-01-28 2:42 ` Stefan Kangas
2024-01-28 5:46 ` Eli Zaretskii
2024-01-28 5:49 ` Stefan Kangas
2024-01-28 7:08 ` Eli Zaretskii
[not found] ` <87v8802yrp.fsf@protesilaos.com>
2024-01-11 19:38 ` Stefan Kangas
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=83r0oit2dv.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=65027@debbugs.gnu.org \
--cc=jporterbugs@gmail.com \
--cc=monnier@iro.umontreal.ca \
--cc=philipk@posteo.net \
--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).