-
Notifications
You must be signed in to change notification settings - Fork 499
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot get TabNine to work with cquery #119
Comments
@Levi-Lesches do you have a |
Oh I didn't see this, thanks for the advice. No I don't appear to (that's odd, how is git even working then? |
Well actually after running I'm not really sure what the problem is, I can try digging around once I have time |
There's a pull request #163 to use |
PR 163 was merged and released. |
So I installed cquery (MAN was that painful -- I've never used cmake) and have it in my PATH.
I type in the following:
cquery --init={\"cacheDirectory\":\"C:\\Users\\path\\to\\my\\project\\.cquery_cache\"}
and get this:
{"jsonrpc":"2.0","method":"$cquery/progress","params":{"indexRequestCount":0,"doIdMapCount":0,"onIdMappedCount":0,"onIndexedCount":0,"activeThreads":0}}
So I know I installed it right. But TabNine keeps compaining it cannot reach the backend, even after running
TabNine::restart
and closing Sublime Text completely. I noticed there was a space in the JSON in the example.toml
file, so I copied-and-pasted it without the space into my own.toml
(note that I already got Python and Dart working so I know how to use the toml)I was able to get it working by replacing
${project_root}
with the full path with 4 backslashes each -- two to escape past Sublime Text, and two to escape past the command line tool. However, once I replaced it with${project_path}
again, it failed. I assume this means that${project_path}
only has two backslashes. How can I change this? And are there any sort of logs I can use to see what's going on (the specific error)? I am using Package Resource Viewer and couldn't find much relating to executing commands in the.toml
fileThe text was updated successfully, but these errors were encountered: