github-actions[bot]
commented
1 week ago Review Checklist
Does this PR follow the [Contribution Guidelines](development guidelines)? Following is a partial checklist:
Proper conventional commit scoping:
-
If you are adding a new plugin, the scope would be the name of the category it is being added into. ex.
feat(utility): added noice.nvim plugin -
If you are modifying a pre-existing plugin or pack, the scope would be the name of the plugin folder. ex.
fix(noice-nvim): fix LSP handler error -
[x] Pull request title has the appropriate conventional commit type and scope where the scope is the name of the pre-existing directory in the project as described above
-
[x]
READMEis properly formatted and uses fenced in links with<url>unless they are inside a[title](url) -
[x] Proper usage of
optstable rather than setting things up with theconfigfunction.
Uzaaft
Axlefublr
📑 Description
Adds the
nvim-cmp-buffer-linesnvim-cmp source, but instead of just adding it to normal completions, keeps it local to a hotkey.The reasoning for this is that, even with a low priority, whole line completions end up being super annoying, when mixed in with all the other (usually more useful) suggestions. So it's for this reason that this source is effectively "opt-in".
The mapping used is
<C-x><C-l>, because that's the default way to do whole line completions. What you basically get with this community pack, is you replace built in whole line completions with ones that use nvim-cmp.The hotkey is wack, but it is default! So I think it makes the most sense, even if there could be other, more ergonomic mappings.
At the very least, if a person wants the functionality, but on a different mapping, they now have the option to take a peek at this community pack, copy paste it into their config, and change the mapping to what they want.
ℹ Additional Information