Skip to content
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

In README.md, clarify the location of chat/ folder for compiling tabnine chat. #162

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

christian-oudard
Copy link

It took me way too long to find this folder. Hope I'll save someone else the time.

Clarify location of chat/ folder for compiling tabnine chat. It took me way too long to find this folder.
@amirbilu
Copy link
Contributor

We can add :TabnineChatBuild command. @aarondill wdyt?

@aarondill
Copy link
Contributor

@amirbilu
that could work. what would you expect it to do? just run cargo build?

if we're doing that, should we also (or instead) add a :TabnineBuild command to run dl_binaries?

@amirbilu
Copy link
Contributor

great idea!

@aarondill
Copy link
Contributor

@amirbilu and @christian-oudard, I'm in favor of adding commands like :TabnineChatBuild to make this process easier for users, but I don't think this PR should be merged, as this files location is different depending on the user's package manager.

if you think differently, I can create a (collapsible) section in the readme describing the location for the most popular package managers (Lazy.nvim, packer, vim-plug, native packages, etc).

Please let me know which you think is the better approach here.

@lavabyrd
Copy link

lavabyrd commented May 25, 2024

Is there anyway this Readme addition could be added in the meantime? It took me far too long to realise I needed to do it from here instead of just cloning the repo and running the cargo build --release command that way

Also for Lazy, the directory would be:

~/.local/share/nvim/lazy/tabnine-nvim/chat

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants