James Trew

It _seems_ to trigger now but now getting permission issues...

I don't know enough fortran to tell what I'm seeing lol This is `foo.f` opened in with the min config  Same config, same file in telescope  ^ this...

Ah.. it's probably a neovim version issue. It looks like I'm relying on some bleeding edge changes on nightly (https://github.com/neovim/neovim/pull/25830) I think we're planning to bump the minimum neovim version...

Thanks for the report and investigative findings. Really helps a lot. I think I can put together a fix for this. Tricky this is that client handlers can do arbitrary...

I created a PR https://github.com/nvim-telescope/telescope.nvim/pull/2770 In my limited testing, this seems to fix these kinds of issues for the `definition`, `references`, `typeDefinition` and `implementation` pickers. I think the rest of...

Can you provide a minimal config showcasing this is actually a telescope issue? I can't really afford to debug everyone's config. And the snippet provided isn't even something I can...

I think generally people just stick with colorschemes or colorscheme builders for more custom stuff. Theoretically, your code looks fine to me at first glance but it's hard to say...

Seems to be working fine on Linux. I'm not sure what's happening on Windows to cause this issue.

Thanks @searleser97 for doing this digging. Give me a few days to let me take a closer look.

Personally, I don't love the idea of having this in telescope core and would rather rely on telescope extensions to do more specialized pickers.