From: Demis Balbach <db@minikn.xyz>
To: help-guix@gnu.org
Cc: andrew@trop.in
Subject: Getting tree-sitter grammars in Guix
Date: Tue, 10 Jan 2023 18:29:04 +0100 [thread overview]
Message-ID: <87h6wycn8f.fsf@minikn.xyz> (raw)
[-- Attachment #1: Type: text/plain, Size: 3202 bytes --]
Hello, I was wondering what the "correct" way would be to get grammars
for the tree-sitter library available in Guix when using tree-sitter
with Emacs 29+.
There is https://github.com/emacs-tree-sitter/tree-sitter-langs, but I
don't think it has been packaged in Guix yet. I started packaging the
grammar for JS/TS:
--8<---------------cut here---------------start------------->8---
(define-public tree-sitter-javascript
(let ((commit "7a29d06274b7cf87d643212a433d970b73969016")
(revision "0")
(version "0.20.0"))
(package
(name "tree-sitter-javascript")
(version (git-version version revision commit))
(source
(origin
(method git-fetch)
(uri (git-reference
(url "https://github.com/tree-sitter/tree-sitter-javascript")
(commit commit)))
(sha256
(base32 "1pk6d9g6a7bzhxmwnvfiycarcgz76wq2rgfqr0xjh7y7swfw5hvw"))
(file-name (git-file-name name version))))
(build-system gnu-build-system)
(native-inputs
(list gcc))
(arguments
`(#:tests?
#f
#:phases
(modify-phases
%standard-phases
(delete 'configure)
(delete 'install)
(delete 'build)
(add-after 'unpack 'create-dirs
(lambda _ (mkdir "lib")))
(add-after 'create-dirs 'compile
(lambda* (#:key inputs outputs #:allow-other-keys)
(let* ((out (assoc-ref outputs "out"))
(gcc (string-append (assoc-ref inputs "gcc") "/bin")))
(copy-file "grammar.js" "src/grammar.js")
(with-directory-excursion
(string-append "./src")
(invoke (string-append gcc "/gcc") "-fPIC" "-c" "-I." "parser.c")
(invoke (string-append gcc "/gcc") "-fPIC" "-c" "-I." "scanner.c")
(invoke (string-append gcc "/gcc")
"-fPIC" "-shared" "parser.o" "scanner.o" "-o"
"libtree-sitter-javascript.so")))))
(add-after 'compile 'symlink
(lambda* (#:key inputs outputs #:allow-other-keys)
(let* ((out (assoc-ref outputs "out"))
(lib (string-append out "/lib")))
(install-file "src/libtree-sitter-javascript.so" lib)))))))
(home-page "https://github.com/tree-sitter/tree-sitter-javascript")
(synopsis "JavaScript and JSX grammar for tree-sitter.")
(description "JavaScript and JSX grammar for tree-sitter.")
(license license:expat))))
--8<---------------cut here---------------end--------------->8---
But I'm not sure if packaging each grammar is the correct way. I
hesitate to continue working on this because there are not other
grammars packaged in Guix (yet). With tree-sitter being built into Emacs
29+ I expected grammars to be packaged already (hence why I'm asking if
this approach is correct).
Thanks in advance!
--
Best regards / Mit freundlichen Grüßen,
Demis Balbach
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next reply other threads:[~2023-01-10 22:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-10 17:29 Demis Balbach [this message]
2023-01-21 16:43 ` Getting tree-sitter grammars in Guix Katherine Cox-Buday
-- strict thread matches above, loose matches on Subject: below --
2023-02-04 4:52 Andrew Tropin
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h6wycn8f.fsf@minikn.xyz \
--to=db@minikn.xyz \
--cc=andrew@trop.in \
--cc=help-guix@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).