unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Daniel Martín" <mardani29@yahoo.es>
To: "Jostein Kjønigsen" <jostein@secure.kjonigsen.net>
Cc: casouri@gmail.com,  jostein@kjonigsen.net,  emacs-devel@gnu.org
Subject: Re: tree-sitter: Paths used for loading of language definitions
Date: Sun, 16 Oct 2022 22:12:59 +0200	[thread overview]
Message-ID: <m14jw34jec.fsf@yahoo.es> (raw)
In-Reply-To: <024de525-07c3-69e8-b5a7-3e2c35287e57@secure.kjonigsen.net> ("Jostein Kjønigsen"'s message of "Sun, 16 Oct 2022 21:36:44 +0200")

Jostein Kjønigsen <jostein@secure.kjonigsen.net> writes:

> Hey there, Yuan Fu.
>
> First of all: Thank you for the tremendous effort you've put in to get
> a tree-sitter implementation mainlined into Emacs. For some of the
> major-modes I've been working on, tree-sitter has been a godsend and
> if it can enable some of them to become mainlined into Emacs... I mean
> nothing could be better!
>
> That said, I've noticed something when building the
> feature/tree-sitter branch, and also while testing other things
> tree-sitter related... If a language-definition SO is
> missing... treesit.el in Emacs only reports looking for files and
> folders typically found within $HOME/.emacs.d/ (that is user-owned
> files).
>
> Based on that, I'm assuming those are the only locations probed. Is
> that assumption correct?

I think the variable treesit-extra-load-path is supposed to contain
those extra locations.



  reply	other threads:[~2022-10-16 20:12 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-16 13:32 Some issues with the tree-sitter branch Eli Zaretskii
2022-10-16 14:01 ` Eli Zaretskii
2022-10-16 15:10 ` Eli Zaretskii
2022-10-16 19:36   ` tree-sitter: Paths used for loading of language definitions Jostein Kjønigsen
2022-10-16 20:12     ` Daniel Martín [this message]
2022-10-17  4:27     ` Yuan Fu
2022-10-17  7:14       ` Jostein Kjønigsen
2022-10-17  7:29         ` Yuan Fu
2022-10-17  8:02         ` Eli Zaretskii
2022-10-17  9:02           ` Yuan Fu
2022-10-17  9:08             ` Eli Zaretskii
2022-10-17 11:56               ` Stephen Leake
2022-10-17 13:39                 ` Eli Zaretskii
2022-10-17 21:15               ` Yuan Fu
2022-10-17  4:53 ` Some issues with the tree-sitter branch Yuan Fu
2022-10-17  5:37   ` Po Lu
2022-10-17  5:48     ` Yuan Fu
2022-10-17  6:48   ` Eli Zaretskii
2022-10-17  9:12     ` Yuan Fu
2022-10-17 10:14       ` Eli Zaretskii
2022-10-18  0:15         ` Yuan Fu
2022-10-18  0:14   ` Yuan Fu
2022-10-18 16:11     ` 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=m14jw34jec.fsf@yahoo.es \
    --to=mardani29@yahoo.es \
    --cc=casouri@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=jostein@kjonigsen.net \
    --cc=jostein@secure.kjonigsen.net \
    /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).