From: Kaushal Modi <kaushal.modi@gmail.com>
To: "João Távora" <joaotavora@gmail.com>,
"David Kastrup" <dak@gnu.org>,
"Juanma Barranquero" <lekktu@gmail.com>,
"Emacs developers" <emacs-devel@gnu.org>,
"Oleh Krehel" <ohwoeowho@gmail.com>,
"Dmitry Gutov" <dgutov@yandex.ru>
Subject: Re: use-package.el -> Emacs core
Date: Tue, 10 Nov 2015 10:56:08 -0500 [thread overview]
Message-ID: <CAFyQvY0fHvPPYvCodBsop9XFgzXz7FtqeCGt_s5Ki263jWSwWA@mail.gmail.com> (raw)
In-Reply-To: <m2twothox7.fsf@Vulcan.attlocal.net>
I would also fit in the cautious category, leaning towards against
(see below for what I mean).
My biggest concern is the duplication and confusion for end-user code.
define-key vs bind-key. As João mentioned in a different context, I
feel this kind of syntactic sugar is probably not OK for end-user
code; providing many options increases the complexity when debugging
code for the user and the maintainer.
My suggestion would be to first merge bind-key into define-key and
sister defuns/macros. If that is feasible, then we can think if
use-package can be merged.
Biggest concerns with bind-key
(1) Plain bind-key macro is not very much different for define-key or
global-set key. I believe its addition is not necessary in the core.
(2) bind-key*, bind-keys, bind-keys* would be good additions but
should they be refactored as define-key* (while retaining the original
define-key arg order) + global-set-key*, define-keys and define-keys*?
(3) How would describe-personal-bindings work? Because if bind-key is
made part of the core, we cannot control which internal package makes
use of it. Write now the only way we know that the user
added/redefined a key is if they made use of one of the bind-key
macros. That luxury will go away once it is part of the core.
About use-package: I also have a opinion that the user will understand
less of how requires, autoloads, eval-after-loads and idle timers work
if they start using use-package as the first thing.
Until we have a solid solution for the above, my vote is against for
both bind-key and use-package.
With that said, would adding bind-key and use-package to GNU Elpa be a
better option?
If we do that,
- There is no concern of duplication and confusion among users that I
mentioned above.
- Maintainers do not have to worry about the use/debug of
use-package+bind-key in the core packages.
- When helping out users debug something, the instructions for
defining keys are pretty consistent: either define-key or
global-set-key (usually the latter) vs the options of
define-key/global-set-key/bind-key/bind-key*/bind-keys/bind-keys*
- Also only the users who know what they are doing would install these packages.
- use-package + bind-key would still reach a wider user-base as not
all users add Melpa to package-archives
next prev parent reply other threads:[~2015-11-10 15:56 UTC|newest]
Thread overview: 95+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-10 0:02 use-package.el -> Emacs core John Wiegley
2015-11-10 0:14 ` Dmitry Gutov
2015-11-10 0:31 ` John Wiegley
2015-11-10 0:40 ` Dmitry Gutov
2015-11-10 7:55 ` Oleh Krehel
2015-11-10 11:52 ` Juanma Barranquero
2015-11-10 12:10 ` Oleh Krehel
2015-11-10 12:23 ` Juanma Barranquero
2015-11-10 12:40 ` Oleh Krehel
2015-11-10 12:47 ` Juanma Barranquero
2015-11-10 15:15 ` John Wiegley
2015-11-10 15:42 ` Juanma Barranquero
2015-11-10 15:56 ` Dmitry Gutov
2015-11-11 0:37 ` Stephen Leake
2015-11-11 0:56 ` Juanma Barranquero
2015-11-10 15:55 ` João Távora
2015-11-10 16:08 ` John Wiegley
2015-11-10 16:23 ` Drew Adams
2015-11-10 14:03 ` David Kastrup
2015-11-10 14:15 ` Oleh Krehel
2015-11-10 14:22 ` João Távora
2015-11-10 15:17 ` John Wiegley
2015-11-10 15:46 ` João Távora
2015-11-10 18:15 ` John Wiegley
2015-11-10 19:32 ` João Távora
2015-11-10 19:47 ` John Wiegley
2015-11-10 21:00 ` João Távora
2015-11-10 15:56 ` Kaushal Modi [this message]
2015-11-10 18:20 ` John Wiegley
2015-11-10 18:32 ` Drew Adams
2015-11-10 18:38 ` John Wiegley
2015-11-10 18:52 ` Kaushal Modi
2015-11-10 18:55 ` John Wiegley
2015-11-10 19:24 ` Drew Adams
2015-11-10 19:35 ` John Wiegley
2015-11-10 20:42 ` Drew Adams
2015-11-10 12:42 ` Kaushal Modi
2015-11-10 12:46 ` David Kastrup
2015-11-10 13:06 ` Oleh Krehel
2015-11-10 18:15 ` Evgeny Panasyuk
2015-11-10 18:31 ` Alan Mackenzie
2015-11-10 13:32 ` Wolfgang Jenkner
2015-11-10 15:08 ` Customize is only for newbies? [was: use-package.el -> Emacs core] Drew Adams
2015-11-11 0:01 ` Wolfgang Jenkner
2015-11-10 14:58 ` Drew Adams
2015-11-10 15:42 ` John Wiegley
2015-11-10 8:49 ` use-package.el -> Emacs core João Távora
2015-11-10 8:57 ` Pedro Silva
2015-11-10 9:45 ` João Távora
2015-11-10 12:01 ` Phillip Lord
2015-11-10 13:37 ` João Távora
2015-11-10 14:07 ` Oleh Krehel
2015-11-10 14:39 ` Nicolas Richard
2015-11-10 14:48 ` João Távora
2015-11-10 15:40 ` John Wiegley
2015-11-12 12:43 ` Nicolas Richard
2015-11-10 17:36 ` Phillip Lord
2015-11-10 0:44 ` Artur Malabarba
2015-11-10 1:05 ` John Wiegley
2015-11-10 1:24 ` Artur Malabarba
2015-11-10 1:37 ` John Wiegley
2015-11-10 3:20 ` Artur Malabarba
2015-11-10 5:37 ` Kaushal Modi
2015-11-10 6:07 ` John Wiegley
2015-11-10 23:27 ` Stephen Leake
2015-11-10 23:32 ` John Wiegley
2015-11-11 9:29 ` Oleh Krehel
2015-11-11 16:48 ` John Wiegley
2015-11-11 20:04 ` Kaushal Modi
2015-11-11 20:10 ` John Wiegley
2015-11-12 2:11 ` Copyright assignments in Gnu Elpa (was: use-package.el -> Emacs core) Michael Heerdegen
2015-11-12 2:19 ` Copyright assignments in Gnu Elpa John Wiegley
2015-11-12 3:50 ` Artur Malabarba
2015-11-12 22:31 ` Copyright assignments in Gnu Elpa (was: use-package.el -> Emacs core) Richard Stallman
2015-11-15 14:51 ` Copyright assignments in Gnu Elpa Andreas Röhler
2015-11-16 19:30 ` Richard Stallman
2015-11-10 1:37 ` use-package.el -> Emacs core Ted Zlatanov
2015-11-10 8:24 ` joakim
2015-11-11 0:29 ` Stephen Leake
2015-11-11 0:45 ` Dmitry Gutov
2015-11-11 9:30 ` Stephen Leake
2015-11-11 10:04 ` Xue Fuqiao
2015-11-11 10:20 ` Artur Malabarba
2015-11-10 8:44 ` Andreas Röhler
2015-11-10 9:29 ` Nicolas Petton
2015-11-11 0:32 ` Stephen Leake
2015-11-11 0:37 ` John Wiegley
2015-11-10 18:21 ` Stephen Leake
2015-11-10 18:34 ` John Wiegley
2015-11-10 19:54 ` Dmitry Gutov
2015-11-10 20:09 ` Kaushal Modi
2015-11-10 20:27 ` John Wiegley
2015-11-11 0:04 ` Stephen Leake
-- strict thread matches above, loose matches on Subject: below --
2017-02-15 19:49 Toon Claes
2017-02-15 19:51 ` John Wiegley
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAFyQvY0fHvPPYvCodBsop9XFgzXz7FtqeCGt_s5Ki263jWSwWA@mail.gmail.com \
--to=kaushal.modi@gmail.com \
--cc=dak@gnu.org \
--cc=dgutov@yandex.ru \
--cc=emacs-devel@gnu.org \
--cc=joaotavora@gmail.com \
--cc=lekktu@gmail.com \
--cc=ohwoeowho@gmail.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).