fix: take into account a nil returned by get_parser

[faergeek]

Fixes #517

Related change in neovim:
neovim/neovim@fd1e019

[JamesWidman]

Given that there's about 2 years of PRs that have not yet received a reply from the repo owner, it looks as if the repo is unmaintained, so it might be best if someone were to become a maintainer with their own fork.

[WillScarlettOhara]

Or switch to mini.comment or ts-comments.nvim ;)

[rseichter]

@WillScarlettOhara Fair point. I tried mini.comment and can't spot a difference so far. Apparently I don't use any particularly fancy moves when dealing with comments. 😉

[faergeek]

@rseichter there's also a builtin commenting support based on mini.comment. :h commenting

[rseichter]

@faergeek So what you are telling me is that I could have dropped Comment.nvim a full two years ago, and never have run into the nil problem at all? That would have been nice...

[faergeek]

@rseichter Yep. So all that's left is to invent a time machine :-)

[rseichter]

@faergeek Tempting. Alas, I am a little busy right now, so I'll have to look into building a time machine some other... time. Or is it "will have been looking"? Dang, temporal grammar is hard. 🤓

[cschindlbeck]

I replaced numToStr/Comment.nvim with echasnovski/mini.comment in my Lazy setup, here are the changes you need:

cschindlbeck/nvim@7d954db

[rseichter]

@cschindlbeck The paths for the mini plug-in suite have changed, see here. Besides, as mentioned above, the mini.comment plugin was integrated into Neovim two years ago, i.e. loading this plugin is no longer required.

[cmon1701]

Hello,
why is this pull request not accepted yet, is there a problem?
(I'm no expert on Github).

[rseichter]

As mentioned in this comment, there have been no commits made in this repository for two years. That seems to line up with the time of Neovim adding its own, internal comment support. I therefore share the impression that the Comment.nvim repo should be considered dead.