all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Misha Zharov <mishazharov1@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: casouri@gmail.com, 61849@debbugs.gnu.org
Subject: bug#61849: 29.0.60; Unable to use treesit-install-language-grammar because repo doesn't have parser.c
Date: Sun, 19 Mar 2023 22:14:44 -0700	[thread overview]
Message-ID: <CAEzzQa_ZFCo0LG+By7JbLTyQoiXPCkAKvkWG_NndrOjMnSJo1w@mail.gmail.com> (raw)
In-Reply-To: <83wn3d9onk.fsf@gnu.org>

> Please chime in to try to convince them to go back to including the
> generated parser files.

Thanks for the update.  I've now done this, but I think that it will be
difficult to make sure that community sticks to this standard of keeping
the autogenerated files in the repo.  Their arguments do have some
merit regarding the difficulty of resolving merge conflicts and overall
maintenance burden.  At the same time, having the autogenerated file
present is a nice QOL feature for users because it's easily reproducible.

I'm not sure what the ultimate solution to this will be though.  It might be
necessary to come up with a new paradigm of installing treesitter
grammars that addresses some of the current issues





  reply	other threads:[~2023-03-20  5:14 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-27  7:34 bug#61849: 29.0.60; Unable to use treesit-install-language-grammar because repo doesn't have parser.c Misha Zharov
2023-02-27 20:00 ` Eli Zaretskii
2023-02-28  3:13   ` Misha Zharov
2023-02-28 12:04     ` Eli Zaretskii
2023-03-03 22:27 ` Yuan Fu
2023-03-04  7:06   ` Eli Zaretskii
2023-03-04 11:06     ` Eli Zaretskii
2023-03-04 20:52       ` Misha Zharov
2023-03-19  7:38       ` Eli Zaretskii
2023-03-20  5:14         ` Misha Zharov [this message]
2023-03-20 19:28           ` Eli Zaretskii
2023-03-20 20:04             ` Dmitry Gutov
2023-03-20 20:20               ` Eli Zaretskii
2023-03-20 22:01                 ` Gregory Heytings
2023-03-21  3:27                   ` Eli Zaretskii
2023-03-21  9:39                     ` Gregory Heytings

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=CAEzzQa_ZFCo0LG+By7JbLTyQoiXPCkAKvkWG_NndrOjMnSJo1w@mail.gmail.com \
    --to=mishazharov1@gmail.com \
    --cc=61849@debbugs.gnu.org \
    --cc=casouri@gmail.com \
    --cc=eliz@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 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.