G Roques

> Probably this is because of `vim.fs` module's implementation. It cannot detect Windows file paths (including `\`) validly. > > After #156, this plugin takes more priority to use `rg`...

> Please run Neovim with env variable: `DEBUG_PLENARY=1`. Thanks for posting these instructions @delphinus! That's a really good debugging tip. Also, I realized the behavior is inconsistent and I see...

> I found problems in `vim.fs.joinpath` & `vim.fs.dir` that they does not think Windows over. Maybe #168 fix this issue. Still testing…… Thank you @delphinus! I checked out that branch,...

> I found a problem for logic for importing entries at the first launch. > > If `file_frecency.bin` does not exist, this plugin imports entries from [`v:oldfiles`](https://neovim.io/doc/user/vvars.html#v%3Aoldfiles). If `v:oldfiles` contains...

> > I can try updating to the latest commit on master. > > Yes. This can help you, maybe. I updated my telescope plugin to the latest commit on...

I was able to get this to work by adding the path to that centralized repo's `node_modules/.bin` directory (containing `eslint`) to my `PATH` variable.

> Thanks for posting. Care to add a short note to the readme for others that might have the same question? 🙏 Sure, I'll re-open this for now, and see...

> Hi, I'm glad you enjoy this plugin! I did not know about renamer.nvim, well this seems like a great match to add support for. I briefly looked at the...

> hi @gbroques, also please pay attention that default 'lsp-progress' will handle the escaping of '%' char, e.g. double the '%'. > > see: https://github.com/linrongbin16/lsp-progress.nvim/blob/cabf7fde50cc0dad367a03a1542d9670d1118bd0/lua/lsp-progress/defaults.lua#L83 > > and: https://github.com/linrongbin16/lsp-progress.nvim/blob/cabf7fde50cc0dad367a03a1542d9670d1118bd0/lua/lsp-progress/defaults.lua#L88 >...

Thank you for the work on this @Conni2461 and @jls83! This PR looks stale. Anything I could do to help?