Tuesday, April 18, 2023

What are some alternatives of vim-surround

I use vim-surround so much that it has become an essential part of my Vim experience. I will continue to use it with gusto. But it does garner a question and that the facilities it provides are rather common in editing source code in general which leads me to wonder what are the "vim --clean" ways to perform the same actions that vim-surround offers.

Say I run Vim on a device where getting a git clone of the plugin difficult. Maybe it only has access to its own config and doesn't have a user accessible file system or something. What kinds of vanilla commands could be done to simulate what vim-surround does?

And if there isn't a clean alternative shouldn't the facilities vim-surround offeres be built into the base executable to begin with? I find it hard to believe we never needed to surround text in Vim prior to Tpope's amazing plugin. There has to have been more basic ways to accomplish such.


CONFIDENTIALITY NOTICE: The information contained in this message may be privileged and/or confidential. It is the property of CrowdStrike.  If you are not the intended recipient, or responsible for delivering this message to the intended recipient, any review, forwarding, dissemination, distribution or copying of this communication or any attachment(s) is strictly prohibited. If you have received this message in error, please notify the sender immediately, and delete it and all attachments from your computer and network.  

--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/c0b94c55-1020-40bc-a37e-d7da67833c2fn%40googlegroups.com.

No comments: