From: Jean Louis <bugs@gnu.support>
To: Eli Zaretskii <eliz@gnu.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Where to get language definition for bash tree-sitter?
Date: Wed, 28 Dec 2022 12:05:11 +0300 [thread overview]
Message-ID: <Y6wGx7MSfttTW8TX@protected.localdomain> (raw)
In-Reply-To: <831qok1zvg.fsf@gnu.org>
* Eli Zaretskii <eliz@gnu.org> [2022-12-27 21:12]:
> Try NEWS.29, if your clone of the Git repository has such a file
> (which would mean you are tracking the master branch).
I do not use branches, only master.
Thanks. I understand instruction is for people who know how to link
it, but I don't.
> To compile such a library, compile the files "scanner.c" and "parser.c"
> (sometimes named "scanner.cc" and "parser.cc") in the "src" subdirectory
> of the library's source tree using the C or C++ compiler, then link
> these two files into a shared library named "libtree-sitter-LANG.so",
> where LANG is the name of the language supported by the grammar as it
> is expected by the Emacs major mode (for example, "c" for 'c-ts-mode',
> "cpp" for 'c++-ts-mode', "python" for 'python-ts-mode', etc.). Then place
> the shared library you've built in the same directory where you keep
> the other shared libraries used by Emacs, or in the "tree-sitter"
> subdirectory of your 'user-emacs-directory', or in a directory
> mentioned in the variable 'treesit-extra-load-path'.
I got these after compiling:
-rw-r--r-- 1 476K Dec 28 11:32 parser.o
-rw-r--r-- 1 6.7K Dec 28 11:32 scanner.o
How do I link them?
gcc -shared maybe, but I know gcc just like you know Org.
--
Jean
Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns
In support of Richard M. Stallman
https://stallmansupport.org/
next prev parent reply other threads:[~2022-12-28 9:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-27 10:21 Where to get language definition for bash tree-sitter? Jean Louis
2022-12-27 11:43 ` Emanuel Berg
2022-12-27 12:43 ` Eli Zaretskii
2022-12-27 13:35 ` Jean Louis
2022-12-27 14:02 ` Emanuel Berg
2022-12-27 14:14 ` Eli Zaretskii
2022-12-27 17:08 ` Jean Louis
2022-12-27 18:10 ` Eli Zaretskii
2022-12-28 9:05 ` Jean Louis [this message]
2022-12-28 17:11 ` Eli Zaretskii
2022-12-30 5:23 ` Jean Louis
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=Y6wGx7MSfttTW8TX@protected.localdomain \
--to=bugs@gnu.support \
--cc=eliz@gnu.org \
--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).