unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Randy Taylor <dev@rjt.dev>
To: "emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: feature/tree-sitter: Where to Put C/C++ Stuff
Date: Tue, 01 Nov 2022 02:30:54 +0000	[thread overview]
Message-ID: <R81eqRnh59M6KReiNitd8krtvaP7UwYJkpekvBIgBogFdv1bOVynbGlKnx5AjwBdhm1A5y1mNLss4Lojzv7g0xOx4HQJ-sCU5CiPPl-ycM8=@rjt.dev> (raw)

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

Hi.

Where specifically should the C and C++ tree-sitter stuff go? I've been using it for a couple months and would like to upstream syntax highlighting for both. I'll focus on getting C done first.

I see there are a lot of cc- files; would it be appropriate to add the tree-sitter stuff into a new cc-treesit.el file?
Thanks.

[-- Attachment #2: Type: text/html, Size: 877 bytes --]

             reply	other threads:[~2022-11-01  2:30 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-01  2:30 Randy Taylor [this message]
2022-11-01  5:44 ` feature/tree-sitter: Where to Put C/C++ Stuff Theodor Thornhill
2022-11-01  7:24   ` Eli Zaretskii
2022-11-01  7:55     ` Theodor Thornhill
2022-11-01  9:22       ` Yuan Fu
2022-11-01  9:41         ` Theodor Thornhill
2022-11-01  9:57       ` Eli Zaretskii
2022-11-01 11:53         ` Theodor Thornhill
2022-11-01 12:28           ` Eli Zaretskii
2022-11-01 13:05             ` Theodor Thornhill
2022-11-01 13:10               ` Eli Zaretskii
2022-11-01 13:27                 ` Theodor Thornhill
2022-11-01 13:49                   ` Eli Zaretskii
2022-11-01 13:54                     ` Theodor Thornhill
2022-11-01 14:03                       ` Eli Zaretskii
2022-11-01 14:12                         ` Theodor Thornhill
2022-11-01 16:09                 ` tomas
2022-11-01 13:12             ` Manuel Uberti
2022-11-04 14:49             ` Benjamin Riefenstahl
2022-11-04 16:17               ` Pascal Quesseveur
2022-11-01 13:32     ` Stefan Monnier
2022-11-01 14:02       ` Eli Zaretskii
2022-11-01 15:09         ` Stefan Monnier
2022-11-01 15:36           ` Theodor Thornhill
2022-11-01 16:43           ` Eli Zaretskii
2022-11-02 20:43   ` João Távora
2022-11-01  7:20 ` Eli Zaretskii
2022-11-01 12:10   ` Alan Mackenzie

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='R81eqRnh59M6KReiNitd8krtvaP7UwYJkpekvBIgBogFdv1bOVynbGlKnx5AjwBdhm1A5y1mNLss4Lojzv7g0xOx4HQJ-sCU5CiPPl-ycM8=@rjt.dev' \
    --to=dev@rjt.dev \
    --cc=emacs-devel@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. 
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).