nnn.vim
kakoune
Our great sponsors
nnn.vim | kakoune | |
---|---|---|
17 | 110 | |
645 | 9,581 | |
- | - | |
2.9 | 9.7 | |
11 months ago | 3 days ago | |
Vim Script | C++ | |
BSD 2-clause "Simplified" License | The Unlicense |
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.
nnn.vim
-
Using neovim without a file tree plugin
So these days I just use https://github.com/mcchrish/nnn.vim
- Call for help: please pitch in to fix outstanding nnn.vim issues!
-
minimal-nnn.nvim - the most minimal nnn plugin ever
Yeah I'm not sure what the point is of such a minimal plugin when nnn.nvim and nnn.vim already exist which both do do that, and more.
- Permanent fixed File Explorer in Neovim
-
"Emacs is bloat and memory intensive"
file managers or project/directory viewer
-
NERDTree alternative
nnn with nnn.vim because I'm lazy and I already use nnn on its own.
- Am I the only one frustrated when jumping in nvim-tree when hitting Ctrl-O ? Can I avoid this ?
-
[PLUGIN] opens xplr inside nvim, and hosts a msgpack client inside xplr!
Created this plugin because I've switched from Ranger to xplr.nvim as my daily driver and wanted a cleaner interaction between the 2 programs. I like to sometimes use my file manager within neovim, and would prefer not to use shell to exchange data between them. Because xplr now uses LuaJit, pynvim/python isn't needed etc (like other msgpack plugins) It aims to support the "regular" features (opening files in nvim, switch cwd etc) like in rnvimr or nnn.vim
-
Vim Users! Share your Clever Configs and Plugin Setups (or learn something new)🔥
You can try nnn.vim, a vim-ish file picker as well as fast and full-featured file manager within vim.
-
Terminal file manager nnn v4.1 Sake released!
You'll invoke it as a floating window. See nnn.vm for usage.
kakoune
- Multi-cursor code editing: An animated introduction
-
Helix: Release 24.03 Highlights
Helix's modal editing is based on Kakoune's modal editing which is like an evolution to Vim's modal editing. You can think of it as being always in selection (visual) mode. https://github.com/mawww/kakoune?tab=readme-ov-file#selectio...
- Kakoune
- Kakoune Code Editor
-
A tutorial for the Sam command language (1986) [pdf]
And while it doesn’t use the sam language precisely, I think in the broader “postfix Vi with visual feedback” category Kakoune[1] also warrants mentioning. The command language, in my experience, feels much more logical than that of Vis coming from a blank slate (things might be different if you come from Vim, but even when I used Vim regularly I never used the editing language that much exactly because I could never remember the damn thing).
And having mentioned Kakoune it’d probably be unfair to then not mention Helix[2]. It has a very similar editing language, but it’s a fairly anti-Unix everything-bolted-in affair on the inside (“everything works out of the box” being the advertising take) compared to Kakoune’s Acme-inspired no-scripting scripting (there’s an ex-style command to exec a user program that can then drive the editor over stdio RPC, a set of hooks, and that’s it). So if you’ve come for the Plan 9 feels, I don’t expect Helix to be that appealing. It’s still a good editor, nevertheless.
[1] https://kakoune.org/
[2] https://helix-editor.com/
-
What is the best book for complete beginner?
You can take a look at kakoune. The source code (excluding documentations, test cases, customizations etc.) is less than 40k. It is, IMHO, a show case of a C++ project in use.
-
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..
-
Understanding the Origins and the Evolution of Vi and Vim
I've been using Vim for years, but if there was one thing I could change, it would be the verb-noun order. The Kakoune[1] editor behaves mostly like Vim, but where Vim has `dw` as "delete word", Kakoune has it backwards: `wd`.
It might sound minor, but by placing the range first, Kakoune can give a preview of what will be changed. The longer or more complicated the command, the more this feature shines.
Strictly better as far as I know. A shame my muscle memory, and all default installations, are still stuck with Vim.
[1] https://kakoune.org/
- Ask HN: Where do I find good code to read?
-
Helix editor: Make HTTP requests and insert JSON
Helix is a postmodern text editor built in Rust built for the terminal. It is inspired by Kakoune, another Rust based text editor. Helix has got multiple selections, built-in Tree-sitter integration, powerful code manipulation and Language server support.
What are some alternatives?
fff - 📁 A simple file manager written in bash.
helix - A post-modern modal text editor.
ranger - A VIM-inspired filemanager for the console
micro-editor - A modern and intuitive terminal-based text editor
nvim-tree.lua - A file explorer tree for neovim written in lua
vis - A vi-like editor based on Plan 9's structural regular expressions
joshuto - ranger-like terminal file manager written in Rust
Yuescript - A Moonscript dialect compiles to Lua.
xplr.vim - Fork of https://github.com/mcchrish/nnn.vim modified to work with xplr. Until xplr has its own plugin.
doom-emacs - An Emacs framework for the stubborn martian hacker [Moved to: https://github.com/doomemacs/doomemacs]
xplr - A hackable, minimal, fast TUI file explorer
neovim - Vim-fork focused on extensibility and usability