From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Jeremy Bryant Newsgroups: gmane.emacs.devel Subject: Re: Moving which-key ELPA package into core - Re: discoverability, better defaults and which-key in Emacs Date: Sun, 04 Feb 2024 22:12:20 +0000 Message-ID: <87o7cvub53.fsf@jeremybryant.net> References: <874jetaxri.fsf@jeremybryant.net> <86fryc1vsh.fsf@gnu.org> <87y1c398u8.fsf@jeremybryant.net> <867cjnz7rc.fsf@gnu.org> <87r0ht7p77.fsf@jeremybryant.net> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="35279"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Eli Zaretskii , Stefan Kangas , Philip Kaludercic , Philip Kaludercic , justin@burkett.cc, emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Feb 04 23:18:56 2024 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 1rWkpB-0008tL-UW for ged-emacs-devel@m.gmane-mx.org; Sun, 04 Feb 2024 23:18:54 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rWkoW-00067Z-DT; Sun, 04 Feb 2024 17:18:12 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rWkoU-00067I-Ro for emacs-devel@gnu.org; Sun, 04 Feb 2024 17:18:11 -0500 Original-Received: from out-179.mta0.migadu.com ([2001:41d0:1004:224b::b3]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rWkoS-0000T1-Dq for emacs-devel@gnu.org; Sun, 04 Feb 2024 17:18:10 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jeremybryant.net; s=key1; t=1707085084; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=wmEexRq+xqEAVoI86ni4m2NR47mnQ8S+8cZ/5Hyxqb4=; b=hi/fk9w2Z+4GyNSrf/DuwdT5Hdn2r4x8swmiN31JNJn5WiX2l9eQeXoElcbomiNoOShxKr /laeUVt4Nv7045F4ALZayCgWf5NWxdg5LcM0tP1xQpFTKZZjQzpxiVQQlu8kNTw7U53gPg t98PkG1G+bJdJyeoLHQOsHUkLcJzD9V61dEoY3zRN85P6y9wggKZBTXEMtXXQE3YiJwWMc oDtyLfzRwB7RaLN6poClZCFYWxhk8RhUVp4FNdJIdMfDkGgMKMnlzq9xXRkSC6DZxOvz6r 8ZMpQek5DwEyHI/Fbha+xeR4eD2qhSNaBH+HGP+iCGRhbJqvi41neSAuv8iJww== X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. In-reply-to: X-Migadu-Flow: FLOW_OUT Received-SPF: pass client-ip=2001:41d0:1004:224b::b3; envelope-from=jb@jeremybryant.net; helo=out-179.mta0.migadu.com X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham 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-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:315868 Archived-At: Stefan Monnier writes: >>>> Move the .el files from the ELPA package into lisp/ ? >>>> Manual entry- ? >>> Something like that. Philip and Stefan will be able to describe the >>> details. >> Philip, Stefan, kindly provide some guidance on what work is needed? > > There's no predefined way to do it. The details depend on what you/we > care about (e.g. do we want to keep updating the GNU ELPA `which-key` > package in the future? If so, do we want to do that by having > a separate upstream from which we "pull" both into `elpa.git` and > `emacs.git` or do we prefer to generate the GNU ELPA package directly > out of the `emacs.git` code? ...). > > And most of it can be figured out along the way (i.e. fixed after the > fact), so I'd say to "just do it" and fix the problems you see as they > come up. > > > Stefan Thank you, based on this, I have submitted a patch as bug #68929 If, as appears in the original email, the package is no longer maintained upstream, it could be maintained in emacs.git