Kyle Chui

As of right now, using the default bindings in insert mode, `stcode` does the behavior that you want. However, if you find yourself doing a lot of surrounds involving ``...

No worries! Maybe now you'll have some incentive to switch to `nvim-surround` :wink:

This seems to happen for me as well when building on NixOS using Coq 8.15 with the 8.15 branch. 

Hey @ejgallego, thanks for the fast response! I'm currently working in a group that relies on [QuantumLib](https://github.com/inQWIRE/QuantumLib), which has only been thoroughly tested for Coq versions 8.12 through 8.15. As...

@Zimmi48 Yeah I would definitely be open to trying to submit a PR to `nixpkgs`! Right now I have `coq-lsp` manually packaged using `pkgs.coq_8_15` in my flake's `devShell` and things...

No worries! The main reason I'm looking at 8.15 is because the library I'm depending on hasn't really been tested extensively on 8.16 and beyond. It may be true that...

> I notice some plugins have problems with passing an empty {} instead of () into setup. I have no idea if thats it but maybe? Shouldn't be an issue;...

Typically plugins like `targets.vim` or `mini.ai`, but what usually happens is that it causes unintended/unexpected behavior, not no behavior at all.

Ah good question, try `verbose xmap S` and see what pops up; you might have a completely different plugin/keymap overriding it.

Yeah try remapping either plugin's bindings to avoid conflicts, and that should fix things. Perhaps plugin authors should check for keymaps before setting them (mine included) :thinking: