A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://lists.gnu.org/archive/html/emacs-devel/2022-11/msg00028.html below:

Re: feature/tree-sitter: Where to Put C/C++ Stuff

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] From: Alan Mackenzie Subject: Re: feature/tree-sitter: Where to Put C/C++ Stuff Date: Tue, 1 Nov 2022 12:10:46 +0000
Hello, Eli.

On Tue, Nov 01, 2022 at 09:20:33 +0200, Eli Zaretskii wrote:
> > Date: Tue, 01 Nov 2022 02:30:54 +0000
> > From: Randy Taylor <dev@rjt.dev>

> > 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?

> I suggest a separate cc-*.el file (e.g., cc-treesit.el), and some user
> option to trigger its use instead of (or maybe in addition to, as the
> case may be) the equivalent CC mode stuff.

> Alan, are you okay with this approach?

Yes, certainly.  It is the approach I would have chosen myself.  The key
sequence C-c C-t is currently unused in CC Mode, and it would seem ideal
to toggle tree-sitter with.

-- 
Alan Mackenzie (Nuremberg, Germany).



RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4