From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.help Subject: Re: What is the policy for moving a feature into core or not? Date: Tue, 30 Jul 2019 10:34:04 -0400 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="154966"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) 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 16:34:36 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 1hsTD1-000eAo-OZ for geh-help-gnu-emacs@m.gmane.org; Tue, 30 Jul 2019 16:34:35 +0200 Original-Received: from localhost ([::1]:33556 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hsTD0-0003RD-Fr for geh-help-gnu-emacs@m.gmane.org; Tue, 30 Jul 2019 10:34:34 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:34444) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hsTCq-0003Q8-Te for help-gnu-emacs@gnu.org; Tue, 30 Jul 2019 10:34:26 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hsTCo-0002Tq-NT for help-gnu-emacs@gnu.org; Tue, 30 Jul 2019 10:34:24 -0400 Original-Received: from 195-159-176-226.customer.powertech.no ([195.159.176.226]:40178 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1hsTCn-0002SL-7B for help-gnu-emacs@gnu.org; Tue, 30 Jul 2019 10:34:22 -0400 Original-Received: from list by blaine.gmane.org with local (Exim 4.89) (envelope-from ) id 1hsTCe-000dkJ-FR for help-gnu-emacs@gnu.org; Tue, 30 Jul 2019 16:34:12 +0200 X-Injected-Via-Gmane: http://gmane.org/ Cancel-Lock: sha1:Ve8GR0hQAHZFqpEgb9dsDCALIyQ= X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 195.159.176.226 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:121266 Archived-At: > As I said I know about such external packages, and it was only an example. > I'm just wondering if there is policy of keeping the core (elpa included) small to > lessen the burden of emacs maintainers, or there is no such policy,  > and if people submitted the necessary papers then they could dump packages into > elpa by the thousand. For GNU ELPA specifically, there is no special policy: any package is acceptable, basically. For Emacs's core, there is no clear cut policy, but since the advent of GNU ELPA we've tried to add packages there rather than in Emacs itself, because it makes it much easier for the package to evolve at its own pace (i.e. better for the package's maintainer) and it lessens the burden for Emacs's maintainers as well. Stefan PS: Here's my own kill ring browser, which I call from `yank-pop` when the last command was not `yank`. (defun yank-browse (string) "Browse the `kill-ring' to choose which entry to yank." (interactive (minibuffer-with-setup-hook #'minibuffer-completion-help (let* ((kills (delete-dups (append kill-ring-yank-pointer kill-ring nil))) (entries (mapcar (lambda (string) (let ((pos 0)) ;; FIXME: Maybe we should start by removing ;; all properties. (setq string (copy-sequence string)) (while (string-match "\n" string pos) ;; FIXME: Maybe completion--insert-strings should ;; do that for us. (put-text-property (match-beginning 0) (match-end 0) 'display (eval-when-compile (propertize "\\n" 'face 'escape-glyph)) string) (setq pos (match-end 0))) ;; FIXME: We may use the window-width of the ;; wrong window. (when (>= (* 3 (string-width string)) (* 2 (window-width))) (let ((half (- (/ (window-width) 3) 1))) ;; FIXME: We're using char-counts rather than ;; width-count. (put-text-property half (- (length string) half) 'display (eval-when-compile (propertize "……" 'face 'escape-glyph)) string))) string)) kills)) (table (lambda (string pred action) (cond ((eq action 'metadata) '(metadata (category . kill-ring))) (t (complete-with-action action entries string pred)))))) ;; FIXME: We should return the entry from the kill-ring rather than ;; the entry from the completion-table. ;; FIXME: substring completion doesn't work well because it only matches ;; subtrings before the first \n. ;; FIXME: completion--insert-strings assumes that boundaries of ;; candidates are obvious enough, but with kill-ring entries this is not ;; true, so we'd probably want to display them with «...» around them. (list (completing-read "Yank: " table nil t))))) (setq this-command 'yank) (insert-for-yank string))