-
-
Notifications
You must be signed in to change notification settings - Fork 851
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Notice of Breaking Changes #1470
Comments
The Users should then move to https://github.com/nvim-telescope/telescope-file-browser.nvim. This is part of the larger strategy to incrementally carve out built-in pickers to own repos. For more, please see #1228. |
As of December 10 (1 week from now) telescope will only support Neovim 0.6 or higher: #1549 If you can't upgrade to this version you have to pin the latest working version in your plugin manager, until you can upgrade. |
Move from Because the newly added
For more informations see |
We will bump the minimum required neovim version 0.7.0 stable for telescope this friday #1851 We will create a tag the working telescope version with neovim 0.6 with the following tag After that neovim version bump we will merge fixes and usage of new features (lua autocmds) that the newest neovim release provides. Soon after this version bump we will adopt a new release strategy. This release strategy is described by tj here #1772 For more information see |
We decided to remove The reason for this is that We wrote a small repo some time ago that allows telescope to be this UI: https://github.com/nvim-telescope/telescope-ui-select.nvim and there is also this https://github.com/stevearc/dressing.nvim which has providers for a couple of different UIs. For more information see |
see :help telescope.changelog-1866 for more information
#2529 was merged and it replaced plenary.filetype with vim.filetype.match. for more information see |
This pinned issue is supposed to announce breaking changes (and possibly other critical info) to users.
The idea is that we announce (potentially) breaking changes with sufficient time (ideally weeks) in advance. Therefore, it is recommended to subscribe to the issue as means to keep informed about breaking news.
Any member should feel free to edit the OP as they see fit.
The text was updated successfully, but these errors were encountered: