You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
nvim-treesitter[fsharp]: Error during compilation
clang: error: no such file or directory: 'src/parser.c'
clang: error: no such file or directory: 'src/scanner.c'
clang: error: no input files
Once I checked the file structure I figured out I had to add fsharp to the beginning of the path for scanner and parser files: 'fsharp/src/scanner.c' and 'fsharp/src/parser.c'.
Is this something particular about this code tree compared to other custom grammars? I just wanted to point this out to anyone who might also have this issue.
As I try to reproduce this error I am getting the following (which I wish I had the time to further debug):
nvim-treesitter[fsharp]: Error during compilation
In file included from fsharp/src/scanner.c:1:
fsharp/src/../../common/scanner.h:4:10: fatal error: 'tree_sitter/alloc.h' file not found
#include "tree_sitter/alloc.h"
^~~~~~~~~~~~~~~~~~~~~
1 error generated.
I'm not sure if others have had this problem when installing this grammar or if I did not read the install instructions correctly.
With the default code config (same as in the readme), I got the following errors after running
:TSInstall fsharp
Once I checked the file structure I figured out I had to add
fsharp
to the beginning of the path for scanner and parser files:'fsharp/src/scanner.c'
and'fsharp/src/parser.c'
.Is this something particular about this code tree compared to other custom grammars? I just wanted to point this out to anyone who might also have this issue.
As I try to reproduce this error I am getting the following (which I wish I had the time to further debug):
Here is my full plugins/init.lua config:
Huge thanks to the maintainers of this grammar <3
M1 Macbook Air on Somoma 14.5
Repo commit number 711d8f9
Editor: Nvchad/NVIM v0.10.1 Release
Up to date treesitter nvim plugin and cli
The text was updated successfully, but these errors were encountered: