all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Jim Porter <jporterbugs@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>, Eli Zaretskii <eliz@gnu.org>
Cc: philipk@posteo.net, 65027@debbugs.gnu.org
Subject: bug#65027: 30.0.50; [PATCH] Document .elpaignore behavior in the Emacs Lisp manual
Date: Thu, 3 Aug 2023 10:24:58 -0700	[thread overview]
Message-ID: <e1299ef1-9313-9ad0-1909-2b63c46e4d92@gmail.com> (raw)
In-Reply-To: <jwvsf908d87.fsf-monnier+emacs@gnu.org>

On 8/3/2023 6:36 AM, Stefan Monnier via Bug reports for GNU Emacs, the 
Swiss army knife of text editors wrote:
>>>   From the discussion in bug#64985, Eli mentioned that .elpaignore wasn't
>>> documented. (It turns out it's mentioned briefly in the GNU ELPA README,
>>> but that's the only place I could find.)
> 
> That's because it was the only place where `.elpaignore` was used/obeyed
> (until the introduction of `package-vc`).

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. I found 
this a bit confusing when I prepared my first package for submission to 
GNU ELPA, so (for example) I didn't learn about ".elpaignore" until 
after I sent my package submission to emacs-devel.

Maybe it would make sense to put all the documentation in the Emacs Lisp 
manual, and then the GNU ELPA README can be the home for documentation 
about how to work with the GNU ELPA repository specifically (mainly as 
an administrator). What do you think?





  reply	other threads:[~2023-08-03 17:24 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 [this message]
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
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=e1299ef1-9313-9ad0-1909-2b63c46e4d92@gmail.com \
    --to=jporterbugs@gmail.com \
    --cc=65027@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --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.