plan9port
kakoune
plan9port | kakoune | |
---|---|---|
28 | 110 | |
1,559 | 9,589 | |
0.3% | - | |
5.0 | 9.7 | |
30 days ago | 6 days ago | |
C | C++ | |
GNU General Public License v3.0 or later | 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.
plan9port
-
Only9Fans
Acme is genuinely worth trying, you can run it on Linux/Mac without a VM [1]. I'm pretty sure Russ Cox [2] and Rob Pike use it as their daily driver which is insane because it doesn't even have syntax highlighting. I used it for years when I was in school as an exercise in masochism, but I learned a lot about Unix, and the mouse-driven workflow actually grew on me.
[1]: https://9fans.github.io/plan9port/
-
Show HN: Towards Oberon+ concurrency; request for comments
[2] https://9fans.github.io/plan9port/
-
A pure C89 implementation of Go channels, including blocking and non-blocking selects
If you find it too complicated and closely tied to Go internals, you can also check out Plan 9 from User Space's version, which is itself based on libthread from Plan 9 starting from 3rd edition, which is itself based on Alef's implementation of channels (Alef is Go's grandfather).
- A tutorial for the Sam command language (1986) [pdf]
- Makefile Tutorial
-
Mk: A Successor to Make [pdf]
I tried plan9port's mk for a moment out of curiosity. I quickly ran into an annoying usability problem: it compares file mtimes with second accuracy.
https://github.com/9fans/plan9port/blob/cc4571fec67407652b03...
With sub-second build times for individual targets, this causes mk to needlessly recompile files because the target may have the same mtime as the prerequisites.
- Plan 9 from User Space
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?
sam - An updated version of the sam text editor.
helix - A post-modern modal text editor.
plan9-1e - Mirror of Plan 9 1st Edition from p9f
micro-editor - A modern and intuitive terminal-based text editor
Fontpkg-PxPlus_IBM_VGA8 - A monospace system font in the styles of regular, italic and underline.
vis - A vi-like editor based on Plan 9's structural regular expressions
Shrine - A TempleOS distro for heretics
Yuescript - A Moonscript dialect compiles to Lua.
fsv - fsv is a file system visualizer in cyberspace. It lays out files and directories in three dimensions, geometrically representing the file system hierarchy to allow visual overview and analysis.
doom-emacs - An Emacs framework for the stubborn martian hacker [Moved to: https://github.com/doomemacs/doomemacs]
mk - make remade
neovim - Vim-fork focused on extensibility and usability