all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: Jim Porter <jporterbugs@gmail.com>
Cc: philipk@posteo.net, eliz@gnu.org, monnier@iro.umontreal.ca,
	65027@debbugs.gnu.org
Subject: bug#65027: 30.0.50; [PATCH] Document .elpaignore behavior in the Emacs Lisp manual
Date: Fri, 04 Aug 2023 21:58:43 -0400	[thread overview]
Message-ID: <E1qS6Z1-00042J-Qk@fencepost.gnu.org> (raw)
In-Reply-To: <e1299ef1-9313-9ad0-1909-2b63c46e4d92@gmail.com> (message from Jim Porter on Thu, 3 Aug 2023 10:24:58 -0700)

[[[ 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. ]]]

  > Yeah, something more general that I've noticed is that as a package 
  > author, the documentation for how to make a package for GNU ELPA is 
  > split between the GNU ELPA README and the Emacs Lisp manual.

It could be an improvement to merge all that documentation into one
text and rewrite it for coherence and clarity.

  > 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 think there is no need for this material to be in the Emacs Lisp
Reference Manual.  So I suggest making a separate short manual about
adding a package to GNU ELPA.  The Emacs Lisp Reference Manual can
direct people to it.

-- 
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-08-05  1:58 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 [this message]
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
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E1qS6Z1-00042J-Qk@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=65027@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=jporterbugs@gmail.com \
    --cc=monnier@iro.umontreal.ca \
    --cc=philipk@posteo.net \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.