Kyle Chui

It usually is quite hard to get a sense for how many people actually *want* this feature. I'll try to remember to make note of it in the next release...

Still delaying this feature request until later, but from a UX standpoint I think it might make sense to make it an additional (and optional) key into each surround, i.e....

For those that are interested, someone else seems to have implemented this functionality as its own plugin: https://github.com/XXiaoA/ns-textobject.nvim Note: `nvim-surround` is still required

@smjonas It seems like this is slightly different; your feature request was about surrounding larger selections (e.g. two words at a time), whereas this seems to be about surrounding a...

Hi there, I'm a big fan of this plugin and would very much like to have this as a feature; far too many times I've decided to comment out a...

I don't think I'm quite following why having `vim.bo.commenstring` as a fallback implies that pattern matching is infeasible. As for your other point, would finding the length of the match...

> After taking a another look in the code; the reason the left/right part should be kept static is to be able to comment the line initially. Oh wow this...

Ah, let me try and rephrase what my initial idea was: * The user passes in some selection and calls one of the commenting functions * The plugin traverses the...

Thanks for the high-level description! Yeah it does seem like quite a bit of extra work, especially because it seems like this would need to be "hard-coded" to a certain...

With the introduction of #136, some configuration options have been renamed to better reflect their actual purpose: * `highlight_motion` → `highlight` * `NvimSurroundHighlightTextObject` → `NvimSurroundHighlight` * The `textobject` key for...