From: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
To: emacs-devel <emacs-devel@gnu.org>
Subject: Re: Re: Make all tree-sitter modes optional
Date: Thu, 19 Jan 2023 17:53:06 +0100 [thread overview]
Message-ID: <CAO48Bk96RNgrzL9F+VNxaUUCk2y6Vk5M1XP4Py4epOB1shN9Ew@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1327 bytes --]
Hi
Disclaimer: no intention to start a flame war, please...
Now: My experience in the last couple of weeks is that there are
tree-sitter modes in the Emacs tree that have non-ts counterparts in MELPA
only. And that's been frustrating. Basically because I don't compile ts
support and despite that, the treesit .el files are installed and used.
Example: dockerfile-mode is in MELPA only. So when I recently opened a
Dockerfile, I got an error saying that Dockerfile-ts-mode couldn't start
because my emacs hasn't ts support compiled in.
I would have prefered to see the dockerfile opened in text mode with no
errors. And then, when I install the Dockerfile-mode package from MELPA,
start working with all the goodies I got from installing the package from
MELPA.
My gut feeling is that if I don't have treesit support compiled in Emacs, I
don't want *-ts-*.el files in my elisp tree nor any side effects related to
these files. Sorry to say, but I feel that the enthusiasm about treesit
some have is a bit pushing for me. And I feel uncomfortable when pushed.
Thanks, /PA
--
Fragen sind nicht da um beantwortet zu werden,
Fragen sind da um gestellt zu werden
Georg Kreisler
Headaches with a Juju log:
unit-basic-16: 09:17:36 WARNING juju.worker.uniter.operation we should run
a leader-deposed hook here, but we can't yet
[-- Attachment #2: Type: text/html, Size: 1713 bytes --]
next reply other threads:[~2023-01-19 16:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-19 16:53 Pedro Andres Aranda Gutierrez [this message]
2023-01-20 8:30 ` Make all tree-sitter modes optional Eli Zaretskii
2023-01-20 16:31 ` Pedro Andres Aranda Gutierrez
2023-01-20 19:13 ` Eli Zaretskii
2023-01-21 11:30 ` Pedro Andres Aranda Gutierrez
2023-01-21 11:48 ` Eli Zaretskii
2023-01-22 6:23 ` Pedro Andres Aranda Gutierrez
2023-01-22 6:38 ` Eli Zaretskii
2023-01-22 10:46 ` 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=CAO48Bk96RNgrzL9F+VNxaUUCk2y6Vk5M1XP4Py4epOB1shN9Ew@mail.gmail.com \
--to=paaguti@gmail.com \
--cc=emacs-devel@gnu.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).