Plugin isn't working but keybindings have been mapped

[hpb0412]

I am following the Neovim from Scratch tutorial but all features don't work.

My specs:

• Mac M1 (Monterey: 12.1)

• iterm2

• Neovim info:

  NVIM v0.6.1
  Build type: Release
  LuaJIT 2.1.0-beta3
  Compiled by brew@HMBRW-A-001-M1-004.local
  
  Features: +acl +iconv +tui
  See ":help feature-compile"
  
     system vimrc file: "$VIM/sysinit.vim"
     fall-back for $VIM: "/opt/homebrew/Cellar/neovim/0.6.1/share/nvim"

• My setup:

  -- comment.lua
  local status_ok, comment = pcall(require, "Comment")
  if not status_ok then
    vim.notify("Comment not found!")
    return
  end
  comment.setup()
  
  -- plugins.lua
  -- ...other stuffs
  use "numToStr/Comment.nvim"
  -- ...
  
  -- init.lua
  require "path.to.plugins"
  require "path.to.comment"

  I also try the instruction from the README.md of this repo

  use {
    'numToStr/Comment.nvim',
    config = function()
        require('Comment').setup()
    end
  }

• I check the :map and found all keymaps have been mapped
  

• Issue: using the gcc and/or other actions doesn't work at all.
  Ex: after typing the gcc the cursor converted to underline and no commenting out

Screen.Recording.2022-02-08.at.12.09.29.PM.mov

• What i did:
  • Try to set mapping.basic to true (at the setup function call)
  • Try different languages: lua, html, css, js, jsx, ts => all doesn't work
  • Try 2 ways of configuration (mentioned above)
  • The only way that works:
    • mimic the mapping with neovim command line

    :lua require("Comment.api").call("toggle_current_linewise_op")

    • then type enter to confirm the command
    • then g@$

[numToStr]

Hmmm, this is interesting but I can't do much by myself as I don't use iTerm.

---

Ok, so if all the mappings are set then running :normal gcc should work. Can you try running the command?

[hpb0412]

Hi @numToStr,
No worries, I totally understand of the device-dependent issue.

FYI, the :normal gcc works 👍
Hope it can give you some ideas about the issue.

Thanks 🙇

[numToStr]

FYI, the :normal gcc works +1 Hope it can give you some ideas about the issue.

Then I can only say that something is wrong with your config or setup. This plugin doesn't contain OS specific things, so I would doubt that this is related to this plugin. I would recommend asking other people (on neovim matrix or reddit) with a similar setup.

[hpb0412]

I found the cause.

I guessed it is because of some kind of key typing timeout.
I went to configuration and found that my timeoutlen of neovim is 100 while default it should be 1000.
Therefore I switch back to 1000 and the plugin works very well.

Thank you 🙇

[kohane27]

@hpb0412 I had the same issue as well. Turned out I copied some config from Chris@machine and he set the following:

set timeoutlen=100 " time to wait for a mapped sequence to complete

I assume the reason he did this was because we use Which-key. Setting it to 1000 means that the Which-key window would pop up only after a second, which is too long. Changing it to 500 seems to be a good middle ground.