From: Eli Zaretskii <eliz@gnu.org>
To: Ergus <spacibba@aol.com>
Cc: philipk@posteo.net, theo@thornhill.no, emacs-devel@gnu.org,
hi@ypei.me, dgutov@yandex.ru, larsi@gnus.org
Subject: Re: Adding major or popular language modes to Emacs distribution
Date: Sun, 29 Aug 2021 09:40:34 +0300 [thread overview]
Message-ID: <83fsusn47x.fsf@gnu.org> (raw)
In-Reply-To: <02B299B7-E782-409C-8147-60EA2171B684@aol.com> (message from Ergus on Sun, 29 Aug 2021 04:15:05 +0200)
> Date: Sun, 29 Aug 2021 04:15:05 +0200
> From: Ergus <spacibba@aol.com>
> CC: Eli Zaretskii <eliz@gnu.org>, hi@ypei.me
>
> Actually, it is more scalable and optimal to invest time implementing lsp and tree-sitteer building support
> because supporting more external packages and modes one by one for languages that maybe won't be
> popular after some years, so they will become unmaintained and unremovable from vanilla. Most of the code
> in the programming modes (and performance penalty) is actually dedicated to syntax highlight, indentation,
> and code navigation. Something that tree-sitee will do better and faster in most cases. Then language
> specific modes could add just some extra specific details... And we can invest then our time improving, not
> implementing basic support.
> Some external packages are also very limited and there are other external additions and plugins to make
> them functional... So adding more and more modes for languages is worthless. Use a ring to rule them all
> please.
We do have a process of obsoleting unused packages, so modes that
become unused and unmaintained have a clear path there.
Also, please don't assume that LSP and Tree Sitter will be here
forever. They can also fall out of fashion and die, at which point it
would be good for us to have some fallbacks.
Last, but not least: support for a programming language isn't limited
to what LSP, TS, and their ilk provide, it includes additional
features that are specific to Emacs. Two trivial ones:
auto-mode-alist and menu-bar items for the language. Less trivial
ones could include REPL-style invocation, support for language
interpreter, etc.
next prev parent reply other threads:[~2021-08-29 6:40 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
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 [this message]
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=83fsusn47x.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dgutov@yandex.ru \
--cc=emacs-devel@gnu.org \
--cc=hi@ypei.me \
--cc=larsi@gnus.org \
--cc=philipk@posteo.net \
--cc=spacibba@aol.com \
--cc=theo@thornhill.no \
/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).