dotfiles
vis
| dotfiles | vis | |
|---|---|---|
| 2 | 56 | |
| 183 | 4,175 | |
| - | - | |
| 6.5 | 8.2 | |
| about 1 month ago | 8 days ago | |
| Shell | C | |
| MIT License | GNU General Public License v3.0 or later |
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
-
Why Kakoune
I use NeoVim. I used Vim previously and just know the built in basics very well.
NeoVim incorporating Lua as a first class language has allowed plugin authors to build plugins that are faster and better than plugins for Vim written in VimScript (or other languages like python/typescript which are much slower).
There is a strong community for neovim on reddit, youtube, etc and plugin authors do a nice job of building tools that work with each other.
Setting it up I agree is a pain, but once done its very little maintenance/work. Even when I've had to 'redo' my setup (eg swithing package managers like vim plug to packer to lazy) its been easy and under 15 or so minutes.
I edit minor things in my config every few months. Everything flows quite nicely now and breaking changes are far less common than they used to be (at least among the plugins I use).
My vim config if you're curious (along with the rest of my dotfiles): https://github.com/sbernheim4/dotfiles/tree/master/vim
-
Neovim/LSP skeleton
Mine's not very bare bones, but its also not massive. I like to think it's decently set up and readable. Hopefully its possible for you to use some parts: https://github.com/sbernheim4/dotfiles
vis
- Vis: A vi-like editor based on Plan 9's structural regular expressions
- Oasis – a small, statically-linked Linux system
-
Why Kakoune
> I wonder if the author has ever heard of vis[0]
Yes.
https://github.com/martanne/vis/wiki/Differences-from-Kakoun...
https://github.com/mawww/kakoune/wiki#onboarding
> which imho fulfills far better each one of those premises
Not very motivated for such a harsh critic..
-
The Text Editor Sam by Rob Pike
If you want an editor that uses Sam's structural regexes with keyboard-focussed vi-style interaction, you might be interested in https://github.com/martanne/vis
-
Can we write a Neo-vim Successor using rust?
Not Rust, but there's vis which aims to be a Vi(m) inspired editor with Sam's structural regular expressions.
-
Met that guy one the train yesterday
I do not use vim nor a WM nor a Thinkpad, but I do use vis. It's great.
-
Helix: Release 23.03 Highlights
> They either break from Vim's model (kakoune, helix) or follow Vim along with all it's flaws (Neovim, Vis).
I am sincerely curious of what flaws from Vim has Vis inherited, in your opinion.
I have the impression that the design idea of Vis is taking only the modal design of Vi (not Vim), plus the structural regular expressions of Sam, then make it as clean as possible with programmability via Lua plugins.
In fact, the state non-goals [1] seems to clearly distant itself from Vim.
[1]: https://github.com/martanne/vis#non-goals
- Helix: Post-Modern Text Editor
- Mle is a small, flexible, terminal-based text editor written in C
What are some alternatives?
nvim-config
kakoune - mawww's experiment for a better code editor
kakoune-wakatime - WakaTime! For Kakoune! Yay!
micro-editor - A modern and intuitive terminal-based text editor
helix - A post-modern modal text editor.
nextvi - Next version of neatvi (a small vi/ex editor) for editing bidirectional UTF-8 text
golf - Some vimgolfs challenges and along with Kakoune solutions
vim-visual-multi - Multiple cursors plugin for vim/neovim
mle - flexible terminal-based text editor (C)
nvim-select-multi-line - Neovim plugin. select multiple lines that are not adjacent.
neovim - Vim-fork focused on extensibility and usability
helix - A post-modern modal text editor.