From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Newsgroups: gmane.emacs.help Subject: Re: What is the policy for moving a feature into core or not? Date: Tue, 30 Jul 2019 09:31:15 +0200 Message-ID: <20190730073115.GA13405@tuxteam.de> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="dDRMvlgZJXvWKvBx" Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="213504"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Mutt/1.5.21 (2010-09-15) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Tue Jul 30 09:31:35 2019 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1hsMbe-000tQ9-Ue for geh-help-gnu-emacs@m.gmane.org; Tue, 30 Jul 2019 09:31:35 +0200 Original-Received: from localhost ([::1]:58514 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hsMbd-0001R1-Fb for geh-help-gnu-emacs@m.gmane.org; Tue, 30 Jul 2019 03:31:33 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:41853) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hsMbX-0001Pf-10 for help-gnu-emacs@gnu.org; Tue, 30 Jul 2019 03:31:28 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hsMbU-0001Mb-QA for help-gnu-emacs@gnu.org; Tue, 30 Jul 2019 03:31:26 -0400 Original-Received: from mail.tuxteam.de ([5.199.139.25]:51018) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hsMbU-0001GI-B6 for help-gnu-emacs@gnu.org; Tue, 30 Jul 2019 03:31:24 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=tuxteam.de; s=mail; h=From:In-Reply-To:Content-Type:MIME-Version:References:Message-ID:Subject:To:Date; bh=lumVbJ0OVsj0Z4dWVj9fWqsvYey983P8jYhp/S+paiI=; b=nQsVe97oMnhNqwihnepJR4zCE/UAe1DgFu4+rR1D/kHiAa06dEMjQ1xWFXZw0WgtjBuBnIBjouxDfky3F9i80Tz9uByLywxgFUKvvlT2gEvfrP8iTNnD1CaKSfsrjnbgXGXzu3EFv8f80m1SaYiL2qr2YCSPCefLQT7kcmX8F6OfAOBpXzxtCFPpzB140VuDdCjeSjkbuBoxCOQb3Iw0icTTeubqp/zpXB+GM/xoMyjKm+BgUC8H4dewnirR6Z+eawqq6iSbMoNJ1m8npLXuB2hHOxknPUmPAOiSC0nT2sE8+3f2M28AlpORwtDkf4bwLASjj8dno9jqyR58CKvrxw==; Original-Received: from tomas by mail.tuxteam.de with local (Exim 4.80) (envelope-from ) id 1hsMbL-0003fZ-4E for help-gnu-emacs@gnu.org; Tue, 30 Jul 2019 09:31:15 +0200 Content-Disposition: inline In-Reply-To: X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x X-Received-From: 5.199.139.25 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "help-gnu-emacs" Xref: news.gmane.org gmane.emacs.help:121258 Archived-At: --dDRMvlgZJXvWKvBx Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jul 30, 2019 at 06:20:34AM +0000, ndame wrote: > Let's take the kill ring. It's a central piece of emacs, yet I don't see = any keyboard > based solution built in to browse and search the kill ring. M-y is extrem= ely basic. There is > a menu, but it's mouse based, inefficient. >=20 > There are external packages, of course, but I wonder if there should be a= builtin way to > navigate and search the kill ring from the keyboard. By builtin I mean a = package available > from at least elpa. Hm. Doing "M-x package-list-packages" and searching there for "kill" yields= a few hits, among them: browse-kill-ring 2.0.0 available melpa-s... interactively insert item= s from kill-ring easy-kill 0.9.3 available gnu kill & mark things easily kill-ring-search 1.1 available melpa-s... incremental search for th= e kill ring (and several more; DISCLAIMER: I haven't tried any of them). Perhaps one of those could fit your needs? Or be a starting point? > Is there a current policy which governs what features are integrated into= the core (elpa)=C2=A0 > and what features are left to outside developers? The only formal hurdle is the copyright assignment papers [0] (if you want your code into Emacs or Elpa; there are alternatives). And if you trust the FSF, this hurdle is minimal. The informal hurdle is getting your stuff out there, maintaining it, and convincing people that it's worth it having a look. Easy stuff, really [1] ;-P Cheers [0] https://www.fsf.org/licensing/assigning.html/?searchterm=3Dcopyright%20= assignment [1] No, just kidding. And reminding myself of the nearly infinite debt I'm in towards the free software community. -- tom=C3=A1s --dDRMvlgZJXvWKvBx Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iEUEARECAAYFAl0/8kMACgkQBcgs9XrR2kZudQCfdS58tiantMe6W7xDDa7Xoukz a54AmI4SRo/RyPGZYpk/N1bpFEgc8p4= =tsen -----END PGP SIGNATURE----- --dDRMvlgZJXvWKvBx--