Is it possible to determine keymaps for any of the surround plugins?

[JJJHolscher]

mini.surround, nvim-surround and vim-surround all set keymaps, and they all are all mistaken they can claim 's' key, as though I wouldn't pick flash/leap any day of the year if it came to a fight.
and, it is a fight because none of the plugins expose settings that let you change their keymaps.

I can respect vim-surround the most for not pretending to be anything it's not, at least I can informedly take the appropriate action.

The docs of nvim-surround and mini.surround pretend otherwise however.
When you copy the docs and change the values there, the plugin just silently ignores you. If you send it the nvim_surround_no_mappings option, it will tell you that mappings are no longer handled through setup, you must use the global option. When I set

    nvim-surround.luaConfig.post = ''
      vim.o.nvim_surround_no_mappings = true
    '';

literally none of my plugins load anymore (I use combinePlugins if that matters).

The mini.surround nixvim docs itself makes no claim over shortcuts, but mini does make claims about mini.surround, but again the options there just get ignored.

So, is there a way to get any of these plugins to allow me to change their keybindings?

[khaneliman]

I do not think performance.combinePlugins is the cause here. It only changes how plugin packages are packed together; it does not rewrite plugin setup semantics or keymaps.

For current nvim-surround v4, upstream intentionally moved keymap configuration out of require("nvim-surround").setup(...):

• setup({ keymaps = ... }) now emits a v4 migration warning: https://github.com/kylechui/nvim-surround/blob/main/lua/nvim-surround/config.lua#L30-L31
• default mappings are created in the plugin file and gated by vim.g.nvim_surround_no_mappings, vim.g.nvim_surround_no_normal_mappings, etc.: https://github.com/kylechui/nvim-surround/blob/main/plugin/nvim-surround.lua#L2-L4
• upstream help says custom keymaps should disable defaults and bind the plugin mappings manually: https://github.com/kylechui/nvim-surround/blob/main/doc/nvim-surround.txt#L53-L59
• the v3 to v4 migration explicitly says the keymaps setup field was removed: https://github.com/kylechui/nvim-surround/blob/main/doc/nvim-surround.txt#L87-L89

So vim.o.nvim_surround_no_mappings is the wrong API. That is a Neovim option lookup, and there is no such option. For upstream v4 this should be a global, for example vim.g.nvim_surround_no_mappings, and it needs to be set before the plugin loads.

There is a narrower nixvim issue here: nixvim still exposes/documents plugins.nvim-surround.settings.keymaps, but with current packaged upstream v4 that field is stale. It should probably be removed/deprecated or replaced with guidance around globals plus explicit keymaps entries targeting the upstream <Plug> mappings. That is separate from combinePlugins.

For comparison, mini.surround does still support setup({ mappings = ... }). Upstream defines and validates config.mappings, then uses those values when creating keymaps:

• default mappings: https://github.com/nvim-mini/mini.nvim/blob/main/lua/mini/surround.lua#L68-L70
• validation/application: https://github.com/nvim-mini/mini.nvim/blob/main/lua/mini/surround.lua#L105-L107
• vim-surround-like mapping example: https://github.com/nvim-mini/mini.nvim/blob/main/lua/mini/surround.lua#L67

So the summary is: mini.surround mappings through nixvim settings should work; nvim-surround.settings.keymaps is stale for v4; vim-surround is a separate Vimscript wrapper with no dedicated nixvim mapping option.