-
Notifications
You must be signed in to change notification settings - Fork 36
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
[Windows Cygwin] Filepaths do not display correctly & files do not open reliably #164
Comments
Probably this is because of After #156, this plugin takes more priority to use |
Thank you for the reply @delphinus! :) I updated to the latest commit 9c18474, and I do have Unfortunately it still doesn't work. The behavior is slightly different now:
|
If you need me to add some I can report the output I see in this thread. |
@gbroques Thank you for further info! It seems that $ export DEBUG_PLENARY=1
$ nvim
# and run :Telescope frecency Then
(I have cut some long paths in logs) |
Thanks for posting these instructions @delphinus! That's a really good debugging tip. Also, I realized the behavior is inconsistent and I see the following two scenarios:
Additionally, I ran I set the The following is the output for
Here is the output for
|
I found problems in |
Thank you @delphinus! I checked out that branch, and tested it. Some of the paths are fixed, but I see duplicates of some paths which still display incorrectly with the "C:\Users.." in the front (see below screenshots). Also, I deleted the Lastly, I'm still seeing the behavior where the picker occassionaly fails to populate until I type a character, and I see a " E5560: nvim_buf_is_valid must not be called in a lua loop callback" warning. |
I found a problem for logic for importing entries at the first launch. If We should improve this by detecting duplication of paths. I will try it. But another problem. vim.opt.runtimepath:prepend [[\Users\jinnouchi.yasushi\AppData\Local\nvim-data\lazy\telescope.nvim]]
vim.opt.runtimepath:prepend [[\Users\jinnouchi.yasushi\AppData\Local\nvim-data\lazy\telescope-frecency.nvim]]
vim.opt.runtimepath:prepend [[\Users\jinnouchi.yasushi\AppData\Local\nvim-data\lazy\plenary.nvim]]
vim.keymap.set("n", "<Leader>ff", "<Cmd>Telescope frecency workspace=CWD<CR>")
vim.keymap.set("n", "<Leader>fo", "<Cmd>Telescope frecency<CR>")
require("telescope").setup {}
vim.fn.chdir [[\Users\jinnouchi.yasushi\AppData\Local\nvim-data\lazy\telescope-frecency.nvim]]
-- vim:se ts=2 sts=2 sw=2 et: And ![]() |
Ah, you're using Cygwin! I did this in plain Windows. I will also setup Cygwin and try the same one. |
Ok, that makes sense. I'll clear my
Sure thing! The following should be my complete telescope configuration: Currently, I'm pinned to a telescope commit, 2ea8dc, from 6 months ago. I can try updating to the latest commit on Let me know if you need any other help to reproduce this, or have questions. Thanks again for all your support in solving these issues! |
I see. Your setup seems to have no mistake.
Yes. This can help you, maybe. |
I updated my telescope plugin to the latest commit on The following is my
|
@gbroques I did changes in #168 and fixed almost all of bugs in using Windows. But I found one problem: #170. This is due to the logic of plenary.nvim, that is needed by telescope.nvim itself. I think this cannot be solved with simple way... And I also tried v0.9.0. But again I could not see |
Filepaths are not displayed correcty in the picker (see below
:Telescope frecency
screenshot ), and sometimes when I select a file an empty buffer opens instead.I haven't been able to reproduce the latter behavior consistently though, but I suspect it's related.
I expect to see filepaths displayed as
:Telescope find_files
displays them (see below screenshot).Steps to Reproduce
telescope-frecency.nvim
in/cygdrive/c/Users/Public/Projects
.telescope-frecency.nvim
directory.:Telescope frecency
.The following is a link to my Telescope configuration:
https://github.com/gbroques/neovim-configuration/blob/919ffbd07538ab432c6eba088c3330793e10b6ad/lua/plugins/fuzzy-finder.lua#L62-L113
I'm currently pinned to commit de41070 which is from early December.
The text was updated successfully, but these errors were encountered: