Control space not working for cmp

[jay-babu]

AstroNvim/lua/configs/cmp.lua

Line 80 in bdddd84

["<C-Space>"] = cmp.mapping(cmp.mapping.complete(), { "i", "c" }),

nothing happens when I press Ctrl + Space. the other bindings work. I did not test them all

[jay-babu]

https://github.com/jayp0521/dotfiles/tree/main/nvim/.config/nvim/lua/user

[mehalter]

<c-space> here is triggering the complete() function. Basically this is used to open the completion menu if it is not available (to my knowledge). So it might not be doing what you think if you are picturing it doing "selection".

An example of this is here: https://asciinema.org/a/dinLAO4CjcdXWKWjObFdsIglJ

When there is no completion menu available, if I press <c-space> then it will open the completion menu appropriately

[jay-babu]

Correct that is not happening. I can send a video later. I can try with vanilla AstroNvim however I don't really see anything conflicting

[mehalter]

Could it be because there is nothing matching the completion? The easiest way to test this is to start typing something where the menu is open automatically and then use <c-e> to close it and then immediately do <c-space> and see if it reopens.

[johnsiras]

Could it be because there is nothing matching the completion? The easiest way to test this is to start typing something where the menu is open automatically and then use <c-e> to close it and then immediately do <c-space> and see if it reopens.

I have the same issue too, doing <c-e> after that doing <c-space> doesn't work

[mehalter]

@johnsiras could you share your user configuration? Also what terminal and operating system are you on?

[johnsiras]

I still don't have my nvim user config repo yet, but my terminal is wezterm both wezterm, terminal, and alacritty doesn't work.
Operating system is windows

[mehalter]

@johnsiras @jayp0521 this appears to be a bug upstream for Neovim on windows: neovim/neovim#8435

[johnsiras]

@johnsiras @jayp0521 this appears to be a bug upstream for Neovim on windows: neovim/neovim#8435

Btw, <c-space> but doing <tab> it works??
I pressed <c-e> then tab works only space doesn't work that's so weird....

And it's annoying too when using tab ik it's for indentation not for cmp completion

wezterm-gui_O2Z4p1A1NU.mp4

[mehalter]

@johnsiras we are currently using a replication of the "super tab" like functionality found here: https://github.com/hrsh7th/nvim-cmp/wiki/Example-mappings#luasnip

This checks to see if there are words before the cursor and if there are then it will try to complete which is the behavior you are experiencing. It will not trigger the complete if you are tabbing in a new line which is most of the cases where one tends to put tab characters.

This functionality can be overridden in the user configuration (I do this because I am not a fan of this default, but the general consensus by the users on the discord/here are that this is preferred):

return {
  plugins = {
    cmp = function(config)
      local cmp = require "cmp"
      local luasnip = require "luasnip"
      config.mapping["<Tab>"] = cmp.mapping(function(fallback)
        if luasnip.expandable() then
          luasnip.expand()
        elseif luasnip.expand_or_jumpable() then
          luasnip.expand_or_jump()
        else
          fallback()
        end
      end, { "i", "s" })
      config.mapping["<S-Tab>"] = cmp.mapping(function(fallback)
        if luasnip.jumpable(-1) then
          luasnip.jump(-1)
        else
          fallback()
        end
      end, { "i", "s" })
      return config
    end,
  },
}

[mehalter]

Since this is an upstream bug affecting windows users and not related to AstroNvim in particular, I'm going to go ahead and close this and leave the issue searchable for anyone else who may have the same problem/question.

[gfcroft]

For anyone stumbling across this thread who has a similar issue (ctrl-space not working when trying to trigger completion) I would recommend checking that your keyboard/terminal app/whatever in the input chain to vim is actually sending the input (ctrl-space) you think it is - particularly if you're on MacOs!

I questioned if my terminal app (iterm2) wasn't sending ctrl-Space through properly, so on iterm2 I turned on raw key reporting mode:

that showed me that space bar wouldn't register any input when ctrl was pressed at the same time

I then stumbled across this article which says that apparently a default system shortcut was made a while ago in macos that uses the ctrl-space combination

https://apple.stackexchange.com/a/351058

deselecting this shortcut like so solved my problem: