tcomment_vim
vim-mundo
tcomment_vim | vim-mundo | |
---|---|---|
8 | 12 | |
1,390 | 779 | |
- | - | |
3.7 | 2.3 | |
about 1 month ago | about 1 month ago | |
Vim Script | Vim Script | |
GNU General Public License v3.0 only | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
tcomment_vim
- My Solution to Block Comments
-
What are your must-have vim/nvim extensions?
tomtom/tcomment_vim - Does embedded filetypes unlike tpope/vim-commentay
-
How do I modify this function to comment lines in visual mode?
-- a proud tcomment user.
-
Comment.nvim: Simple and powerful comment plugin for neovim. Supports commentstring, dot repeat, left-right/up-down motions, hooks, and more
Yeah, you are right but currently, most of them only support commentstring which means only single-line comments. But block comments are sometimes useful too. Also, I was using tcomment before, which IMO is the best commenting plugin for vim/neovim as it supports left-right motion comments which I haven't seen in any Lua plugin as of now. So that's why I decided to write this plugin to honor tcomment and to port all of its features to Lua :)
-
Where should fingers be placed on the keyboard? :s/^/#/
Plugin 'https://github.com/tomtom/tcomment_vim' Comment out code with this plugin, instead.
-
nerdcommenter seems to better figure out what comment syntax to use than vim-commentary, but i like vim-commentary more at everything else
That said, I switched to tcomment years ago because it better detected single va multi-line comments for me.
-
(neo)vim users, what does your haskell setup look like?
tcomment_vim
-
vim-commentary block vs line comments
Vim-commentary is great, but AFAICT, only supports one commenting style per file type. tcomment.vim supports line, inline, and block styles.
vim-mundo
-
Is there a way to record and view all commands used on the file?
there's also telescope-undo and vim-mundo
-
Recommended minimal set of plugins for a great experience
I don't always need it, but when I do I find vim-mundo incredibly helpful. Understanding the vim undotree is hard without a visualization and mundo's ability to search my undo chunks makes it easy to revive some previous change that wasn't committed to version control.
-
Undo tree?
Still using mundo here (https://github.com/simnalamburt/vim-mundo)
-
How to navigate back and forth through last edits?
You mean undo/redo? that's u and . To view undos visually you can use a plugin like [vim-mundo](https://github.com/simnalamburt/vim-mundo
-
Take More Screenshots
I'm glad you found something that works for you, and I don't mean to dissuade you even if I could, but to me that feels like an antipattern if you only use it for typed text.
Consider that with a text editor like Vim, for example, you can "time travel" [0] through your file's edits, or even have undo branches/trees [1][2] available per file. That saves you the trouble of having to transcribe text from screenshots, and also barely uses any storage space.
Plain text is also highly more portable and more likely to be recoverable in case of drive failure or file corruption.
Additionally, or alternatively, you could try any sort of manual versioning system or background automatic backup solution that keeps versions of files as you work on them.
[0]: https://vimtricks.com/p/vimtrick-time-travel-in-vim/
[1]: https://neovim.io/doc/user/undo.html#undo-tree
[2]: https://github.com/simnalamburt/vim-mundo
-
What are your must-have vim/nvim extensions?
mundo undo tree
-
Time traveling with Vim
It's not just minutes either, you can do seconds with s, hours with h, days with d and get this - "writes" with w. You can also just simply go back to an arbitrary n number of buffer states before; but just like writes, that's hard to keep track of mentally and instead you should probably use a proper plugin for that.
-
What do you prefer for NOTE TAKING or similar purposes?
I used to use Typora before I got into Neovim and realised that it wasn't free software either. Now I'm quite satisfied with my current setup, which uses: - aerial.nvim for header outline and navigation - run-code.nvim for running code blocks - vim-mundo for persistent undo history traversal (like Mac's time machine) - Prettier for auto-formatting Markdown as well as code blocks to their respective languages
-
Piece of mind for a reddit noob.
Using a plugin like undotree (or Gundo, or Mundo) to visualize the edit history is by far the most practical solution to OP's problem, and I'm shocked you're the only person to suggest it.
-
Why is it so hard to see code from 5 minutes ago?
There's a fork called mundo which has an inline diff mode that I'm a big fan of — https://github.com/simnalamburt/vim-mundo
What are some alternatives?
vim-commentary - commentary.vim: comment stuff out
undotree - The undo history visualizer for VIM
nvim-ts-context-commentstring - Neovim treesitter plugin for setting the commentstring based on the cursor location in a file.
undo-tree
Comment.nvim - :brain: :muscle: // Smart and powerful comment plugin for neovim. Supports treesitter, dot repeat, left-right/up-down motions, hooks, and more
gundo.vim - A git mirror of gundo.vim
kommentary - Neovim commenting plugin, written in lua.
gruvbox - Retro groove color scheme for Vim - community maintained edition
vim-sandwich - Set of operators and textobjects to search/select/edit sandwiched texts.
riscv-v-spec - Working draft of the proposed RISC-V V vector extension
vim-visual-star-search - Start a * or # search from a visual block
StyleCopAnalyzers - An implementation of StyleCop rules using the .NET Compiler Platform