From: Drew Adams <drew.adams@oracle.com>
To: bruce.connor.am@gmail.com, emacs-devel <emacs-devel@gnu.org>
Subject: RE: Customizable modes and package.el
Date: Mon, 30 Mar 2015 10:09:51 -0700 (PDT) [thread overview]
Message-ID: <461a15b7-6e18-4ffc-b059-d1decc25275c@default> (raw)
In-Reply-To: <CAAdUY-+_qJqN_xiR3jKofLRp7DSDK1V6yFdbPh7q_EV5jHj3CQ@mail.gmail.com>
> > > `package-initialize' could look into some file like
> > > ~/.emacs.d/package-init.el and load that before initializing.
> >
> > Please, not Yet Another File That Changes Emacs' Behaviour
> The file would not exist unless the user manually created it.
> I'm not thrilled at this solution, and I'm open to alternatives,
> but we have to do something.
This thread was started with a question about using Customize
instead of requiring users to put Lisp code in their init files.
The user asked, "What did I do wrong?" The answer is apparently
that Emacs is not yet ready for you to use Customize to configure
your use of package.el.
That's what should be done, IMO, whether now or later: enable
users to configure their use of package.el using Customize,
without resorting to Lisp in init files.
If for some reason that is not possible for all use cases, it
should still be a goal for the most common use cases.
I'd be among the first to say that good use of Emacs is very
much about making use of Emacs Lisp, but do we need to force
users to put code in their init files in order to make good use
of the package system?
next prev parent reply other threads:[~2015-03-30 17:09 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-28 8:58 Customizable modes and package.el Sebastian Wiesner
2015-03-28 9:30 ` Philipp Stephani
2015-03-28 12:26 ` Stefan Monnier
2015-03-28 14:59 ` Sebastian Wiesner
2015-03-28 17:55 ` Artur Malabarba
2015-03-28 20:42 ` Stefan Monnier
2015-03-29 14:48 ` Artur Malabarba
2015-03-30 0:41 ` Stefan Monnier
2015-03-30 7:05 ` Artur Malabarba
2015-03-30 13:39 ` Stefan Monnier
2015-03-30 14:31 ` Artur Malabarba
2015-03-30 14:55 ` Robert Pluim
2015-03-30 16:07 ` Artur Malabarba
2015-03-30 17:09 ` Drew Adams [this message]
2015-03-30 17:28 ` Stefan Monnier
2015-11-08 3:26 ` David Reitter
2015-11-08 3:43 ` Kaushal Modi
2015-11-08 4:33 ` Drew Adams
2015-11-08 10:48 ` Artur Malabarba
2015-11-08 10:50 ` Artur Malabarba
2015-03-30 17:45 ` Achim Gratz
2015-04-18 1:52 ` Ted Zlatanov
2015-04-18 4:30 ` Stefan Monnier
2015-04-18 4:46 ` Artur Malabarba
2015-03-30 19:06 ` Artur Malabarba
2015-03-30 20:36 ` Stefan Monnier
2015-03-31 20:14 ` João Távora
-- strict thread matches above, loose matches on Subject: below --
2015-04-18 8:36 Richard Y. Kim
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=461a15b7-6e18-4ffc-b059-d1decc25275c@default \
--to=drew.adams@oracle.com \
--cc=bruce.connor.am@gmail.com \
--cc=emacs-devel@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 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).