unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
To: Yuan Fu <casouri@gmail.com>
Cc: "João Paulo Labegalini de Carvalho" <jaopaulolc@gmail.com>,
	emacs-devel@gnu.org
Subject: Re: Tree-sitter doc question
Date: Mon, 12 Dec 2022 09:57:05 +0100	[thread overview]
Message-ID: <CAO48Bk8RhkkPPc_-kyTJbT66LVGo652SzRWmA2Z7TC9+YqVDkw@mail.gmail.com> (raw)
In-Reply-To: <1CF30111-BFFE-4928-B40C-347A5EE3FF8B@gmail.com>

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

THANKSSSS !!!
It is a bit hidden, though ;-) A bit of a highlight may not hurt for
too-quick readers like me...

/PA

On Sun, 11 Dec 2022 at 23:04, Yuan Fu <casouri@gmail.com> wrote:

>
>
> > On Dec 11, 2022, at 12:31 AM, Pedro Andres Aranda Gutierrez <
> paaguti@gmail.com> wrote:
> >
> > Obrigado, João Paulo
> >
> > That's done :-) I now have an Emacs with tree-sitter and I have gone to
> the admin/... directory to compile the language support .so.
> > Maybe the final step in that documentation would be to say a word on
> where to place those files when testing and how to
> > "politely encourage" Emacs to load and use them ;-)
>
> admin/notes/tree-sitter/starter-guide has this:
>
> and language definitions will be in the /dist directory. You can
> either copy them to standard dynamic library locations of your system,
> eg, /usr/local/lib, or leave them in /dist and later tell Emacs where
> to find language definitions by setting ‘treesit-extra-load-path’.
>
> So I think we are covered :-)
>
> Yuan



-- 
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: 1940 bytes --]

  reply	other threads:[~2022-12-12  8:57 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-09  8:33 Re: Tree-sitter doc question Pedro Andres Aranda Gutierrez
2022-12-09 12:10 ` Eli Zaretskii
2022-12-10  7:29   ` Pedro Andres Aranda Gutierrez
2022-12-10  8:46     ` Eli Zaretskii
2022-12-10 11:14       ` Pedro Andres Aranda Gutierrez
2022-12-10 15:29         ` João Paulo Labegalini de Carvalho
2022-12-11  8:31           ` Pedro Andres Aranda Gutierrez
2022-12-11 22:03             ` Yuan Fu
2022-12-12  8:57               ` Pedro Andres Aranda Gutierrez [this message]
2022-12-12 16:36         ` Eric S Fraga
2022-12-12 17:59           ` Stefan Monnier
2022-12-12 18:11             ` Eli Zaretskii
2022-12-12 18:20               ` Stefan Monnier
2022-12-12 18:32                 ` Óscar Fuentes
2022-12-12 18:52                   ` Juanma Barranquero
2022-12-12 19:20                     ` Óscar Fuentes
2022-12-12 19:37                       ` Eli Zaretskii
2022-12-12 22:50                       ` Tim Cross
2022-12-12 23:34                         ` João Paulo Labegalini de Carvalho
2022-12-13  3:25                           ` Tim Cross
2022-12-12 19:19                 ` Fraga, Eric
     [not found] <20221208141247.36l2j3bxggslsykl.ref@Ergus>
2022-12-08 14:12 ` Ergus
2022-12-08 14:38   ` Eli Zaretskii
     [not found]     ` <20221208145246.3iq7ehnxdii5xgqq@Ergus>
2022-12-08 14:57       ` Eli Zaretskii
2022-12-08 15:08         ` Felix
2022-12-08 15:44           ` Eli Zaretskii
2022-12-08 16:05             ` Stefan Kangas
2022-12-08 16:24               ` Juanma Barranquero
2022-12-08 16:29                 ` Felix
2022-12-08 17:39                   ` Eli Zaretskii
2022-12-08 17:35                 ` Eli Zaretskii
2022-12-08 17:43           ` Stefan Monnier

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=CAO48Bk8RhkkPPc_-kyTJbT66LVGo652SzRWmA2Z7TC9+YqVDkw@mail.gmail.com \
    --to=paaguti@gmail.com \
    --cc=casouri@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=jaopaulolc@gmail.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 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).