numToStr

> perhaps these navigation keymappings in theory could leverage that plugin? Yes, that's the idea. And we also have https://github.com/RRethy/nvim-treesitter-textsubjects But nothing will work properly until `+` quantifier support.

> is there an issue or pull-request to track the conversation and subsequent work on adding `+` quantifier? Follow #133, i already linked couple of PR there. > Separately, in...

This is expected. `gc` has to decide whether to comment or not, if it finds any line uncommented then it comments the whole motion/visual region. And to uncomment the whole...

@IndianBoy42 That's perfect. Just a pointer, I anyone wish to implement custom keybindings I'll recommend using `require('Comment').toggle()` for this.

@xeluxee This is the best I can do to cover this case. ```lua local A = vim.api local U = require('Comment.utils') function _G.__flip_flop_comment(vmode) local lcs, rcs = U.unwrap_cstr(vim.bo.commentstring) local scol,...

@xeluxee You might wanna use operatorfunc `:h operatorfunc`. This might work though I haven't tested ```lua A.nvim_set_keymap('n', 'gt', 'set operatorfunc=v:lua.__flip_flop_commentg@', { noremap = true, silent = true }) ```

So that now the API is stable. I am considering adding this but I am not sure whether to add a default mapping or just a give a lua api...

What will be the keymap's LHS? I'll be similar to `gc` as it will also wait for some motion like `k`, `l`. I am also assuming that the user will...

I am not sure about the `` combination but AFAIK even `` is enough to put you on normal mode from insert mode.

I see, that both `` and `` are similar. Although, I am not sure how to fix this as of now. `vim-commentary` must be doing something to prevent this, might...