From: Eli Zaretskii <eliz@gnu.org>
To: Arthur Miller <arthur.miller@live.com>
Cc: philipk@posteo.net, hi@ypei.me, emacs-devel@gnu.org
Subject: Re: Adding major or popular language modes to Emacs distribution
Date: Sat, 28 Aug 2021 18:09:59 +0300 [thread overview]
Message-ID: <83pmtxmwqg.fsf@gnu.org> (raw)
In-Reply-To: <AM9PR09MB49777DFB503A31BDF63816EA96C99@AM9PR09MB4977.eurprd09.prod.outlook.com> (message from Arthur Miller on Sat, 28 Aug 2021 17:03:10 +0200)
> From: Arthur Miller <arthur.miller@live.com>
> Cc: Philip Kaludercic <philipk@posteo.net>, hi@ypei.me, emacs-devel@gnu.org
> Date: Sat, 28 Aug 2021 17:03:10 +0200
>
> What I was thinking of is that some of prog modes that ship with Emacs are
> frankly not very good compared to external packages, and people are anyway
> downloading something else (for exapel js vs js2 or lisp vs slime/sly). It would
> be nice if everything was in Emacs by default but, maybe it is better to lessen
> the burden on Emacs devs themselves and point users to external package instead.
Lessening the maintenance burden is not the most important goal of
Emacs development; providing users with better support for their
editing jobs is more important.
I don't think anyone will disagree that Emacs should support JS OOTB.
> Now that we have non gnu elpa, and Stefan says it is no problem to ship someone
> elses packages, maybe some good soul could package those into non gnu elpa and
> Emacs could do like some other text editors, simply point users to download
> needed package or download it on demand?
>
> There was no non gnu elpa before, maybe you could revise the policy in that
> light?
Non-GNU ELPA is not part of the equation, because packages put there
will probably never be able to become part of Emacs. The issue at
hand here is whether to have packages that support important features
in GNU ELPA or in core.
next prev parent reply other threads:[~2021-08-28 15:09 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-27 23:04 Adding major or popular language modes to Emacs distribution Yuchen Pei
2021-08-27 23:12 ` Philip Kaludercic
2021-08-27 23:31 ` Yuchen Pei
2021-08-28 2:38 ` Arthur Miller
2021-08-28 6:47 ` Eli Zaretskii
2021-08-28 11:34 ` Qiantan Hong
2021-08-28 11:52 ` Eli Zaretskii
2021-08-28 13:14 ` Stefan Monnier
2021-08-28 13:37 ` Eli Zaretskii
2021-08-28 13:42 ` Dmitry Gutov
2021-08-28 13:49 ` Eli Zaretskii
2021-08-28 14:16 ` Dmitry Gutov
2021-08-28 14:37 ` Eli Zaretskii
2021-08-28 14:46 ` Dmitry Gutov
2021-08-28 15:01 ` Eli Zaretskii
2021-08-28 14:59 ` Lars Ingebrigtsen
2021-08-28 15:03 ` Eli Zaretskii
2021-08-28 6:24 ` Eli Zaretskii
2021-08-28 13:45 ` Philip Kaludercic
2021-08-28 13:56 ` Eli Zaretskii
2021-08-28 14:30 ` Philip Kaludercic
2021-08-28 14:40 ` Eli Zaretskii
2021-08-28 14:45 ` Theodor Thornhill
2021-08-28 14:58 ` Eli Zaretskii
2021-08-28 15:03 ` Arthur Miller
2021-08-28 15:09 ` Eli Zaretskii [this message]
2021-08-28 15:32 ` Philip Kaludercic
2021-08-28 15:53 ` Lars Ingebrigtsen
2021-08-28 16:28 ` Theodor Thornhill
2021-08-28 20:40 ` Dmitry Gutov
2021-08-29 2:15 ` Ergus
2021-08-29 6:40 ` Eli Zaretskii
2021-08-28 16:55 ` Arthur Miller
2021-08-28 17:02 ` Theodor Thornhill
2021-08-28 6:21 ` 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
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=83pmtxmwqg.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=arthur.miller@live.com \
--cc=emacs-devel@gnu.org \
--cc=hi@ypei.me \
--cc=philipk@posteo.net \
/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).