Our great sponsors
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
-
vimscript over lua
I still have my init.vim from back when I used to use vim: https://github.com/MunifTanjim/dotfiles/blob/c73af0ae16/private_dot_config/nvim/init.vim
-
zed - yet another plugin manager for zsh. Nothing fancy, nothing new. Just does the basic stuffs - pulls, compiles and loads the plugins... does some completion stuffs. Fairly simple implementation with about 300 LOC. Why? 'cause I used zinit before and it vanished recently... so why not? 🤷🏼♂️
In case anybody's interested, here's my own .zshrc using it: https://github.com/MunifTanjim/dotfiles/blob/9aa77d15/private_dot_config/zsh/dot_zshrc.tmpl
-
Use same tmux keybindings on both your local and nested remote tmux sessions painlessly! This lets you suspend your local session, so that you can interact with the nested remote session directly.
Tmux config: - https://github.com/MunifTanjim/.dotfiles/blob/1067dcc80da5549a4fe058a13d665145e48d8ad4/dot_tmux.conf#L22-L73
info.vim
-
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).
What are some alternatives?
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