James Trew

Oof, I'm almost tempted to say "it's not our problem" considering `:h [==]` nets the same result... Your solution is pretty interesting though - first time actually learning about all...

Thanks! For the `offset_encoding` part, I think it's probably better to call `vim.lsp.util.locations_to_items` earlier, before calling `apply_action_handler`, then pass the return value of it to `apply_action_handler`. This is what we...

thanks lgtm!

Can you give this PR a try? https://github.com/nvim-telescope/telescope.nvim/pull/2999

I wrote some unit tests (and ran them against Windows with github actions) for the function related to handling path_display here: https://github.com/nvim-telescope/telescope.nvim/pull/3013 I think I was able to fix the...

Hmm... I starting to wonder if this is git setting related. Doing `git status` on Windows powershell gives me unix style paths.  This combined with the fact that `vim.loop.cwd`...

Ahh... nice find. I see the issue now I believe - although the plenary change complicates things a little despite it having the right intentions. Man windows paths are finicky...

I'm not super familiar with fzf-lua but trying out `FzfLua buffers` the preview looks pretty similar. Telescope is missing line numbers. Is that what you're referencing? Are there any other...

I think I'm a little bit confused about what you're trying to do but to open `help_tags` with the current filename you can do `:lua require('telescope.builtin').help_tags({ default_text = vim.fn.expand('%:t') })`...

Is the previewer not adequate for seeing context?