From: Stefan Kangas <stefankangas@gmail.com>
To: Alan Third <alan@idiocy.org>
Cc: Emacs developers <emacs-devel@gnu.org>, ndame <ndame@protonmail.com>
Subject: Re: Making Emacs popular again with a video
Date: Sat, 9 May 2020 08:12:14 -0700 [thread overview]
Message-ID: <CADwFkmmkGxD+nthAjQg4P0BaAT+O0go70zrM_0EuDTw7-5eWaw@mail.gmail.com> (raw)
In-Reply-To: <20200509132808.GA42734@breton.holly.idiocy.org>
Alan Third <alan@idiocy.org> writes:
>> IMHO, we should not promote third-party "init files" as a primary
>> option, but rather improve Emacs itself.
>
> Maybe we should embrace them, and provide tools to build custom Emacs
> distributions.
Perhaps I was being unclear. What I don't like is the suggestion that
we should just tell people to go to website X to download and install
a bunch of init files.
I think we could provide some _variant_ of what these distributions are
doing, namely sets of ready-made customization. The question is how to
go about it.
I've been thinking a lot about this problem, but I have not had time to
do any serious work. So please consider these ideas as tentative:
I would propose to add a concept of "custom profiles" (or simply
"profiles"), which are basically defthemes. Please see the separate
(brief) discussion about this here, and also the related thread:
https://lists.gnu.org/archive/html/emacs-devel/2020-04/msg02032.html
One can imagine these "profiles" to be big distributions like spacemacs,
or (perhaps better) small snippets or sets of customization. Some of
these could/should be included in Emacs by default.
One can also imagine there being one profile providing "good defaults
for a new user".[1] Maybe such a profile could be the default at some
point in the future, but this is IMHO better discussed and decided once
it actually exists.
Best regards,
Stefan Kangas
Footnotes:
[1] Eli has pointed out that the biggest hurdle is to decide what such a
"profile" (in my terminology) should include.
next prev parent reply other threads:[~2020-05-09 15:12 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 [this message]
2020-05-09 19:53 ` Stefan Monnier
-- 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
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=CADwFkmmkGxD+nthAjQg4P0BaAT+O0go70zrM_0EuDTw7-5eWaw@mail.gmail.com \
--to=stefankangas@gmail.com \
--cc=alan@idiocy.org \
--cc=emacs-devel@gnu.org \
--cc=ndame@protonmail.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).