info.vim
By HiPhish
vinfo
Vim info documentation reader, lets you read info pages within Vim or start it from the shell prompt (instead of Info) (by alx741)
Our great sponsors
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.
info.vim
Posts with mentions or reviews of info.vim.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-02-28.
-
vimscript over lua
As for writing plugins though, Lua beats Vim script any time of the day. I wrote info.vim back in the early days and it was a major pain to write in Vim script. If I had to redo it today I would 100% write it in Lua.
-
plugin annoncement - nvlime
Yeah, mapping a function instead of a mapping is even better. I just don't like if a predefined mapping is hard to remember or (even worse) conflicts with one of my existing mappings. Personally I like it the way Neovim's LSP client does it: you get a Lua (or Vim script) API that you can map yourself. In my info.vim I provide the commands :InfoNext, :InfoPrev and :InfoUp, but I also have a code snippet of reasonable default bindings in my README that people can just copy-past into their configuration. If they disagree with my defaults they can then change that snippet instead of having to fight my plugin to scrub away the defaults.
-
sidebar.nvim - A generic and modular lua sidebar
info.vim (my own)
-
Man pages in color, with links
I think we're all aware of the Man plugin, What I really want is info.vim being distributed by default aswell.
-
Future plans for Autotools
A wiki is not adequate documentation and I hate this trend of making documentation HTML only. Not everyone uses or even can use a web browser. GNU software has this great tool called Texinfo which lets you write a proper book-sized documentation with proper table of contents, chapters, and indexes. You can generate HTML, PDF, and most importantly info files. You can read info files in your terminal, in Emacs, or even in Vim (wrote a plugin for that).
vinfo
Posts with mentions or reviews of vinfo.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-02-15.
-
Man pages in color, with links
Didn't know that one, I have been using vinfo for a while, with vinfo () { nvim -c "Vinfo $@" -c 'silent only' } I'm gonna try the plugin you mentioned though, it has support for nodes while mine doesn't I think.
What are some alternatives?
When comparing info.vim and vinfo you can also consider the following projects:
vlime - A Common Lisp dev environment for Vim (and Neovim)
zeavim.vim - Zeal for Vim
sidebar.nvim - A generic and modular lua sidebar for Neovim
vim-devdocs - Look up keyword on https://devdocs.io from Vim
Vim - The official Vim repository
neovim - Vim-fork focused on extensibility and usability
investigate.vim - A Vim plugin for looking up documentation
nvim-metals - A Metals plugin for Neovim
nvlime - A Common Lisp development environment for Neovim
rofi - Rofi: A window switcher, application launcher and dmenu replacement
bat - A cat(1) clone with wings.