-
-
Notifications
You must be signed in to change notification settings - Fork 72
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
File "does not look like a chat file" #104
Comments
Previously, to facilitate switching between different Neovim configurations, I created symbolic links for the nvim folders located under the .local/share/ and .config/ directories, linking them to different distro. However, this approach led to the this issue. I resolved my problem by explicitly specifying the real address of the chat folder in the chat_dir option. |
I'm using gp.nvim and it is really useful for me. I'm also encountering the same problem.
As a catch, the md files under I am not familiar with Lua and may have configured it incorrectly. Sincerely, |
Hi everyone, Checking whether or not a file is a chat uses several conditions. The latest version, I've just pushed, should provide more verbose message. If anyone would be willing to try it and share the error (ideally in it's entirety - for example real file path on which it failed), it would greatly help to hone on the problem. Tomorrow I'll try to replicate and debug the issue with symlinks mentioned by @kingfirewxm. |
Note for myself: https://vi.stackexchange.com/questions/44028/weird-interaction-between-gp-nvim-and-syntastic (I guess I have to install Windows 😢 ) |
@Robitx I updated gp.nvim to v2.4.7 and did the same things.
I'm sorry I forgot to say that I'm using gp.nvim on WSL2🙏
I change state_dir and chat_dir because I want to sync chats around the devices I use via GoogleDrive. I created symbolic link on WSL2 home.
then, I set the env in .zshenv below.
I tried two settings.
This config set dirs not using envs, but this sent the same message.
This config set dirs not using the symbolic links. This goes well. From this and kingfirewxm's comments, I think the symbolic link is causing the problem🤔 |
Additionaly I tried below.
Then, I got the same message.
|
I can confirm that the problem is also caused by a symlink for me. Specifying |
@lennartack @yanosea @kingfirewxm The latest version 2.4.9 should be able to handle symlinks properly, please give it go. |
It works, thank you! |
@Robitx |
* chore: wip backup * chore: wip backup * chore: formating * feat: working copilot agents * chore: wip backup * chore: wip backup + lmstudio test * chore: fmt * chore: wip * fix: toggle GpChatNew popup (resolve #112) * chore: auto-generate vimdoc * chore: strip whitespace in buf target resolve * fix: handle symlinks in chat checks (issue: #104) * feat: ollama with openAI endpoint + gemini * chore: fix typo * feat: show current agent in chat * chore: copilot bearer refreshing * feat: dynamic model for googleai * feat: support for perplexity and anthropic * docs: vim-plug setup snippet (issue: #123) * chore: auto-generate vimdoc * feat: update defaults to use latest model versions: gpt-4o and gpt-3.5-turbo * chore: auto-generate vimdoc * feat: filter out empty lines in picker * fix: set the popup window to markdown filetype * chore: wip backup * chore: wip backup * chore: formating * feat: working copilot agents * chore: wip backup * chore: wip backup + lmstudio test * chore: fmt * chore: wip * feat: ollama with openAI endpoint + gemini * chore: fix typo * feat: show current agent in chat * chore: copilot bearer refreshing * feat: dynamic model for googleai * feat: support for perplexity and anthropic * chore: handle old user chat prefix * chore: newer copilot headers * chore: GPT4 => GPT4o rename * chore: default sys prompt vars * chore: disable all but openAI before merging to main * chore: better migration message * docs: readme section about multi provider support --------- Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: Shalom Yiblet <[email protected]> Co-authored-by: Tan Long <[email protected]> Co-authored-by: XXiaoA <[email protected]>
Recently GpChat stopped working.
Steps to reproduce:
I see an error message:
Gp: file "/path/to/chat.md" does not look like a chat file
.The text was updated successfully, but these errors were encountered: