all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Corwin Brust <corwin@bru.st>
To: Jim Porter <jporterbugs@gmail.com>
Cc: philipk@posteo.net, 65027@debbugs.gnu.org, info@protesilaos.com,
	Stefan Kangas <stefankangas@gmail.com>,
	Eli Zaretskii <eliz@gnu.org>,
	Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#65027: 30.0.50; [PATCH] Document .elpaignore behavior in the Emacs Lisp manual
Date: Tue, 5 Sep 2023 21:22:18 -0500	[thread overview]
Message-ID: <CAJf-WoQ-=ffPyp=pRcZN9Vym_cCvOt+wTXTK8ficR_wVOS6d0g@mail.gmail.com> (raw)
In-Reply-To: <992e75c0-32f1-c5bc-e7bd-00c4af5d875d@gmail.com>

On Tue, Sep 5, 2023 at 8:56 PM Jim Porter <jporterbugs@gmail.com> wrote:
>
> In another subthread for this bug, we'd discussed making a *new* manual
> that discusses ELPA and/or creating packages for Emacs in general. If we
> want to create such a manual, I think that's the place my patch should
> go. However, I'm not sure what the status is on that; I have time to
> help out with it, but not enough time to write a whole manual myself.
>
> I CCed some of the people discussing this into this subthread too.
>

I'm (still) interested in working on this.  I haven't had another
offline discussion on this since I last replied in.

Key points I observed from that thread were (1) preference for
Packaging (not ELPA) as central topic, (2) expectation that we clearly
define rules for where to put things, especially WRT to moving things
already within some existing manual.

My thoughts are in the direction of working on a "mission statement"
and outline, as next steps.  I hope having an outline will help make
it possible to combine efforts from several contributors, there
probably are not many people with time to sit down and write a whole
manual :)

BTW, just in case Someone™ dies have time for this (and would find
this easies to work on if left more greenfield), it won't hurt my
feelings to have a "straw-dog" to discuss from, rather than starting
from an outline and ground-rules, as I'm suggesting/assuming.





  reply	other threads:[~2023-09-06  2:22 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 [this message]
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='CAJf-WoQ-=ffPyp=pRcZN9Vym_cCvOt+wTXTK8ficR_wVOS6d0g@mail.gmail.com' \
    --to=corwin@bru.st \
    --cc=65027@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=info@protesilaos.com \
    --cc=jporterbugs@gmail.com \
    --cc=monnier@iro.umontreal.ca \
    --cc=philipk@posteo.net \
    --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 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.