Re: Qeustion about Ftreesit_pattern_expand

[Yuan Fu <casouri@gmail.com>]

> On Jun 25, 2024, at 10:05 PM, Gerd Möllmann <gerd.moellmann@gmail.com> wrote:
> 
> Yuan Fu <casouri@gmail.com> writes:
> 
>>> On Jun 24, 2024, at 2:26 PM, Gerd Möllmann <gerd.moellmann@gmail.com> wrote:
>>> 
>>> Not important, just as context: I wanted to see if igc works with
>>> treesit Lisp objects, built with treesitter, and finally even got
>>> grammars for C and C++ installed :-/. Font-locking didn't work in my
>>> fork (CL packages), which I fixed.
>>> 
>>> My question:
>>> 
>>> Function Ftreesit_pattern_expand uses this to print Lisp objects:
>>> 
>>> return Fprin1_to_string (pattern, Qnil, Qt);
>>> 
>>> where prin1 prints readably, and second arg nil means add escapes as
>>> needed to that the result can be read back, by function read.
>>> 
>>> Why is it printing readably with escapes?
>>> 
>>> I know tree-sitter doesn't understand Lisp escaping because that was my
>>> problem with the font-locking. Or, in other words, should the second arg
>>> be Qt for don't escape?
>>> 
>> 
>> Thanks for checking this Gerd. IIUC, readably is controlled by the
>> second argument, so it’s not redundant: if the second arg is Qnil,
>> print readably (prin1), if it’s Qt, print without quotes and escapes
>> (princ). I guess the function should’ve been called print-to-string to
>> avoid confusion.
> 
> Erm, there's a misunderstanding it seems. I'm not talking about function
> names or anything, I'm basically saying that the function call to
> Fprin1_to_string is wrong, and its second argument should be Qt
> not Qnil :-)

Ah, then I can explain. Basically I want to convert the sexp query

((function_definition) @defun
 "return" @keyword)

to a string that’s like this

"((function_definition) @defun
 "return" @keyword)"

If the second arg is Qt, the result would be

"((function_definition) @defun
 return @keyword)"

which is not what I want. Basically, strings need to be still quoted.

Yuan