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.
add-ed
-
Hired: A Modern Take on 'Ed'
It isn't too late yet, you can be the one to bring The Standard Editor to the Webshit masses!
The backing library https://github.com/sidju/add-ed could either be run through https://neon-bindings.com/ , or compiled into web assembly for that matter. Should just be a weekend project to create an electron `ed`, and if that isn't sufficiently bloated you can `node install everything`.
-
pacdef, the declarative package manager for Arch, releases v1.0.0
When/if "later (TM)" occurs, I recommend defining your tests using fixtures/check functions. For example, my library requires a fair bit of work both to setup an arbitrary state and read the resulting state after a test. Since that is needed in every test I have abstracted it into this function https://github.com/sidju/add-ed/blob/main/tests/shared/inner_fixture.rs , which I then create more readable/usable wrappers around here https://github.com/sidju/add-ed/blob/main/tests/shared/fixtures.rs .
-
The ! command, what do you use it for?
( The ed clone I am writing: https://github.com/sidju/hired , and its backend: https://github.com/sidju/add-ed )
- Intuitive: A crate for writing TUIs declaratively
hired
- Hired: A Modern Take on 'Ed'
-
The ! command, what do you use it for?
( The ed clone I am writing: https://github.com/sidju/hired , and its backend: https://github.com/sidju/add-ed )
- Thoughts on some of the actively developed text editors written in Rust?
-
Nano vs Vim (text editor)
OR, use modern ED! https://github.com/sidju/hired Syntax highlighting, command history and replaceable backend.
-
Interface test for all structs that implement a trait
My current solution is to have it written implementation agnostic for the only implementation that currently exists. ( Seen here: https://github.com/sidju/hired/blob/bde09775eca11c3f98f88f29eb006f4dc6e057fd/src/buffer/vecbuffer.rs#L249 ) In the longer term I intend on writing a macro that essentially creates that exact test but replaces the constructor ("VecBuffer::new()") with whatever string is given to the macro. That should work well, but will have to wait a little.
What are some alternatives?
scripts - My ~/bin
lapce - Lightning-fast and Powerful Code Editor written in Rust
jless - jless is a command-line JSON viewer designed for reading, exploring, and searching through JSON data.
kibi - A text editor in ≤1024 lines of code, written in Rust
CTRLGGitBlame.vim - Append git blame information to the output of <C-g>
pepper - simple and opinionated modal code editor for your terminal
intuitive - A library for building declarative text-based user interfaces
glyph - My own personal code editor built with Rust + OpenGL
dotfiles - ❄️ My dotfiles for NixOS and macOS as a Nix flake. Neovim, Fish shell, Wezterm, etc.
neovide - No Nonsense Neovim Client in Rust
amp - A complete text editor for your terminal.
zee - A modern text editor for the terminal written in Rust [Moved to: https://github.com/zee-editor/zee]