.dotfiles VS info.vim

Compare .dotfiles vs info.vim and see what are their differences.

Our great sponsors
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • WorkOS - The modern identity platform for B2B SaaS
  • SaaSHub - Software Alternatives and Reviews
.dotfiles info.vim
3 5
24 -
- -
8.0 -
2 months ago -
Lua
- -
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.

.dotfiles

Posts with mentions or reviews of .dotfiles. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-02-28.

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
    4 projects | /r/neovim | 28 Feb 2023
    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
    2 projects | /r/neovim | 25 Dec 2022
    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
    10 projects | /r/neovim | 19 Sep 2021
    info.vim (my own)
  • Man pages in color, with links
    3 projects | /r/neovim | 15 Feb 2021
    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
    1 project | /r/programming | 26 Jan 2021
    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).

What are some alternatives?

When comparing .dotfiles and info.vim you can also consider the following projects:

vim-tmux-navigator - Seamless navigation between tmux panes and vim splits

vlime - A Common Lisp dev environment for Vim (and Neovim)

twf - Standalone tree view file explorer, inspired by fzf.

vinfo - Vim info documentation reader, lets you read info pages within Vim or start it from the shell prompt (instead of Info)

dotfiles

sidebar.nvim - A generic and modular lua sidebar for Neovim

better-vim-tmux-resizer - Resize tmux panes and Vim windows with ease

Vim - The official Vim repository

tmux-suspend - Plugin that lets you suspend local tmux session, so that you can work with nested remote tmux session painlessly.

neovim - Vim-fork focused on extensibility and usability

dotfiles - My dotfiles managed with chezmoi

nvim-metals - A Metals plugin for Neovim