Kyle Chui

First post about how to modify custom selections can be [found here](https://github.com/kylechui/nvim-surround/discussions/101#discussion-4230927).

Discussion on how documentation should be split/coordinated between the built-in help docs and wiki can be [found here](https://github.com/kylechui/nvim-surround/discussions/119).

Discussion on how filetype-specific default configurations should be exposed to the user can be [found here](https://github.com/kylechui/nvim-surround/discussions/137).

Just as a note: this might not be fixed until #113 is merged, since that branch has quite a few breaking changes and major restructuring. Note to self: The `.`...

Hmm... doing a bit more thinking, I'm not actually 100% sure this is possible to remedy with the current structure of the code

This might actually be incompatible with automatic indentation, at least if [this upstream feature](https://github.com/neovim/neovim/issues/19426) doesn't get added.

I would like to keep this plugin as minimal as possible, so maybe it would be more sensible for advanced users to define their own operator maps? Maybe something similar...

This seems like a doable/reasonable idea---I was originally going to complain about having to use `vim.fn.searchpos()` and `vim.fn.searchpairpos()`, but if the user provides the selections then we could be on...

@akinsho I 100% agree, which is why my original plan was to ignore non-textobject cases and focus only on extending functionality via defining *new* textobjects. I opened #52 a few...

@andrewferrier I'm not referring to the surrounds themselves when I say "textobject"---I'm referring to how textobjects are used (by both my plugin and vim-surround) to actually discern the location of...