unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Daniel Mendler via "Emacs development discussions." <emacs-devel@gnu.org>
To: Dmitry Gutov <dmitry@gutov.dev>
Cc: Philip Kaludercic <philipk@posteo.net>,
	 emacs-devel@gnu.org,
	 Stephen Leake <stephen_leake@stephe-leake.org>
Subject: Re: Ada-mode to be abandoned?
Date: Sun, 07 Jan 2024 22:02:41 +0100	[thread overview]
Message-ID: <87edeseu1a.fsf@daniel-mendler.de> (raw)
In-Reply-To: <f6427ff5-e5a4-40fa-8970-cd0f3b28ef5e@gutov.dev> (Dmitry Gutov's message of "Sun, 7 Jan 2024 22:36:45 +0200")

Dmitry Gutov <dmitry@gutov.dev> writes:

> On 07/01/2024 18:26, Philip Kaludercic wrote:
>> Dmitry <dmitry@gutov.dev> writes:
>> 
>>> On Sun, Jan 7, 2024, at 2:34 PM, Philip Kaludercic wrote:
>>>> What I am wondering, is if this simplification were to take place, if it
>>>> would be possible to add ada-mode (or ada-ts-mode in that case) back to
>>>> the core?
>>> What is this fetish of adding everything to the core?
>> For me it is usually just that it is easier for a newcomer to get stuff
>> working, without having to deal with package management, which can be a
>> bother when working offline or in isolated environments.
>
> This can be argued for just about any bit of Elisp code, but we don't want all
> the universe inside the Emacs repo, do we?

While package management may be easier, there is also a discoverability
aspect. Every added package and mode makes it a little bit more
difficult for newcomers to figure out what they want to use. Which mail
client is it going to be, which IRC client, ...? For programming
language modes the problem may not be that significant, since the modes
usually activate themselves. However the documentation still gets
inflated and one may get lost in the sea of information.

In the case of Heex I see this package header:

;;; heex-ts-mode.el --- Major mode for Heex with tree-sitter support -*- lexical-binding: t; -*-
;; ...
;; This package provides `heex-ts-mode' which is a major mode for editing
;; HEEx files that uses Tree Sitter to parse the language.

Then there is this NEWS entry:

*** New major mode 'heex-ts-mode'.
A major mode based on the tree-sitter library for editing HEEx files.

This information is not helpful for a newcomer. On the other hand if you
are already an Elixir/Heex user, it should not pose a difficulty for you
to find the appropriate packages on GNU ELPA.

Daniel



  reply	other threads:[~2024-01-07 21:02 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-07 12:34 Ada-mode to be abandoned? Philip Kaludercic
2024-01-07 14:48 ` Eli Zaretskii
2024-01-07 15:21 ` Dmitry
2024-01-07 15:25   ` Eli Zaretskii
2024-01-07 15:54     ` Dmitry
2024-01-07 16:55       ` Eli Zaretskii
2024-01-08  2:14         ` Dmitry Gutov
2024-01-08  3:36           ` Eli Zaretskii
2024-01-08 12:22             ` Eli Zaretskii
2024-01-08 12:37               ` Dmitry Gutov
2024-01-08  1:45       ` Po Lu
2024-01-07 15:34   ` Daniel Mendler via Emacs development discussions.
2024-01-07 15:45     ` Alfred M. Szmidt
2024-01-07 15:58     ` Dmitry
2024-01-07 17:52     ` Stefan Kangas
2024-01-07 16:26   ` Philip Kaludercic
2024-01-07 16:48     ` Daniel Mendler via Emacs development discussions.
2024-01-07 20:36     ` Dmitry Gutov
2024-01-07 21:02       ` Daniel Mendler via Emacs development discussions. [this message]
2024-01-07 21:27         ` Stefan Kangas
2024-01-07 22:05           ` Daniel Mendler via Emacs development discussions.
2024-01-08  3:26         ` Eli Zaretskii
2024-01-07 17:46   ` Is it better to add treesitter modes to core? Stefan Kangas
2024-01-07 21:27     ` Dmitry Gutov
2024-01-08  6:15       ` Philip Kaludercic
2024-01-08 12:46         ` Dmitry Gutov
2024-01-08 12:47         ` Eli Zaretskii
2024-01-09 19:27           ` Philip Kaludercic
2024-01-09 19:54             ` Eli Zaretskii
2024-01-09 20:21               ` Philip Kaludercic
2024-01-10  3:29                 ` Eli Zaretskii
2024-01-09  5:20       ` Stefan Kangas
2024-01-09 17:50         ` Dmitry Gutov
2024-01-09 17:54           ` Dmitry Gutov
2024-01-09 18:59           ` Stefan Kangas
2024-01-09 19:51             ` Eli Zaretskii
2024-01-09 20:06               ` Dmitry Gutov
2024-01-10  6:27                 ` Stefan Kangas
2024-01-10 11:38                   ` Dmitry Gutov
2024-01-10 12:03                     ` Stefan Kangas
2024-01-10 12:14                       ` Dmitry Gutov
2024-01-10 15:11                         ` Stefan Kangas
2024-01-10 12:35                       ` Modes in generic-x.el (was: Is it better to add treesitter modes to core?) Peter Oliver
2024-01-10 13:50                         ` Eli Zaretskii
2024-01-10 13:47                       ` Is it better to add treesitter modes to core? Eli Zaretskii
2024-01-07 16:29 ` Ada-mode to be abandoned? Fernando Oleo Blanco
2024-01-07 16:48   ` Philip Kaludercic
2024-01-07 17:22     ` Fernando Oleo Blanco

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=87edeseu1a.fsf@daniel-mendler.de \
    --to=emacs-devel@gnu.org \
    --cc=dmitry@gutov.dev \
    --cc=mail@daniel-mendler.de \
    --cc=philipk@posteo.net \
    --cc=stephen_leake@stephe-leake.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).