From: Zheng Junjie <zhengjunjie@iscas.ac.cn>
To: 70720@debbugs.gnu.org
Cc: Katherine Cox-Buday <cox.katherine.e+guix@gmail.com>,
70720-done@debbugs.gnu.org, Karl Hallsby <karl@hallsby.com>,
Liliana Marie Prikler <liliana.prikler@gmail.com>,
Andrew Tropin <andrew@trop.in>
Subject: [bug#70720] [PATCH 0/3] Add tree-sitter-verilog/-vhdl/-erlang
Date: Tue, 14 May 2024 00:40:55 +0800 [thread overview]
Message-ID: <87y18dy8a0.fsf@iscas.ac.cn> (raw)
In-Reply-To: <cover.1714663253.git.karl@hallsby.com> (Karl Hallsby via Guix-patches via's message of "Thu, 2 May 2024 10:36:37 -0500")
[-- Attachment #1: Type: text/plain, Size: 866 bytes --]
Karl Hallsby via Guix-patches via <guix-patches@gnu.org> writes:
> Verilog & VHDL have Emacs major modes for them. I have tested that both
> verilog-ts-mode and vhdl-ts-mode produce syntax highlighting.
>
> Erlang does not have a tree-sitter-powered major-mode for Emacs yet.
>
> Karl Hallsby (3):
> gnu: Add tree-sitter-verilog.
> gnu: Add tree-sitter-vhdl.
> gnu: Add tree-sitter-erlang.
>
> gnu/packages/tree-sitter.scm | 58 ++++++++++++++++++++++++++++++++++++
> 1 file changed, 58 insertions(+)
>
>
> base-commit: 5010a51fc91aeac5a3b87a3eea04f18f3fe8a3a3
push, see
https://git.savannah.gnu.org/cgit/guix.git/commit/?id=65186deae436f419fbe56a88d097181453728a29
https://git.savannah.gnu.org/cgit/guix.git/commit/?id=6b6ad68559ef57764af6460aef6d5cd46fab06eb
https://git.savannah.gnu.org/cgit/guix.git/commit/?id=b23aa4c1d6ebbbee316d2f2bee87ad4ce7c67345
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
prev parent reply other threads:[~2024-05-13 16:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-02 15:36 [bug#70720] [PATCH 0/3] Add tree-sitter-verilog/-vhdl/-erlang Karl Hallsby via Guix-patches via
2024-05-02 15:39 ` [bug#70720] [PATCH 1/3] gnu: Add tree-sitter-verilog Karl Hallsby via Guix-patches via
2024-05-10 12:16 ` Zheng Junjie
2024-05-02 15:39 ` [bug#70720] [PATCH 2/3] gnu: Add tree-sitter-vhdl Karl Hallsby via Guix-patches via
2024-05-10 12:14 ` Zheng Junjie
2024-05-02 15:39 ` [bug#70720] [PATCH 3/3] gnu: Add tree-sitter-erlang Karl Hallsby via Guix-patches via
2024-05-10 12:18 ` Zheng Junjie
2024-05-10 16:26 ` [bug#70720] [PATCH 1/3] gnu: Add tree-sitter-verilog Karl Hallsby via Guix-patches via
2024-05-10 16:26 ` [bug#70720] [PATCH 2/3] gnu: Add tree-sitter-vhdl Karl Hallsby via Guix-patches via
2024-05-10 16:26 ` [bug#70720] [PATCH 3/3] gnu: Add tree-sitter-erlang Karl Hallsby via Guix-patches via
2024-05-10 16:49 ` [bug#70720] [PATCH 1/3] gnu: Add tree-sitter-verilog Liliana Marie Prikler
2024-05-10 18:28 ` Karl Hallsby via Guix-patches via
2024-05-10 18:28 ` [bug#70720] [PATCH 2/3] gnu: Add tree-sitter-vhdl Karl Hallsby via Guix-patches via
2024-05-10 18:28 ` [bug#70720] [PATCH 3/3] gnu: Add tree-sitter-erlang Karl Hallsby via Guix-patches via
2024-05-13 16:40 ` Zheng Junjie [this message]
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=87y18dy8a0.fsf@iscas.ac.cn \
--to=zhengjunjie@iscas.ac.cn \
--cc=70720-done@debbugs.gnu.org \
--cc=70720@debbugs.gnu.org \
--cc=andrew@trop.in \
--cc=cox.katherine.e+guix@gmail.com \
--cc=karl@hallsby.com \
--cc=liliana.prikler@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/guix.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).