From: Eli Zaretskii <eliz@gnu.org>
To: Wilhelm Kirschbaum <wkirschbaum@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Is it worth it to add an extremely basic heex-mode and elixir-mode?
Date: Mon, 30 Dec 2024 16:20:21 +0200 [thread overview]
Message-ID: <86y0zxntga.fsf@gnu.org> (raw)
In-Reply-To: <CAOS0-35Lq==bHrKrHAwESuD4tkdQ3JNQP6kNB=pjM9gGvB_3AA@mail.gmail.com> (message from Wilhelm Kirschbaum on Mon, 30 Dec 2024 13:57:20 +0200)
> From: Wilhelm Kirschbaum <wkirschbaum@gmail.com>
> Date: Mon, 30 Dec 2024 13:57:20 +0200
>
> There is currently a heex-ts-mode and elixir-ts-mode in Emacs, but no non-ts mode equivalents. There is
> also an existing elixir-mode on MELPA https://github.com/elixir-editors/emacs-elixir but I think the
> development on it has mostly been halted ( The conversations has dried up in the elixir forums at least ).
> I don't see the existing elixir-mode going into Emacs, because there are quite a few issues and the work will
> be more than the time I or anyone I know can free up.
>
> The reason why I added the elixir-ts-mode is to have a maintainable mode for Elixir developers to use out of
> the box, this was after I tried to update the existing elixir-mode for almost a year without much success.
>
> Perhaps I can add a very basic heex- and elixir-mode so that people without the knowledge of how
> tree-sitter works can have some benefit? Any thoughts on this?
Feel free to work on such a mode, and thanks. Having a mode that
doesn't need tree-sitter means more flexibility for users, so it is
always welcome. However, whether the effort is justified (assuming
it's non-trivial) is your call.
next prev parent reply other threads:[~2024-12-30 14:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-30 11:57 Is it worth it to add an extremely basic heex-mode and elixir-mode? Wilhelm Kirschbaum
2024-12-30 14:20 ` Eli Zaretskii [this message]
2024-12-30 14:25 ` Wilhelm Kirschbaum
2025-01-02 4:37 ` Richard Stallman
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=86y0zxntga.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=wkirschbaum@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.