unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stephen Leake <stephen_leake@stephe-leake.org>
To: Corwin Brust <corwin@bru.st>
Cc: Justin Burkett <justin@burkett.cc>, Ergus <spacibba@aol.com>,
	Stefan Kangas <stefan@marxist.se>,
	Stefan Monnier <monnier@iro.umontreal.ca>,
	Emacs developers <emacs-devel@gnu.org>
Subject: Re: Include which-key.el in the Emacs distribution
Date: Sun, 13 Feb 2022 15:25:47 -0800	[thread overview]
Message-ID: <86leye9wn8.fsf@stephe-leake.org> (raw)
In-Reply-To: <CAJf-WoSoYmg=4OKXnNG8RPcD__oeQdRfO9KhhEi3MMnzVUUUTw@mail.gmail.com> (Corwin Brust's message of "Sun, 13 Feb 2022 12:17:20 -0600")

Corwin Brust <corwin@bru.st> writes:

> On Sun, Feb 13, 2022 at 11:59 AM Stephen Leake
> <stephen_leake@stephe-leake.org> wrote:
>>
>> Corwin Brust <corwin@bru.st> writes:
>>
>> > Hi all.  Having `which-key' available in core remains popular, at least on IRC.
>> >
>> > Now that it is available from GNU Elpa I wonder what is left to do and
>> > if there appears hope of including it with Emacs 29.
>> >
>> > Does anyone "here" have thoughts on how this may be coming along/what
>> > else is needed?
>>
>> I started on a branch to implement bundling elpa packages in the emacs
>> release; see feature/bundle-elpa, file admin/notes/elpa, and this email
>> thread on emacs-devel:
>> https://lists.gnu.org/archive/html/emacs-devel/2021-01/msg01017.html
>
> Does solving this block the possibility to include which-key, in your
> view?

The goal is to have a mechanism to easily include any ELPA package with
the Emacs release. The above is one approach to that.

> I know, at least, ERC is maintained via GNU ELPA but bundled in each
> Emacs release.  Would it make sense to look into how that's being
> done, perhaps as an interim step?

That's easy; there is a lisp/erc directory in the master emacs git
repository. Apparently someone syncs the code between there and ELPA.
There are several other packages that use that approach; which-key could
as well.

There are also "core" ELPA packages; the code resides in the emacs
master repository, but the ELPA server also packages it. I think the
only examples of those are single-file, but it should work for
multi-file as well.

-- 
-- Stephe



  reply	other threads:[~2022-02-13 23:25 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-08 13:54 Include which-key.el in the Emacs distribution Stefan Kangas
2020-09-08 14:01 ` Ergus
2020-09-08 14:16   ` Stefan Kangas
2020-09-08 17:29   ` Yuan Fu
2020-09-08 17:40     ` Justin Burkett
2020-09-08 20:40       ` Stefan Kangas
2020-09-08 16:22 ` Alfred M. Szmidt
2020-09-08 17:24   ` Eli Zaretskii
2020-09-08 17:37     ` Amin Bandali
2020-09-08 17:51       ` Alfred M. Szmidt
2020-09-08 17:54         ` Justin Burkett
2020-09-08 18:06           ` Eli Zaretskii
2020-09-08 18:11             ` Justin Burkett
2020-09-08 20:40               ` Stefan Kangas
2020-09-08 18:10           ` Alfred M. Szmidt
2020-09-08 18:00       ` Eli Zaretskii
2020-09-08 19:12         ` Amin Bandali
2020-09-08 18:25 ` Caio Henrique
2020-09-08 19:19 ` Stefan Monnier
2020-09-08 20:14   ` Ergus
2020-09-08 20:40     ` Stefan Kangas
2022-02-11 21:31       ` Corwin Brust
2022-02-13 17:30         ` Philip Kaludercic
2022-02-14  9:04           ` Pankaj Jangid
2022-02-14 16:23           ` [External] : " Drew Adams
2022-02-14 22:09           ` Tim Cross
2022-02-13 17:59         ` Stephen Leake
2022-02-13 18:17           ` Corwin Brust
2022-02-13 23:25             ` Stephen Leake [this message]
2022-02-14  2:47               ` Stefan Monnier
2022-02-14  3:09                 ` Justin Burkett
2022-02-14  3:46                   ` Corwin Brust
     [not found] <<CADwFkmmvVRqnQGA_d8bMA66SXbpjis+j-1UiceY7Lk7eY6iugA@mail.gmail.com>
     [not found] ` <<E1kFgO6-0000cE-Dj@fencepost.gnu.org>
2020-09-08 17:55   ` Drew Adams
     [not found]   ` <<83sgbskwq8.fsf@gnu.org>
2020-09-08 18:05     ` Drew Adams

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=86leye9wn8.fsf@stephe-leake.org \
    --to=stephen_leake@stephe-leake.org \
    --cc=corwin@bru.st \
    --cc=emacs-devel@gnu.org \
    --cc=justin@burkett.cc \
    --cc=monnier@iro.umontreal.ca \
    --cc=spacibba@aol.com \
    --cc=stefan@marxist.se \
    /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).