sharpchen

I just tried again in a new wsl, turns out no problem. It seems it didn't download from nixos cache when I first encountered this issue so it compiles from...

strangely it was black-boxed in librewolf(a firefox-based browser) too

should use get and set instead ```lua require('Comment.ft').set('c', {'//%s', '//%s'}) ``` And I don't think this make any sense? the second element is for block commenting, you can never use...

`vim.bo.commentstring` is the last resort, `pre_hook` and ft has higher priority https://github.com/numToStr/Comment.nvim/blob/e30b7f2008e52442154b66f7c519bfd2f1e32acb/lua/Comment/utils.lua#L173-L185

I never noticed that usage, it actually should work since it uses set too. https://github.com/numToStr/Comment.nvim/blob/e30b7f2008e52442154b66f7c519bfd2f1e32acb/lua/Comment/ft.lua#L310-L314 But it's set only, you can't get the value with the same form.

@git-dimiz can you provide more details of how you do block commenting? I don't quite understand what is **do not work**. From what I can tell, you can test by...

>Deleting the keymaps causes some strange behavior where it delets the line. Make sure they're deleted before comment.nvim loads, in your case they seems to be removed completely as well...

Congrats :) The reason is as the readme states: >First you need to call the setup() method to create the default mappings. `opts` will be passed to `setup` behind the...

Smart case for matching items? Such as `Parameter`(a type from lsp) should be preferred over `parameter~`(a snippet) when `P` is typed. `min_keyword_length` and `score_offset` currently are not handling priorities very...

@Saghen opened in #1158 Besides smart case, I think exact matching might solve more than that(currently supports fuzzy match only as far as I know? Items from sources are always...