nvim-telescope
feat(builtin.marks): add support for cwd and cwd_only options
Description
This PR allows usage of cwd and cwd_only options in marks picker.
Fixes #3213
Type of change
New feature (non-breaking change which adds functionality)
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list relevant details about your configuration
- [ ]
:lua require('telescope.builtin').marks({ cwd_only = true }) - [ ]
:lua require('telescope.builtin').marks({ cwd = '/path/to/cwd' })
Configuration:
- Neovim version (nvim --version): NVIM v0.10.1
- Operating system and version: macOS 14.7
Checklist:
- [x] My code follows the style guidelines of this project (stylua)
- [x] I have performed a self-review of my own code
- [x] I have commented my code, particularly in hard-to-understand areas
- [x] I have made corresponding changes to the documentation (lua annotations)
I would like to say that this PR works flawlessly, and I would like to add that I would like this functionality to be made available for :Telescope jumplist as well. I've tried some similar code changes, but it doesn't work because jumplist only has bufnrs and no filenames. And get_filename_fn is not available outside of make_entry.lua. Any ideas anybody?
Not trying to be rude or anything but is anyone at the helm on telescope.nvim? I see it's 5 months since the last commit or am I mistaken? Necessary PR here I feel like too.
@xeon826 feel free to install from my fork https://github.com/cascassette/telescope.nvim instead which has cwd_only options for both marks and jumps
No promises about maintenance or even checking the issues/discussions tho
@xeon826 feel free to install from my fork https://github.com/cascassette/telescope.nvim instead which has cwd_only options for both marks and jumps
No promises about maintenance or even checking the issues/discussions tho
I would but other plugins are looking for telescope.nvim. Again, all due respect, wondering about the status of this very pivotal nvim plugin.
This needs somebody to push the CI allow button here at least. There are two other code reviews making 3 parties using this, and a code review looks sane to me. It should be linted and tested and keep moving forward.
