CodeReviewer.vim
Utility for code reviews (using quickfix) (by vim-scripts)
vim-bookmarks
Vim bookmark plugin (by MattesGroeger)
CodeReviewer.vim | vim-bookmarks | |
---|---|---|
3 | 9 | |
12 | 932 | |
- | - | |
0.0 | 0.0 | |
over 13 years ago | 4 months ago | |
VimL | Vim Script | |
- | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
CodeReviewer.vim
Posts with mentions or reviews of CodeReviewer.vim.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-04-28.
-
Plugin for code annotation without modifying the codebase
After posting this, I started looking into https://github.com/vim-scripts/CodeReviewer.vim. It's quite good and fulfils most of what I want. It's also really simple enough for me to modify if needed. This satisfies what I need, but please feel free to comment
-
Saving visited file locations to a temp list during a session and jump to them
This is the plugin which I had used earlier - https://github.com/vim-scripts/CodeReviewer.vim. I have modified it to be able to use different comment files and to jump to the file location for each comment (there are no tags like a quickfix). [This VS code extension](https://github.com/vsls-contrib/codetour) functionality is what I am eventually looking for. I still think a quickfix kind of interface would be the best.
-
CodeTour: Record guided “brown bag” intros for your codebases
For vim I use the CodeReviewer plugin [1] to capture comments for files. I modified it to use differently named comment files and to jump to the file locations from the comment line. I am planning to include support for hierarchical comments or referring other comment files from within one. Also the problem of tracking code changes or referring to a certain git commit is still there - in clearcase it can be easily done with a reference to the branch, but not sure how to do it in git.
[1] https://github.com/vim-scripts/CodeReviewer.vim
vim-bookmarks
Posts with mentions or reviews of vim-bookmarks.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-04-28.
-
How to annotate text files in vim/nvim?
Looks like https://github.com/MattesGroeger/vim-bookmarks won't do it, because:
-
Plugin for code annotation without modifying the codebase
I currently use https://github.com/MattesGroeger/vim-bookmarks but it's definitely not sufficient since it provides a tiny space for editing. It's good all-around, and I might spend time to modify it, but if there's an existing tool, I'd absolutely love that
-
Open small console
vim-bookmarks lets you mark and annotate locations in a file. Like if you were trying to understand some code and wanted to leave yourself notes but didn't want them in the file. I usually use todo comments, so I haven't actually tried this plugin.
- Are additional pickers supposed to appear in the Telescope menu ?
-
Doc Comments — GoogleDocs-inspired comments for Neovim
I made a plugin that adds GoogleDocs-style comments to Neovim. Basically, you can highlight a specific region of text and add an annotation to it. You can retrieve the annotation for an annotated text region by placing the cursor in that region and executing the GetComment command. This plugin is mainly intended for prose, where lines (paragraphs) are relatively long and annotating specific parts of a line is useful. If you only need to annotate on a per-line basis, then a plugin like vim-bookmarks may work just as well or better.
-
The Overly Persistent Marks Problem
So "Plan B" is now to experiment with vim-bookmarks. Bonus: there's a Telescope extension.
-
A better mark system for me
From what I've seen, people can only remember a few marks anyway, so having more wouldn't really help. If you really need more marks there are plugins like vim-bookmarks.
-
Create link to a location in any file
vim-bookmarks is a great plugin that simplifies dealing with marks yourself.
-
Can you place a mark of same letter in different places and cycle through them?
Have you considered using vim-bookmarks? It allows you to cycle through bookmarks among other features.
What are some alternatives?
When comparing CodeReviewer.vim and vim-bookmarks you can also consider the following projects:
codetour - VS Code extension that allows you to record and play back guided tours of codebases, directly within the editor.
telescope-vim-bookmarks.nvim - Integrates vim-bookmarks into telescope.nvim
github1s - One second to read GitHub code with VS Code.
vim-signature - Plugin to toggle, display and navigate marks
neovim - Vim-fork focused on extensibility and usability
DocComments - GoogleDocs comments for Neovim
vim-ripple - Makes Vim into a "scratchpad" tool for Python, Ruby, Perl, and/or Lua