Repository navigation
Plugin isn't working but keybindings have been mapped #115
Description
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.mdof this repouse { 'numToStr/Comment.nvim', config = function() require('Comment').setup() end }
-
I check the
:mapand found all keymaps have been mapped
-
Issue: using the
gccand/or other actions doesn't work at all.
Ex: after typing thegccthe 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.basicto true (at thesetupfunction 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
enterto confirm the command - then
g@$
- Try to set
Activity
numToStr commentedon Feb 8, 2022
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 gccshould work. Can you try running the command?hpb0412 commentedon Feb 8, 2022
Hi @numToStr,
No worries, I totally understand of the device-dependent issue.
FYI, the
:normal gccworks 👍Hope it can give you some ideas about the issue.
Thanks 🙇
numToStr commentedon Feb 8, 2022
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 commentedon Feb 8, 2022
I found the cause.
I guessed it is because of some kind of key typing timeout.
I went to configuration and found that my
timeoutlenofneovimis100while default it should be1000.Therefore I switch back to
1000and the plugin works very well.Thank you 🙇
[-]The plugin doesn't work on iterm2 / Mac OS[/-][+]Plugin isn't working but keybindings have been mapped [/+]kohane27 commentedon Apr 7, 2022
@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 completeI 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.caamittiwari commentedon Jul 25, 2022
this totally depends upon how fast u type the key and your system configuration if type fast u may decrease it and if not increase it
plugin is working fine and very great plugin to use
Vaisakhkm2625 commentedon Aug 28, 2022
Thanks.. for me gcc itself wasn' working, and i was copied many things from Chris@machine.. :) now everything is working... thanks
[several plugin files] Replace commentary with Comment.nvim
gyaaniguy commentedon Mar 9, 2024
I had the same issue when using vscode neovim extension + kickstart.nvim
It had reduced the time to 300ms in init.lua . I changed it to 1000 and all is good now !
vim.opt.timeoutlen = 1000