emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: c-ts-mode


From: João Távora
Subject: Re: c-ts-mode
Date: Thu, 7 Sep 2023 16:58:29 +0100

On Thu, Sep 7, 2023 at 10:37 AM Eli Zaretskii <eliz@gnu.org> wrote:

> Some of the styles are already supported.  The rest should also be
> possible (at least most of them), but someone will have to write the
> code.  It is not a simple matter of "importing", since CC Mode
> implements these features based on infrastructure that either doesn't
> exist or makes no sense in treesit-supported modes.

Thanks for clarifying.  My current cc-mode user style is very
simple (I think) it inherits from the 'gnu' style and adds
minimal things.

(c-add-style "user"
             '("gnu"
               (c-special-indent-hook)
               (c-offsets-alist
                (substatement-open . 0)
                (namespace-open . -2)
                (innamespace . -2)
                (extern-lang-open . -2)
                (inextern-lang . -2))))

Basically I'd just like to keep code inside top-level
C++ namespaces and extern blocks unindented.
As to substatement-open I don't even know what
the purpose is anymore.

I see that c++-ts-mode already has a gnu user style, so
I would just need to add my preferences.  Is there a manual
entry somewhere for learning how to do this?

Also, if I may go on a tangent:  Is the forward-sexp-function
for c++-ts-mode currently undergoing work on master?  It
doesn't seem to work and all C-M-foo navigation is broken as
a result.

Debugger entered--Lisp error: (treesit-invalid-predicate nil)
  treesit-node-match-p(#<treesit-node ";" in 41-42> sexp t)
  #f(compiled-function (node) #<bytecode
0x197a9d284470c5e2>)(#<treesit-node ";" in 41-42>)
  treesit-node-top-level(#<treesit-node ";" in 41-42>
#f(compiled-function (node) #<bytecode 0x197a9d284470c5e2>) t)
  treesit--things-around(47 sexp)
  treesit--navigate-thing(47 1 end sexp restricted)
  treesit-end-of-thing(sexp 1 restricted)
  treesit-forward-sexp(1)

Setting the variable to nil brings me to more familar
and satisfactory terrain where, and I suppose the non-treesit
syntax table is being used for that.  Is there any big
advantage in switching to treesitter's forward-sexp-function?

João



reply via email to

[Prev in Thread] Current Thread [Next in Thread]