unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: hw <hw@adminart.net>
To: help-gnu-emacs@gnu.org
Subject: Re: how to use tree-sitter-langs package
Date: Fri, 08 Mar 2024 07:20:16 +0100	[thread overview]
Message-ID: <429763e74d594e978aa187e7a162c7fca612ee2d.camel@adminart.net> (raw)
In-Reply-To: <87edcniu5u.fsf@posteo.net>

[-- Attachment #1: Type: text/plain, Size: 1252 bytes --]

On Wed, 2024-03-06 at 09:30 +0000, Philip Kaludercic wrote:
> hw <hw@adminart.net> writes:
> 
> > Hi,
> > 
> > I installed the tree-sitter-langs package with emacs' package
> > installer.  I got a directory with a bunch of files in it.
> 
> What package is that?

It shows up in package-list-packages.  What else can I say?

> Emacs 29 comes with a few something-ts-modes pre-installed, and
> there are a few more on GNU and NonGNU ELPA.  The important thing is
> to install the grammar, using M-x treesit-install-language-grammar.

I made an entry to treesit-language-source-alist and thus managed to
install it for the language I was looking for.  But that probably
means that I'm not using the package.

This is probably not the right way to do it, and the package seems to
support a lot of languages.  And I don't like these makeshift setups
that never update and when you come back later you have to start over
trying to figure out what you did some months or years ago, like when
you want yet another language.  It's cruft right away.  Aren't
packages supposed to avoid such bad setups?

> > How do I use this package?  I'd like to have the syntax highlighting
> > for some of the languages the package supports.



[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 858 bytes --]

      reply	other threads:[~2024-03-08  6:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-03 18:42 how to use tree-sitter-langs package hw
2024-03-06  9:30 ` Philip Kaludercic
2024-03-08  6:20   ` hw [this message]

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=429763e74d594e978aa187e7a162c7fca612ee2d.camel@adminart.net \
    --to=hw@adminart.net \
    --cc=help-gnu-emacs@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.
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).