From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stephen Leake Newsgroups: gmane.emacs.devel Subject: Re: Include which-key.el in the Emacs distribution Date: Sun, 13 Feb 2022 15:25:47 -0800 Message-ID: <86leye9wn8.fsf@stephe-leake.org> References: <20200908201434.hrvupafbu2kyvb4q@Ergus> <86pmnqabr3.fsf@stephe-leake.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="21016"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (windows-nt) Cc: Justin Burkett , Ergus , Stefan Kangas , Stefan Monnier , Emacs developers To: Corwin Brust Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Feb 14 00:26:53 2022 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nJOGa-0005HY-Bd for ged-emacs-devel@m.gmane-mx.org; Mon, 14 Feb 2022 00:26:52 +0100 Original-Received: from localhost ([::1]:52696 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nJOGZ-0001C8-5i for ged-emacs-devel@m.gmane-mx.org; Sun, 13 Feb 2022 18:26:51 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:33708) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nJOFi-0000TV-Rw for emacs-devel@gnu.org; Sun, 13 Feb 2022 18:25:58 -0500 Original-Received: from gproxy5-pub.mail.unifiedlayer.com ([67.222.38.55]:49569 helo=progateway7-pub.mail.pro1.eigbox.com) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nJOFc-0003zh-7d for emacs-devel@gnu.org; Sun, 13 Feb 2022 18:25:58 -0500 Original-Received: from cmgw10.mail.unifiedlayer.com (unknown [10.0.90.125]) by progateway7.mail.pro1.eigbox.com (Postfix) with ESMTP id 8B60010048536 for ; Sun, 13 Feb 2022 23:25:49 +0000 (UTC) Original-Received: from host2007.hostmonster.com ([67.20.76.71]) by cmsmtp with ESMTP id JOFZnLUH1nAlUJOFZnEsed; Sun, 13 Feb 2022 23:25:49 +0000 X-Authority-Reason: nr=8 X-Authority-Analysis: v=2.4 cv=QIOt+iHL c=1 sm=1 tr=0 ts=6209937d a=dWLzHQi6WpdymmZIwiVdBw==:117 a=HlCpoMJyzbfmKqni6+j5Yg==:17 a=dLZJa+xiwSxG16/P+YVxDGlgEgI=:19 a=oGFeUVbbRNcA:10:nop_rcvd_month_year a=vvvmwbhNdt4A:10:endurance_base64_authed_username_1 a=9i_RQKNPAAAA:8 a=mDV3o1hIAAAA:8 a=ydJb217EkcUNxjancuIA:9 a=GWRbQ2Pfx9cA:10:demote_hacked_domain_1 a=Ev4oQ7kfJBNsvnoXShoW:22 a=_FVE-zBwftR9WsbkzFJk:22 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=stephe-leake.org; s=default; h=Content-Type:MIME-Version:Message-ID: In-Reply-To:Date:References:Subject:Cc:To:From:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=BGOAgMW6dAMstEWfRFhqVQQYYRafWAHJhsYADUicddY=; b=O9jGtQARy4FC2kb83bxVnTRyXn UKYhtK7EXy0c5kkWkg73HxvCA2jPVwRzX0ouSI2lkRB57RyIjv6ifyr5pHwkheU/oIqApLA1FwWZx bX0kd8aXeHPFBBSxVue8amZLmVKPhccInp1DWEaGwkSsUDGa2Qf2jqMiydEN17P+CsYjNZ4l/aMYY fm29W5Kg93gatcFUelo2wdA2H4Kk8kWUgpxaZGrTDiNq8uo39BFuou8xizezWjQSG1IJemSwesgE6 8U234kH7A8a0heBwuuFpRkXn65e/gGG531GGUyV0aAwlEh2BgylGQAjS5hON96m+pdGFXY4sclY/u HRwWYI8Q==; Original-Received: from 192-184-171-126.fiber.dynamic.sonic.net ([192.184.171.126]:51308 helo=Takver4) by host2007.hostmonster.com with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1nJOFY-002XB5-Sv; Sun, 13 Feb 2022 16:25:48 -0700 In-Reply-To: (Corwin Brust's message of "Sun, 13 Feb 2022 12:17:20 -0600") X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - host2007.hostmonster.com X-AntiAbuse: Original Domain - gnu.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - stephe-leake.org X-BWhitelist: no X-Source-IP: 192.184.171.126 X-Source-L: No X-Exim-ID: 1nJOFY-002XB5-Sv X-Source-Sender: 192-184-171-126.fiber.dynamic.sonic.net (Takver4) [192.184.171.126]:51308 X-Source-Auth: stephen_leake@stephe-leake.org X-Email-Count: 4 X-Source-Cap: c3RlcGhlbGU7c3RlcGhlbGU7aG9zdDIwMDcuaG9zdG1vbnN0ZXIuY29t X-Local-Domain: yes Received-SPF: pass client-ip=67.222.38.55; envelope-from=stephen_leake@stephe-leake.org; helo=progateway7-pub.mail.pro1.eigbox.com X-Spam_score_int: -16 X-Spam_score: -1.7 X-Spam_bar: - X-Spam_report: (-1.7 / 5.0 requ) BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=no autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:286225 Archived-At: Corwin Brust writes: > On Sun, Feb 13, 2022 at 11:59 AM Stephen Leake > wrote: >> >> Corwin Brust 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