From: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Make all tree-sitter modes optional
Date: Sat, 21 Jan 2023 12:30:26 +0100 [thread overview]
Message-ID: <CAO48Bk8VnGPO0m-WuaJyOk41xp+H1im4YSzs0jNykeWm+rzvug@mail.gmail.com> (raw)
In-Reply-To: <83o7qtm33d.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 4321 bytes --]
Hi Eli,
Eli writes:
> Why would it confuse? You also have there stuff like w32-win.el.gz,
> which is used only on MS-Windows, and other files that are not
> necessarily for your configuration. This is not a problem, and
> shouldn't be one.
I don't know, maybe for me there is a difference between the OS specific
stuff, tree-sitter and other stuff in Emacs:
tree-sitter modes 'compete' with 'regular' modes and if I don't have
tree-sitter activated at compile time, it can be misleading to see those
files there and 'sub-optimal' (to say the least) to get a message that you
can't use them.
OS related stuff is different in the sense that, well, if I'm on a Linux
system and try to use (you say the OS)-specific features, it is natural
that I get a 'wake-up' message there and stop trying to do things that make
no sense.
As for the rest, having dormant features that _work_ (or are WIP with a
level of maturity enough to be in master) and only wait for me to test them
and activate them if they help me in my day-to-day interactions with Emacs,
of course, put 10^n n->infinity of those in Emacs, no problem.
In that sense, if there was a way to disregard *-ts-*.el files in ELC/ELN
compilation and installation when I compile Emacs _without_ tree-sitter
support, the whole picture would be (once again, IMvHO) much more coherent.
Thanks for your patience, /PA
On Fri, 20 Jan 2023 at 20:13, Eli Zaretskii <eliz@gnu.org> wrote:
> > From: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
> > Date: Fri, 20 Jan 2023 17:31:44 +0100
> > Cc: emacs-devel@gnu.org
> >
> > Thanks for that :-)
> > It's a first step. However, the *-ts-mode.el files still go through the
> .el compilation, yielding error messages
> > during the compilation.
>
> What error messages? Please show them, we cannot possibly guess what
> messages do you see.
>
> And why is it a problem that the *.el files are being compiled as part
> of the build? A build compiles all the *.el files, including ones you
> will never use and ones that you cannot use (e.g., because they are
> for Emacs running on other OSes). That is never a problem.
>
> > Additionally, they get installed in the binary distribution:
> >
> > emacs-29 ➤ find Emacs.app -name \*-ts-\*
> > Emacs.app/Contents/Resources/lisp/progmodes/c-ts-mode.el.gz
> > Emacs.app/Contents/Resources/lisp/progmodes/c-ts-mode.elc
> > Emacs.app/Contents/Resources/lisp/progmodes/cmake-ts-mode.el.gz
> > Emacs.app/Contents/Resources/lisp/progmodes/cmake-ts-mode.elc
> > Emacs.app/Contents/Resources/lisp/progmodes/dockerfile-ts-mode.el.gz
> > Emacs.app/Contents/Resources/lisp/progmodes/dockerfile-ts-mode.elc
> > Emacs.app/Contents/Resources/lisp/progmodes/go-ts-mode.el.gz
> > Emacs.app/Contents/Resources/lisp/progmodes/go-ts-mode.elc
> > Emacs.app/Contents/Resources/lisp/progmodes/java-ts-mode.el.gz
> > Emacs.app/Contents/Resources/lisp/progmodes/java-ts-mode.elc
> > Emacs.app/Contents/Resources/lisp/progmodes/json-ts-mode.el.gz
> > Emacs.app/Contents/Resources/lisp/progmodes/json-ts-mode.elc
> > Emacs.app/Contents/Resources/lisp/progmodes/ruby-ts-mode.el.gz
> > Emacs.app/Contents/Resources/lisp/progmodes/ruby-ts-mode.elc
> > Emacs.app/Contents/Resources/lisp/progmodes/rust-ts-mode.el.gz
> > Emacs.app/Contents/Resources/lisp/progmodes/rust-ts-mode.elc
> > Emacs.app/Contents/Resources/lisp/progmodes/typescript-ts-mode.el.gz
> > Emacs.app/Contents/Resources/lisp/progmodes/typescript-ts-mode.elc
> > Emacs.app/Contents/Resources/lisp/textmodes/toml-ts-mode.el.gz
> > Emacs.app/Contents/Resources/lisp/textmodes/toml-ts-mode.elc
> > Emacs.app/Contents/Resources/lisp/textmodes/yaml-ts-mode.el.gz
> > Emacs.app/Contents/Resources/lisp/textmodes/yaml-ts-mode.elc
> >
> > That may be a source of confusion ...
>
> Why would it confuse? You also have there stuff like w32-win.el.gz,
> which is used only on MS-Windows, and other files that are not
> necessarily for your configuration. This is not a problem, and
> shouldn't be one.
>
--
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: 5351 bytes --]
next prev parent reply other threads:[~2023-01-21 11:30 UTC|newest]
Thread overview: 114+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-19 16:53 Re: Make all tree-sitter modes optional Pedro Andres Aranda Gutierrez
2023-01-20 8:30 ` 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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2023-02-18 7:55 Pedro Andres Aranda Gutierrez
2023-03-11 12:45 ` Ongaro
[not found] <84973.1672843723@hassadar.pretzelnet.org>
[not found] ` <83wn62xi3k.fsf@gnu.org>
[not found] ` <m1cz7u5brr.fsf@yahoo.es>
[not found] ` <83o7rexe2n.fsf@gnu.org>
[not found] ` <83h6x5xym7.fsf@gnu.org>
2023-01-15 14:01 ` Eli Zaretskii
2023-01-15 23:39 ` Dmitry Gutov
2023-01-16 7:43 ` Theodor Thornhill
2023-01-16 16:30 ` Dmitry Gutov
2023-01-16 12:34 ` Eli Zaretskii
2023-01-16 13:06 ` Dmitry Gutov
2023-01-16 14:20 ` Eli Zaretskii
2023-01-16 14:50 ` Dmitry Gutov
2023-01-16 14:59 ` Eli Zaretskii
2023-01-17 12:59 ` Dmitry Gutov
2023-01-17 13:47 ` Eli Zaretskii
2023-01-17 14:32 ` Dmitry Gutov
2023-01-17 14:52 ` Eli Zaretskii
2023-01-17 15:22 ` Dmitry Gutov
2023-01-17 17:02 ` Eli Zaretskii
2023-01-17 17:10 ` Dmitry Gutov
2023-01-17 17:38 ` Eli Zaretskii
2023-01-17 17:59 ` Dmitry Gutov
2023-01-17 18:04 ` Eli Zaretskii
2023-01-17 18:21 ` Dmitry Gutov
2023-01-17 18:40 ` Eli Zaretskii
2023-01-17 18:49 ` Dmitry Gutov
2023-01-17 19:03 ` Eli Zaretskii
2023-01-17 19:21 ` Dmitry Gutov
2023-01-18 1:11 ` Yuan Fu
2023-01-18 1:23 ` Dmitry Gutov
2023-01-18 3:34 ` Eli Zaretskii
2023-01-18 3:52 ` Dmitry Gutov
2023-01-18 12:06 ` Eli Zaretskii
2023-01-18 14:00 ` Dmitry Gutov
2023-01-18 14:51 ` Eli Zaretskii
2023-01-18 12:36 ` Stefan Monnier
2023-01-16 1:12 ` Po Lu
2023-01-17 17:30 ` Juri Linkov
2023-01-17 17:58 ` Eli Zaretskii
2023-01-17 18:19 ` Juri Linkov
2023-01-17 18:41 ` Eli Zaretskii
2023-02-14 19:08 ` Alan Mackenzie
2023-02-14 19:29 ` Eli Zaretskii
2023-02-14 21:02 ` Alan Mackenzie
2023-02-15 15:35 ` Eli Zaretskii
2023-02-15 17:57 ` Alan Mackenzie
2023-02-15 18:33 ` Eli Zaretskii
2023-02-15 20:31 ` Alan Mackenzie
2023-02-16 5:41 ` tomas
2023-02-16 7:27 ` Eli Zaretskii
2023-02-16 22:05 ` Yuan Fu
[not found] ` <87v8k2g04m.fsf@dick>
2023-02-15 20:34 ` Eli Zaretskii
[not found] ` <87mt5eegkw.fsf@dick>
2023-02-16 7:53 ` Eli Zaretskii
2023-02-16 8:52 ` Po Lu
2023-02-15 21:40 ` Alan Mackenzie
2023-02-17 13:30 ` Alan Mackenzie
2023-02-17 13:37 ` Po Lu
2023-02-17 13:46 ` Stefan Monnier
2023-02-17 14:16 ` Po Lu
2023-02-17 14:40 ` Eli Zaretskii
2023-02-17 14:56 ` Dmitry Gutov
2023-02-17 15:04 ` Eli Zaretskii
2023-02-17 16:04 ` Stefan Kangas
2023-02-17 17:42 ` Morgan Willcock
2023-02-17 15:15 ` Gregory Heytings
2023-02-17 13:54 ` Alan Mackenzie
[not found] ` <d4c1a7f6-b5bf-f4f3-8d79-1c6b1d07cf70@yandex.ru>
2023-02-17 14:22 ` Po Lu
2023-02-17 14:58 ` Eli Zaretskii
2023-02-17 15:18 ` Alan Mackenzie
2023-02-15 18:34 ` Stefan Monnier
2023-02-15 19:01 ` Dmitry Gutov
2023-02-15 19:26 ` Stefan Monnier
2023-02-15 19:47 ` Eli Zaretskii
2023-02-15 19:53 ` Stefan Monnier
2023-02-15 20:06 ` Eli Zaretskii
2023-02-15 21:04 ` Stefan Monnier
2023-02-16 7:42 ` Eli Zaretskii
2023-02-16 9:49 ` Basil L. Contovounesios
2023-02-16 11:48 ` Eli Zaretskii
2023-02-16 14:41 ` Stefan Monnier
2023-02-16 15:42 ` Eli Zaretskii
2023-02-16 16:45 ` Stefan Monnier
2023-02-16 17:05 ` Eli Zaretskii
2023-02-16 19:14 ` Dmitry Gutov
2023-02-16 20:07 ` Stefan Monnier
2023-02-16 5:45 ` tomas
2023-02-16 8:26 ` Eli Zaretskii
2023-02-16 10:30 ` Alan Mackenzie
2023-02-16 12:38 ` Po Lu
2023-02-16 12:53 ` Dmitry Gutov
2023-02-15 20:24 ` Dmitry Gutov
2023-02-16 7:05 ` Eli Zaretskii
2023-02-16 7:53 ` Theodor Thornhill
2023-02-16 8:34 ` Eli Zaretskii
2023-02-16 8:46 ` Theodor Thornhill
2023-02-16 11:58 ` Dmitry Gutov
2023-02-16 11:56 ` Dmitry Gutov
2023-02-16 14:48 ` Theodor Thornhill via Emacs development discussions.
2023-02-16 14:56 ` Dmitry Gutov
2023-02-16 15:15 ` Theodor Thornhill
2023-02-15 23:48 ` Lynn Winebarger
2023-02-16 2:56 ` Stefan Monnier
2023-02-15 19:07 ` Eli Zaretskii
2023-02-15 19:27 ` Stefan Monnier
2023-02-15 21:06 ` Basil L. Contovounesios
2023-02-16 7:44 ` Eli Zaretskii
2023-02-15 18:25 ` Juri Linkov
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=CAO48Bk8VnGPO0m-WuaJyOk41xp+H1im4YSzs0jNykeWm+rzvug@mail.gmail.com \
--to=paaguti@gmail.com \
--cc=eliz@gnu.org \
--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).