From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: ndame Newsgroups: gmane.emacs.help Subject: What is the policy for moving a feature into core or not? Date: Tue, 30 Jul 2019 06:20:34 +0000 (GMT) Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="193757"; mail-complaints-to="usenet@blaine.gmane.org" 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 08:28:18 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 1hsLcQ-000x0E-Cs for geh-help-gnu-emacs@m.gmane.org; Tue, 30 Jul 2019 08:28:18 +0200 Original-Received: from localhost ([::1]:58244 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hsLcO-0003EF-RL for geh-help-gnu-emacs@m.gmane.org; Tue, 30 Jul 2019 02:28:16 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:56405) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hsLcG-0003Dx-RA for help-gnu-emacs@gnu.org; Tue, 30 Jul 2019 02:28:09 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hsLcF-0000Z4-RA for help-gnu-emacs@gnu.org; Tue, 30 Jul 2019 02:28:08 -0400 Original-Received: from fmfe23.onbox.hu ([46.107.16.228]:52785 helo=web-out.onbox.hu) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1hsLcF-0000St-8h for help-gnu-emacs@gnu.org; Tue, 30 Jul 2019 02:28:07 -0400 X-fm-smtp-source: yes Original-Received: from localhost (localhost [62.165.214.82]) by web-out.onbox.hu (Postfix) with SMTP id 45yRSZ17xyzs05 for ; Tue, 30 Jul 2019 08:27:58 +0200 (CEST) X-AccountId: 57978162 X-Originating-Ip: 62.165.214.82 X-VR-SPAMSTATE: OK X-VR-SPAMSCORE: 0 X-VR-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrgeduvddrledvgddutdejucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuggftfghnshhusghstghrihgsvgdpucfhtffggffotefknfenuceurghilhhouhhtmecufedttdenucenucfjughrpeffhffkufggtgfvihesrgdtregstddtudenucfhrhhomhepnhgurghmvgcuoegvmhgrtghsuhhsvghrsehfrhgvvghmrghilhdrhhhuqeenucfkphepiedvrdduieehrddvudegrdekvdenucfrrghrrghmpehhvghloheppdhinhgvthepiedvrdduieehrddvudegrdekvddpmhgrihhlfhhrohhmpegvmhgrtghsuhhsvghrsehfrhgvvghmrghilhdrhhhupdhrtghpthhtohephhgvlhhpqdhgnhhuqdgvmhgrtghssehgnhhurdhorhhgnecuvehluhhsthgvrhfuihiivgeptd DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=simple/relaxed; t=1564468078; s=20181004; d=freemail.hu; h=Date:From:Message-ID:Subject:MIME-Version:Content-Type:To; l=1550; bh=7rl1pPx2lqJl6CUxCKTOT8cr9dr55GXpKyhu/el1xmc=; b=1PmT1zE2UYCSp2XTn/qe5h6fa5nnzfd0xCx+Y74TSs6Bok2TQ+X9R8hW2p0kdtG/ SdShIb9a9Cx0IPCC8qlZ8TMxICO1iC4r9B91KsGpMRHIIqKJptigkISZVk/kTUmvo5p wYf+eti7RxHYIIT24TXD3k6bLhuo42e48ngCUj867H2mHSHjDRcC4oLdVpf8K8Qlo6e Vy+XuzbLPkjXErLbtxw6DFy3DEbFOECpJekJs3T4JhaB3gNFV6tJz7yEGitqY/hPSEd Wkji2MhpNjO/p4XNm7wLDKllBlEeqp6+fZynreVHji6pp2dCJOj+NRilJ5eDiThRtZS 1pIVl4mD9w== X-detected-operating-system: by eggs.gnu.org: FreeBSD 9.x [fuzzy] X-Received-From: 46.107.16.228 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 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:122045 Let's take the kill ring. It's a central piece of emacs, yet I don't see an= y keyboard based solution built in to browse and search the kill ring. M-y is extremel= y basic. There is a menu, but it's mouse based, inefficient. There are external packages, of course, but I wonder if there should be a b= uiltin way to navigate and search the kill ring from the keyboard. By builtin I mean a pa= ckage available from at least elpa. Is there a current policy which governs what features are integrated into t= he core (elpa)=C2=A0 and what features are left to outside developers?