From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Alan Third <alan@idiocy.org>
Cc: Emacs developers <emacs-devel@gnu.org>,
Stefan Kangas <stefankangas@gmail.com>,
ndame <ndame@protonmail.com>
Subject: Re: Making Emacs popular again with a video
Date: Sat, 09 May 2020 15:53:04 -0400 [thread overview]
Message-ID: <jwvpnbcoppy.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <20200509132808.GA42734@breton.holly.idiocy.org> (Alan Third's message of "Sat, 9 May 2020 14:28:08 +0100")
> Maybe we should embrace them, and provide tools to build custom Emacs
> distributions. Put absolutely everything that isn’t absolutely
> required for Emacs into ELPA so there’s a core Emacs that is as basic
> as it gets, then, I don’t know, use manifest files to build
> a distribution that pulls in the stuff we need from ELPA or
> wherever else.
I think we should, indeed. Sadly, I haven't found the time/energy to
dig into Doom, Spacemacs, etc... to see how we could do that in a way
that's better than what's already done.
For me "better" would mostly mean that the efforts expanded on one
distribution would "directly" carry over to another.
In an ideal world, these distributions would be basically a list of
packages that are required along with a kind of custom-theme.
And ideally, you should then be able to say you want "Spacemacs + foo -
bar" and you can later update to the latest Spacemacs and it will still
work (still removing "bar" from it and adding "foo" to it).
Stefan
next prev parent reply other threads:[~2020-05-09 19:53 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-08 10:58 Making Emacs popular again with a video ndame
2020-05-08 11:32 ` Stefan Kangas
2020-05-09 13:28 ` Alan Third
2020-05-09 15:12 ` Stefan Kangas
2020-05-09 19:53 ` Stefan Monnier [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-05-14 17:11 ndame
2020-05-14 17:48 ` Stefan Monnier
2020-05-14 19:28 ` Drew Adams
2020-05-15 3:11 ` Tim Cross
2020-05-15 3:20 ` Richard Stallman
2020-05-14 22:05 ` T.V Raman
2020-05-08 8:26 Nathan Colinet
2020-05-08 10:39 ` Arthur Miller
2020-05-10 20:48 ` Nathan Colinet
2020-05-08 10:41 ` Stefan Kangas
2020-05-10 16:18 ` Nathan Colinet
2020-05-08 11:33 ` Eli Zaretskii
2020-05-10 20:32 ` Nathan Colinet
2020-05-11 22:59 ` Stefan Kangas
2020-05-09 7:50 ` Andreas Röhler
2020-05-10 20:57 ` Nathan Colinet
2020-05-12 3:12 ` Richard Stallman
2020-05-12 7:04 ` Arthur Miller
2020-05-12 13:59 ` Dmitry Gutov
2020-05-12 14:47 ` Arthur Miller
2020-05-12 16:08 ` Drew Adams
2020-05-13 4:01 ` Richard Stallman
2020-05-13 8:49 ` Arthur Miller
2020-05-14 5:14 ` Richard Stallman
2020-05-14 10:22 ` Arthur Miller
2020-05-14 10:55 ` Robert Pluim
2020-05-15 3:25 ` Richard Stallman
2020-05-15 7:55 ` Arthur Miller
2020-05-15 10:11 ` Eli Zaretskii
2020-05-15 10:43 ` Arthur Miller
2020-05-15 11:23 ` Eli Zaretskii
2020-05-15 19:15 ` H. Dieter Wilhelm
2020-05-15 18:41 ` H. Dieter Wilhelm
2020-05-22 19:09 ` Ben McGinnes
[not found] ` <E1jcLVP-0003SB-II@fencepost.gnu.org>
2020-05-24 19:16 ` Ben McGinnes
2020-05-14 14:13 ` Eli Zaretskii
2020-05-14 7:38 ` Tim Cross
2020-05-14 7:51 ` Andreas Röhler
2020-05-14 14:18 ` Eli Zaretskii
2020-05-14 15:36 ` Tim Cross
2020-05-13 10:43 ` Stefan Kangas
2020-05-12 8:23 ` Andreas Röhler
2020-05-13 3:55 ` Richard Stallman
2020-05-13 8:18 ` Andreas Röhler
2020-05-13 10:53 ` Stefan Kangas
2020-05-13 16:20 ` Drew Adams
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=jwvpnbcoppy.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=alan@idiocy.org \
--cc=emacs-devel@gnu.org \
--cc=ndame@protonmail.com \
--cc=stefankangas@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 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.