Bug Plenary Path while normalize path in WINDOWS

[syukri21]

I got this error

While fresh install using

NvChad/starter

E5108: Error executing lua: ...a/Local/nvim-data/lazy/plenary.nvim/lua/plenary/path.lua:643: Could not create file: C:\Users\Syukri\Documents\Digi\digisign-devkube\C:/Users/Syukri/AppData/Local/nvim-data/telescope_history
stack traceback:                                                                                                                [C]: in function 'error'                                                                                                ...a/Local/nvim-data/lazy/plenary.nvim/lua/plenary/path.lua:643: in function 'touch'                                    ...ta/lazy/telescope.nvim/lua/telescope/actions/history.lua:183: in function 'init'                                     ...ta/lazy/telescope.nvim/lua/telescope/actions/history.lua:81: in function 'handler'                                   ...data/lazy/telescope.nvim/lua/telescope/actions/state.lua:50: in function 'get_current_history'                       ...-data/lazy/telescope.nvim/lua/telescope/actions/init.lua:80: in function <...-data/lazy/telescope.nvim/lua/telescope/actions/init.lua:78>                                                                                                    ...im-data/lazy/telescope.nvim/lua/telescope/actions/mt.lua:58: in function 'key_func'                                  ...nvim-data/lazy/telescope.nvim/lua/telescope/mappings.lua:269: in function <...nvim-data/lazy/telescope.nvim/lua/telescope/mappings.lua:268>  

[silberlu]

I got the same error with LazyVim

[nomnivore]

Same issue here. Fresh install of LazyVim on Windows. Same config works just fine in WSL2

[rakshasha-medhi]

I'm having the same issue, using Lazyvim. Every time opening the find file the error message always pops up and even though I can see the file, I cannot open it.

[MMJLee]

Same with fresh install of NVChad

[PowerzinBR]

Same here, maybe try to get an previous version of plenary and download it, then move to the plugins data folder i guess? This error wasn't here before.

[Aaron2017Li]

Same issue here.
Fresh install of LazyVim on the latest Windows 11 while same configs work fine in a WSL2 Ubuntu 22.04
After a recent update using LazyVim, the issue arose.

[nomnivore]

Same here, maybe try to get an previous version of plenary and download it, then move to the plugins data folder i guess? This error wasn't here before.

I tried reverting to several old commits - as old as one year ago - and the issue persisted. I think the root of the change may be somewhere else, maybe a neovim version update? I'm on the latest neovim-nightly.

NVIM v0.10.0-dev-2671+gdc110cba3
Build type: RelWithDebInfo
LuaJIT 2.1.1710088188

[Aaron2017Li]

Same here, maybe try to get an previous version of plenary and download it, then move to the plugins data folder i guess? This error wasn't here before.

I tried reverting to several old commits - as old as one year ago - and the issue persisted. I think the root of the change may be somewhere else, maybe a neovim version update? I'm on the latest neovim-nightly.

NVIM v0.10.0-dev-2671+gdc110cba3
Build type: RelWithDebInfo
LuaJIT 2.1.1710088188

I have just updated telescope to 1e59188 ("fix(utils.path_expand): improve windows support") using LazyVim, which fixed the issue.
So I believe it has nothing to do with Nvim.
I'm using the latest stable release, which is

NVIM v0.9.5
Build type: RelWithDebInfo
LuaJIT 2.1.1703942320

I appreciate jamestrew's timely work. ❤️

[PowerzinBR]

Same here, maybe try to get an previous version of plenary and download it, then move to the plugins data folder i guess? This error wasn't here before.

I tried reverting to several old commits - as old as one year ago - and the issue persisted. I think the root of the change may be somewhere else, maybe a neovim version update? I'm on the latest neovim-nightly.

NVIM v0.10.0-dev-2671+gdc110cba3
Build type: RelWithDebInfo
LuaJIT 2.1.1710088188

Oh, yes
At least the bug got fixed, since it was related to Telescope. I thinked it comed from plenary, haha!

[nomnivore]

Problem is resolved on my end as well now thanks to the telescope update. I think it's safe to close this issue.