nvim-surround VS vimtex

(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

The full changelog is here: https://github.com/lervag/vimtex/releases/tag/v2.14.

Feel free to open an issue on GitHub. Please take care to fill in the issue template; it's meant to help you provide useful details that make it easier for me to give a useful answer.

I use vimwiki almost daily, but it's not professional use, just daily notes and organizing my life. I started using zim but I found I really missed writing/editing with vim. Then I found vimwiki. There are things I'm not super happy about with it. I saw that /u/lervag (love his vimtex plugin) released a wiki plugin and I was/am interested in it, but I have so much in my wiki right now that I don't want to deal with conversion issues.

Definitely get vimtex and set it up so you can view the compiled document in one window, and your notes in the other. Get used to vim a bit with some vim tutorial (there are a bunch out there), and have latex shortcuts you use in all your documents.

I do think VSCode is a great tool and I recommend it frequently to people, but I still want to set the record straight here. Yes, vim is obviously limited in the sense that as a CLI app it doesn't draw it's own PDF or HTML windows, that's fair. But it can remote control your favorite PDF viewer or browser for roughly the same functionality. I'm currently writing my thesis using vimtex and it's quite smooth. And all the other stuff you mention is implemented quite competently by various plugins like vim-fugitive, coc.nvim, vimspector and copilot.vim.

Obsidian is limited by its use of markdown files. You can use Overleaf, Vimtex, or LaTeX workshop on VS Code to render your tex documents.

Some language-specific plugins like vimtex also include their own text objects.

I would post an issue on the VimTeX Github page: https://github.com/lervag/vimtex/issues. That way you might also get help to disable the possible indexing. I have also needed to disable project file scanning to stop Vim from hanging, when pressing Ctrl + N to perform simple auto-complete.

Absolutely VimTeX