all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: rrudakov@fastmail.com
Cc: casouri@gmail.com, raman@google.com, emacs-devel@gnu.org
Subject: Re: tree-sitter and language support
Date: Fri, 25 Nov 2022 14:05:48 +0200	[thread overview]
Message-ID: <83h6ynutlv.fsf@gnu.org> (raw)
In-Reply-To: <m24juntiob.fsf@Romans-MBP.home> (message from Roman Rudakov on Fri, 25 Nov 2022 11:41:47 +0100)

> From: Roman Rudakov <rrudakov@fastmail.com>
> Cc: "T.V Raman" <raman@google.com>, emacs-devel@gnu.org
> Date: Fri, 25 Nov 2022 11:41:47 +0100
> 
> > We are just starting to work on tree-sitter’s user-facing
> > documentation, including the (emacs) manual and NEWS file. I’ll
> > definitely improve the error message. In the meantime, find files 
> > that
> > looks like libtree-sitter-xxx.so and put them under
> > ~/.emacs.d/tree-sitter (or a standard library location like
> > /usr/local/lib), and Emacs should be able to find them.
> >
> > Yuan
> 
> Hi Yuan!
> 
> I have a question. Are these paths hardcoded?

This is Emacs; how can you assume such hard-coded paths are even possible?

Of course, they aren't hard-coded!  Emacs looks in the standard directories
for shared libraries, then in user-emacs-directory, then in the directories
mentioned in treesit-extra-load-path.

> I can fix it by adding /opt/homebrew/lib to treesit-extra-load-path, 
> but I'm wondering how to install grammar properly to avoid setting 
> this variable.

Adding this to treesit-extra-load-path is fine.  Alternatively, install the
shared library where you have the other shared libraries on your system
(a.k.a. "standard places").



  reply	other threads:[~2022-11-25 12:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-25  5:20 tree-sitter and language support T.V Raman
2022-11-25  6:51 ` Yuan Fu
2022-11-25 10:41   ` Roman Rudakov
2022-11-25 12:05     ` Eli Zaretskii [this message]
2022-11-25 17:57   ` T.V Raman
2022-11-25 19:48     ` Eli Zaretskii
2022-11-25 12:28 ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83h6ynutlv.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=casouri@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=raman@google.com \
    --cc=rrudakov@fastmail.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.