nvim-surround VS move.nvim

(Neo)vim supports plugins, which make your code editor much better. You need a faster way to comment stuff? Sure, here is nvim-comment. Now you need a better tool to surround text by certain characters? Alright, we also have nvim-surround. And this goes on for almost everything you ever needed. And in the rare case that you can't find a plugin for what you need: Write it yourself! It's very easy to write plugins, as vim and neovim both have a lot of functions that help with writing those.

So, I've been using floaterm and I like it a lot so far! But my ideal workflow would look like this

My guess would be to save the current location of the cursor, then iterate through all possible motions you want, i.e. a[, at, etc. After each time your operator marks get updated and you can save those locations, before resetting the cursor position to the original spot. Finally, take the innermost/closest pair of marks to be your selection. That would be my guess at least, I think your question is similar to how aliases are implemented in nvim-surround.

Thanks! I was using nvim-surround, but I didn't check dit

Oh sorry I forgot to add additional context. I already have keymaps that starts with m but not dealing visual mode. For example, I'm using ms, mr, md for nvim-surround. That is why I'm trying to map mi and ma, not just m for entering visual mode.

I'm trying out https://github.com/kylechui/nvim-surround (maybe a Lua port of that same plugin) and it it seems very capable. With some remapped shortcuts I think I can bend it to my will. Thanks!

The other plugin that can do this is kylechui/nvim-surround. Not sure how to set it up, though.

You could probably use a surround plugin like nvim-surround and then have an ftplugin that uses the buffer_setup function to create a custom surround.

require("ns-textobject").setup({}) -- from https://github.com/kylechui/nvim-surround/discussions/53#discussioncomment-3134891 require("nvim-surround").buffer_setup({ surrounds = { ["l"] = { add = function() local clipboard = vim.fn.getreg("+"):gsub("\n", "") return { { "[" }, { "](" .. clipboard .. ")" }, } end, find = "%b[]%b()", delete = "^(%[)().-(%]%b())()$", change = { target = "^()()%b[]%((.-)()%)$", replacement = function() local clipboard = vim.fn.getreg("+"):gsub("\n", "") return { { "" }, { clipboard }, } end, }, }, },

this might actually be a better surround plugin for surround https://github.com/kylechui/nvim-surround

there is also move.nvim which also allows you to move a visual block like that: https://github.com/fedepujol/move.nvim

The author of move.nvim has inactive his repo (https://github.com/fedepujol/move.nvim) and now this plugin comes, thanks so much <3

I've just updated my plugins and noticed that fedepujol/move.nvim was giving me an error.

I was trying to find a clean, concise way to set up my mappings through legendary.nvim for move.nvim which has separate commands for normal vs. visual mode. I didn't want a separate line for each mode (which before would be needed because different commands would be run based on the mode).