Slash Commands Without Nvim-Cmp

[collindutter]

Hi! I love the plugin, fantastic work!

I recently switched from nvim-cmp to blink.cmp. Is there any way trigger slash commands without using nvim-cmp? And are there any plans to support non-nvim-cmp autocompletion providers?

Thanks!

[olimorris]

I'm keeping a close on blink. Very excited by what it offers. Docs are still super light and I note that the API is still in "beta quality" but I would love to add support for it when it becomes feasible.

I'd expect a lot of the logic that I've added in for nvim-cmp could just be copied over.

[GitMurf]

We don't modify any mappings with Telescope. Whatever you've set in your Telescope setup is carried through to CodeCompanion.

So is the expectation when you use the "default action" (or whatever they call it), which is Enter key, that should select a buffer for example and add it as a reference in the chat? In pretty much everything in telescope, if you do not Tab select multiple items, pressing Enter the default is to "select / apply" that item. But it seems slash commands are not doing that.

Let me know if we are not fully understanding each other ;)

[collindutter]

So as far as implementing something, I can think of a couple paths:

1. Set a custom omnifunc in the CodeCompanion buffer. This would not be auto-completed, however, and would require users to trigger via CTRL-X CTRL-O.
2. Implement a CodeCompanion language server that provides completions. This feels a bit hacky and overcomplicated, but it would allow the completions to work with any autocompletion provider (native, cmp, blink, etc). Could perhaps draw inspiration from none-ls.

[GitMurf]

1. Set a custom omnifunc in the CodeCompanion buffer. This would not be auto-completed, however, and would require users to trigger via CTRL-X CTRL-O.

I think this is a great idea and the approach I would take.

@collindutter for the time being, have you done much with omnifunc / creating your own custom sources like this?

I then think it would be fairly trivial for @olimorris to provide an interface to map to, likely based off current Cmp integration, and then could make it generalized instead of needing to support each type of completion plugin / tool / source.

In hacking through the api a bit, it already is fairly easy to get slash commands to work, so I imagine it wouldn't be too difficult (famous last words) 😀

[collindutter]

have you done much with omnifunc / creating your own custom sources like this?

Not at all, I was reading up on all this today 😄

I wasn't able to find many resources on custom completefuncs, especially in lua. Could maybe use mini.completions completefunc as a starting point.

[GitMurf]

We don't modify any mappings with Telescope. Whatever you've set in your Telescope setup is carried through to CodeCompanion.

So is the expectation when you use the "default action" (or whatever they call it), which is Enter key, that should select a buffer for example and add it as a reference in the chat? In pretty much everything in telescope, if you do not Tab select multiple items, pressing Enter the default is to "select / apply" that item. But it seems slash commands are not doing that.

Let me know if we are not fully understanding each other ;)

@olimorris beat you to announcing your own fix! 🤣 Thanks for getting on this! 🎉 6184bd4

[lcmen]

Thanks for the plugin! It's really awesome. I have some beginner questions.

I also don't use nvim-cmp, and I was also wondering if I can use slash command in chat buffer. Any time I type /buffer, e.g. Check current /buffer for code errors it replies: Please select the code in the buffer you want me to check.

Set a custom omnifunc in the CodeCompanion buffer. This would not be auto-completed, however, and would require users to trigger via CTRL-X CTRL-O.

How can I set a custom omnifunc for completing codecompanion slash commands for code companion chat buffer?

[olimorris]

We have some progress:

2024-11-21.22_37_19.-.WezTerm.mp4

Ironically, what's been the biggest help is using the help slash command and sending over a load of sections from the Neovim manual to Anthropic. I've set a customisable keymap in the config, <C-/>, which triggers completion in the chat buffer.

The plan is to then remove cmp as a required dependency and I'll do the same for Telescope soon.

Hopefully ship this tomorrow.

[collindutter]

You're a legend, great work @olimorris!

[olimorris]

Gentleman, this is live. Please let me know how you get on. The default mapping is <C-/> which can be overwritten in the config.

[olimorris]

@collindutter I've just pushed an updated commit. I wasn't properly evaluating if cmp existed which meant it wasn't setting the keymap.

[collindutter]

That did it! 🎉

I still had to rebind to <C-_> as per this thread, not sure if that's a better default or not.

EDIT: fixed link.

[olimorris]

I won't take that chance. I'll make <c-_> the default. Thanks for testing.

[collindutter]

Thanks for the awesome plugin and responsiveness! Going to mark this as resolved.

[GitMurf]

Traveling this weekend but will try when back home Sunday!

[rpbaptist]

Is there any way this can work with FzfLua instead of Telescope?

[olimorris]

Funny you mention it. I'm refactoring the slash commands tomorrow and will be adding fzf-lua for commands alongside Telescope.

I believe I have a "default" option for everything except help tags.

[olimorris]

@rpbaptist fzf_lua is an option right now for everything but the help tags FYI

[olimorris]

I'm working on the blink.cmp integration. There's an outstanding issue which needs to be resolved on their side but should be straightforward.

[GitMurf]

How is blink? I haven't tried it as I am happy with my simple custom completions implementation, but I keep hearing everyone talk about it!

[olimorris]

I only installed it yesterday and my comparison point is nvim-cmp, so too early to really call it. The API is very clean though, install was a breeze. The pull of frecency and auto bracket support won me over. And, I dug through the source code for about 10 mins yesterday and was able to workout how I could add support for it in CodeCompanion. So on that basis, it's a big thumbs up.

I liken it to when Lazy.nvim came along after Packer. You had a decent repo to learn from and could also avoid the big architectural mistakes which hindered new features (I seem to recall versioning and rollbacks being a real challenge in Packer). And in the case of blink.cmp, you can add ridiculous speed (not that it was ever an issue for me) with sensible result algorithms.

[olimorris]

Happy to report that v10.5.0 supports blink.cmp following the resolution of #440.

Follow the instructions in the README in order to set it up.

[collindutter]

Woohoo! Just confirmed that it is working

Worth nothing that I had to install blink from HEAD since that patch is not in a release yet. And I think we can use opts_extend to avoid redeclaring the providers, but I can't seem to get that part working..

return {
  'saghen/blink.cmp',
  build = 'cargo build --release',
  -- version = 'v0.*',
  enabled = true,
  opts_extend = { 'sources.completion.enabled_providers' },
  opts = {
    sources = {
      completion = {
        enabled_providers = { 'codecompanion' },
      },
      providers = {
        codecompanion = {
          name = 'CodeCompanion',
          module = 'codecompanion.providers.completion.blink',
          enabled = true,
        },
      },
    },
  },
}