Simon Hauser

As of December 10 (1 week from now) telescope will only support Neovim 0.6 or higher: https://github.com/nvim-telescope/telescope.nvim/pull/1549 If you can't upgrade to this version you have to pin the latest...

Move from `vim.lsp.diagnostic` to `vim.diagnostic` #1553 Because the newly added `vim.diagnostic` has no longer anything to do with lsp we also decided to rename our diagnostic functions: - Telescope lsp_document_diagnostics...

We will bump the minimum required neovim version 0.7.0 [stable](https://github.com/neovim/neovim/releases/tag/v0.7.0) for telescope this friday https://github.com/nvim-telescope/telescope.nvim/pull/1851 We will create a tag the working telescope version with neovim 0.6 with the following...

We decided to remove `lsp_code_actions` and `lsp_range_code_actions` from telescope, probably in the next two days. #1866 The reason for this is that `code_actions` is currently out of date duplicated code...

You probably wont see any Problems if you use `sorting_strategy = ascending` (see `:help telescope.defaults.sorting_strategy`). Would be nice if someone could test this CC @sultanahamer i knew it wasnt that...

sure the row seems to be correct but its still borked. And i dont need this issue so the fix needs to come from the community

We can leave it like this for now, i wont remove it. Only if the maintenance overhead is greater than the benefit of having it

What `grep_string` did you actually do? Just `:Telescope grep_string` because that one greps for the word under cursor. Or did you do `Telescope grep_string search=` which basically loads every line...

If you are using fzf-native, its a fzf-native bug because i do not yet have support for utf8 case. Its on my roadmap: https://github.com/nvim-telescope/telescope-fzf-native.nvim#todo I was already working on it...

We could add a `TelescopeCursor` hl group