Add scheme extension to list

[ekaitz-zarraga]

Using this PR to let you know about my Scheme extension.

I think it mostly works, but I had a hard time making it understand the difference between a standard comment (;) and a comment from the srfi 62 (#;) that affects the following expression. I'm not sure about how to deal with some other things either but I'll go improving it as I use it in my everyday work (I'm a heavy scheme user).

Thanks for this plugin, it's cool that it's based on treesitter, I was using vim-paredit before, which is based on regular expressions and has a lot of issues with large files. I had a lot of out of sync issues... it was hard to deal with.

This is way better!
I'll let you know about my experience using this.

[julienvincent]

Super cool! I'm glad you're finding this plugin useful!

Thanks for the extension - you are the first third party to create an extension for this!

I'm not sure about the comment issue, were you having issues with how nvim-paredit is handling comments or treesitter?

Also happy to help out with any other issues you might be having, let me know.

[ekaitz-zarraga]

Super cool! I'm glad you're finding this plugin useful!

Thanks for the extension - you are the first third party to create an extension for this!

Thank you!

I'm not sure about the comment issue, were you having issues with how nvim-paredit is handling comments or treesitter?

Treesitter was calling the online comments and the srfi 62 comments comment so it was hard to differentiate one from another.

Also happy to help out with any other issues you might be having, let me know.

I'm looking for a balancer too, I was using vim-paredit before and if i deleted a line with parenthesis and things like that it kept the balance. I found nvim-parinfer but it does other extra stuff I don't want. I just want the file to keep the parenthesis coherent. Are you planing on working on that? I could help.

[julienvincent]

Not planning on working on that. I want to keep this plugin specific to structural editing - I think parinfer should probably be handled by a separate plugin.

I would be willing to ensure that nvim-paredit did not conflict with parinfer plugins - so if any changes needed to be made to nvim-paredit to ensure they worked side-by-side I think that would be acceptable.