rune | remacs | |
---|---|---|
8 | 19 | |
387 | 4,570 | |
- | 0.1% | |
9.6 | 1.8 | |
13 days ago | about 3 years ago | |
Emacs Lisp | Emacs Lisp | |
GNU General Public License v3.0 only | GNU General Public License v3.0 only |
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.
rune
-
The Emacsen family, the design of an Emacs and the importance of Lisp (2023)
Two projects that may be of interest, related to this topic:
- Rune (https://github.com/CeleritasCelery/rune) - A re-implementation of Emacs but in Rust (like Remacs, but actively developed)
- Pimacs (https://github.com/federicotdn/pimacs) - Same, but using Go (created by me, but developed in a very slow pace)
-
Text Editor Data Structures
[2] https://github.com/CeleritasCelery/rune/issues/17#issuecomme...
- rune: Rust VM for Emacs
-
Design of Emacs in Rust
I second this ! I had trouble finding the github link, but here is is https://github.com/CeleritasCelery/rune
- Rune: An experimental Emacs Lisp interpreter written in Rust
-
Implementing a safe garbage collector in Rust
> How is anything rooted here? The lifetime changed from 'arena to 'root but I don't see a root being created.
In this example, the Vec has been rooted previously. So pushing an object into the Vec will make it "transitively" rooted (accessible from the root). You would root a struct with the root_struct![1] macro, which works very similar to the root! macro shown in the post.
However you made you realize one error; The rooted `Vec` in the example you pointed is a by value type, but in the implementation you can only get references to rooted structs, so that example needs to be updated.
> But later we see roots not obeying a LIFO order, under "Preventing escapes" where roots are dynamically created and destroyed in an arbitrary order.
Objects are just a copyable wrapper around a pointer, so they are not the part that has the LIFO semantics. inside the root! macro[2] there is a `StackRoot` type that is the actual "root". The object just borrows from that so that is has a 'root lifetime and is valid post gc. The actual root struct is not exposed outside of the macro.
I hope this makes the distinction between "roots" and "objects" clearer. Objects are just pointers to heap data. When we root an object we store the data it points to on the root stack and create a new `StackRoot`. Then we say this object is rooted. But the struct that "does the rooting" is inside the macro and not exposed. Rooting a struct works similarly.
[1] https://github.com/CeleritasCelery/rune/blob/5a616efbed763b9...
-
I came to the conclusion that I wont learn Elisp...unless...
Hack on Rune
remacs
-
Given how powerful Emacs is and how important it has been for my computing over the past four decades, I think it would be more useful to me for people to label all non-emacs articles [Not Emacs]
you might want to check remacs, a rewrite of emacs in Rust.
-
What would you rewrite in Rust?
Emacs. There's Remacs… well, there was Remacs. It seems the project has fizzled out.
-
Design of Emacs in Rust
Remacs
-
I made an OpenGL-like renderer to learn Rust. Had an amazing developing experience!
Well...
-
Linux Kernel 6.1 Released with Initial Rust Code
here are a few
-
Financial resources required to rewrite the Emacs core
[1] https://github.com/remacs/remacs
- Stallman when someone installs NVIDIA drivers on their desktop
-
How do the neovim plugins for OrgMode and Magit compare with the real thing?
Yeah most likely they won't mature at all. Many of the emacs-ng folks were doing an incremental Rust rewrite called Remacs before abandoning that. It's great to see these people having fun, but I wouldn't bet on them to be around in the long term.
- Implementing a safe garbage collector in Rust
-
Emacs as a universal front-end interface
There are alternative Emacs-like editors implemented in better languages like Common Lisp like Climacs which seem to be no longer maintained, there have been attempts at rewriting Emacs in Guile Scheme like Guile Emacs which have fizzled out, there are more recent attempts at implementing Emacs in Rust which isn't even a Lisp. I am really hoping Guile Emacs or Climacs see a resurrection, that or some other Lisp-based Emacs clone comes along that manages to supplant GNU Emacs. If more people would put efforts into projects like these, Emacs as a platform would be so much better than something like Electron.
What are some alternatives?
dotemacs
emacs-ng - A new approach to Emacs - Including TypeScript, Threading, Async I/O, and WebRender.
immer - Postmodern immutable and persistent data structures for C++ — value semantics at scale
emacs-everywhere - Mirror of https://git.tecosaur.net/tec/emacs-everywhere
c-rrb - RRB-tree implemented as a library in C.
vifm - Vifm is a file manager with curses interface, which provides Vim-like environment for managing objects within file systems, extended with some useful ideas from mutt.
gc-arena - Incremental garbage collection from safe Rust
emacs-application-framework - A free/libre and open-source extensible framework that revolutionizes the graphical capabilities of Emacs, the key to ultimately Live in Emacs [Moved to: https://github.com/emacs-eaf/emacs-application-framework]
racket - The Racket repository
magit - It's Magit! A Git Porcelain inside Emacs.
boa - Boa is an embeddable and experimental Javascript engine written in Rust. Currently, it has support for some of the language.
turbo-log - Fast log message inserting for quick debug.