[Windows] Trouble Moving Generated .so on TSInstall powershell
#6659
Replies: 7 comments 1 reply
-
|
You probably have the parser open in a different Neovim instance, in which case Windows locks it. We have fixed that on Make sure to close all Neovim instances, manually clear out the target dir, and try again. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the help on this issue and the previous issue @clason! When running: Check health results.The only issue is that PowerShell has no features installed :(. As well when opening a ps1 file (checked w/ Im reading through this section of documentation. My interpretation is that since the so is generated and installed the config for the parser is more or less correct. Although there is a section on queries but I couldn't piece together exactly how to investigate the queries files to see if this could be causing my issues. So my main question - why does the plugin not recognize the highlighting capabilities of the powershell parser. |
Beta Was this translation helpful? Give feedback.
-
|
Yes, obviously you need to put the corresponding queries on runtimepath. The parser is useless without them. |
Beta Was this translation helpful? Give feedback.
-
|
Ah I am still fairly new to treesitter so unfortunately that wasn't obvious to me :( But I'm glad it was obvious to you, as it let me try some things out! So I couldn't find where nvim-treesitter downloads the source from the remote url, so I went ahead and cloned directly into my data folder, re-installed to make sure parser is generated and copied over appropriately, and finally added the queries to the runtime path. Here is my updated configuration: Checking my runtime path shows that the path is added appropriately: Contents of the directory tree-sitter-powrshell\queries directory: I went ahead and closed nvim, reopened and ran Check health for tree sitter output.I read all the query definitions get combined at runtime, but im curious if there is a way to check if the query defined in this new/custom runtime path is being considered by the plugin? Would you happen to have any suggestions on how to check that. Or do you suspect the .scm file is being loaded, but something else may be amiss. Thanks again for all of the help so far! |
Beta Was this translation helpful? Give feedback.
-
|
Queries are not downloaded as these are editor specific; you will need to provide your own. The parser table only concerns the parser itself. |
Beta Was this translation helpful? Give feedback.
-
|
I noticed that, so I downloaded the github repo of the PowerShell parser which contained an additional Assuming the plugin now has visibility to the PowerShell-specific queries, Im lost on what the missing link here is. Parser is installed, queries are visible, what else is required? |
Beta Was this translation helpful? Give feedback.
-
|
First, upstream queries are not (guaranteed to be) compatible with Neovim; the queries in this repo are hand-crafted specifically for Neovim. Second, queries are expected in a specific place (like parsers): |
Beta Was this translation helpful? Give feedback.
-
|
Went ahead and moved things around with the information you suggested. Thanks again for all the help! |
Beta Was this translation helpful? Give feedback.
-
Describe the bug
Hello, I am slowly trying to get my nvim environment setup for PowerShell editing on Windows.
The current issue I am running into is that it seems the nvim-treesitter installation process is attempting to move the newly generated .so to a common spot, but is having issues.
The interesting thing I notice is that the so gets moved to the destination directory, but the command still fails... quite odd! Either way any help or direction would be extremely helpful. Thank you in advance!
Here is the error message:
Here are the contents of both of the referenced directories:
Contents of source directory.
Contents of target directory
Finally here is the configuration for the PS parser:
To Reproduce
Install PowerShell parser with provided configuration on a Windows machine with the zig compiler.
Expected behavior
No errors!
Output of
:checkhealth nvim-treesitternvim-treesitter: require("nvim-treesitter.health").check() Installation ~ - WARNING `tree-sitter` executable not found (parser generator, only needed for :TSInstallFromGrammar, not required for :TSInstall) - OK `node` found v20.13.1 (only needed for :TSInstallFromGrammar) - OK `git` executable found. - OK `zig` executable found. Selected from { "zig" } Version: info: Usage: zig [command] [options] - OK Neovim was compiled with tree-sitter runtime ABI version 14 (required >=13). Parsers must be compatible with runtime ABI. OS Info: { machine = "x86_64", release = "10.0.22631", sysname = "Windows_NT", version = "Windows 11 Enterprise" } ~ Parser/Features H L F I J - c ✓ ✓ ✓ ✓ ✓ - c_sharp ✓ ✓ ✓ . ✓ - gitcommit ✓ . . . ✓ - gitignore ✓ . . . . - java ✓ ✓ ✓ ✓ ✓ - javascript ✓ ✓ ✓ ✓ ✓ - json ✓ ✓ ✓ ✓ . - jsonc ✓ ✓ ✓ ✓ ✓ - lua ✓ ✓ ✓ ✓ ✓ - markdown ✓ . ✓ ✓ ✓ - powershell . . . . . - query ✓ ✓ ✓ ✓ ✓ - sql ✓ . . ✓ ✓ - vim ✓ ✓ ✓ . ✓ - vimdoc ✓ . . . ✓ - xml ✓ ✓ ✓ ✓ ✓ - yaml ✓ ✓ ✓ ✓ ✓ Legend: H[ighlight], L[ocals], F[olds], I[ndents], In[j]ections +) multiple parsers found, only one will be used x) errors found in the query, try to run :TSUpdate {lang} ~Output of
nvim --versionAdditional context
No response
Beta Was this translation helpful? Give feedback.
All reactions