From: "Óscar Fuentes" <ofv@wanadoo.es>
To: ndame <emacsuser@freemail.hu>
Cc: "help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Subject: Re: What is the policy for moving a feature into core or not?
Date: Sat, 14 Dec 2019 15:05:38 +0100 [thread overview]
Message-ID: <87woaz9f4d.fsf@telefonica.net> (raw)
In-Reply-To: <Axu6xw.KYGaop2LyO8.2WJYvl9GYwbYFYIyHAFx@freemail.hu> (ndame's message of "Tue, 30 Jul 2019 06:20:34 +0000 (GMT)")
ndame <emacsuser@freemail.hu> writes:
> 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 extremely 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 builtin way to
> navigate and search the kill ring from the keyboard. By builtin I mean a package available
> from at least elpa.
Elpa has undo-tree.
> Is there a current policy which governs what features are integrated into the core (elpa)
> and what features are left to outside developers?
Elpa is not core. Anyone can contribute a package to Elpa as long as it
meets certain quality and legal requirements. It is relatively easy and
painless.
Contributions to core Emacs must meet much more strict quality and
usability requirements. Typically, long discussions ensue even for
apparently trivial details.
BTW, I'm not an Emacs maintainer. This is what I learnt after years of
observing the community.
next prev parent reply other threads:[~2019-12-14 14:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-30 6:20 What is the policy for moving a feature into core or not? ndame
2019-07-30 7:31 ` tomas
2019-12-14 11:29 ` Emanuel Berg via Users list for the GNU Emacs text editor
2019-12-14 12:30 ` Óscar Fuentes
2019-12-14 14:05 ` Óscar Fuentes [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-07-30 11:58 ndame
2019-07-30 13:31 ` tomas
2019-07-30 13:59 ` John Yates
2019-07-30 14:34 ` Stefan Monnier
2019-08-03 17:45 ` Emanuel Berg
2019-08-04 13:05 ` Stefan Monnier
2019-07-30 14:10 ndame
2019-07-30 14:13 ` tomas
2019-07-30 14:53 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87woaz9f4d.fsf@telefonica.net \
--to=ofv@wanadoo.es \
--cc=emacsuser@freemail.hu \
--cc=help-gnu-emacs@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.