sapling
symex.el
Our great sponsors
sapling | symex.el | |
---|---|---|
7 | 18 | |
705 | 254 | |
- | 1.2% | |
3.7 | 6.2 | |
3 months ago | 13 days ago | |
Rust | Emacs Lisp | |
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.
sapling
- Sapling: A highly experimental vi-inspired editor where you edit code, not text
-
Emacs Is Not Enough
Basically, when you say 'structural editing', do you mean making an AST for every kind of input and having a modal command language that permits traversal and editing of that AST. Like what sapling https://github.com/kneasle/sapling is attempting to do ?
-
Why are we storing source code in plaintext?
For example, you can edit the AST directly: https://github.com/kneasle/sapling
- Sapling livestream
-
Rust coding livestream - building Sapling, a better code editor
Livestream link here: https://youtu.be/dJtLEGOFYC0 Code here: https://github.com/kneasle/sapling
-
Show HN: Experimental Semantic Code Explorer
There's a text editor being developed that edits code based on nodes of its AST representation - https://github.com/kneasle/sapling
symex.el
-
Sapling: A highly experimental vi-inspired editor where you edit code, not text
I also recommend symex[1]. Although it is more “locked-in” to s-expressions than other solutions (which takes some getting used to at first), I find that for me this is exactly what makes movement feel much more intuitive and editing much more precise.
The one thing I don’t like is that symex depends on so many other plugins (especially Evil, which I am trying to swap out with the more lightweight meow), but this will apparently change soon. They are also working towards support for non-Lisp languages via tree-sitter, but I don’t know how well it works.
[1]: https://github.com/drym-org/symex.el
-
We've launched Attribution Based Economics
The pilot projects (including Symex.el) are accepting financial contributions and will distribute them to sources of value including contributors and antecedent projects in a process that we all have a say in.
-
Tree-sitter starter guide
This is a really useful synopsis. symex has recently had TS support merged in, and apparently includes navigation and structural editing similar to its lisp-like language capabilities. I think it's still early going and I haven't tested, but may be worth a look.
- Learn Lisp the Hard Way
-
What modal sexp editing mode should I switch to?
Has anyone used symex.el without evil? I just learned it can be use with vanilla emacs (despite the 2nd word in its tagline). I also learned they have a tree-sitter branch which will expand its powers to many languages.
-
Advice on config hacking / yak shaving / bikeshedding
I started out using evil, but now I mostly use Symex. (Structural editing. non-lisps support wip for those sad moments you can't use lisp). For now depends on evil, but could be separated.
-
You are invited to the First Congress for Attribution-Based Economics!
The purpose of this congress is to engage in the process of Dialectical Inheritance Attribution, which is a collective process by which we apply agreed-upon standards to the task of appraising and attributing the value of work done in the world. At this initial congress, there are two open source projects on the agenda to be appraised: Symex.el which is an Emacs extension, and Qi, which is a functional DSL on the Racket platform.
- symex.el: An evil way to edit Lisp symbolic expressions ("symexes") as trees in Emacs
-
paredit based on treesitter
symex has a branch that’s been working on integrating with tree-sitter.
-
Paredit 25 Released
If you want to go nuts with structural editing you may also want to check out symex mode: https://github.com/drym-org/symex.el
It uses paredit (among others) for its low level functionality, but the vim-style modal interface allows you to manipulate the tree structure with single keystrokes in a precise and very expressive way. Keep in mind that you have to actively learn how to use it and it will feel awkward at first (similar to how vim feels for beginners), but I find the editing experience very pleasent and smooth after I got used to it.
Another thing I really like about it is that you can still switch to normal mode and it doesn’t get in your way like other plugins where I had to change my keybindings all the time because the amount of convenient shortcuts is still quite limited in the end. This modal switching to different editing contexts (or languages?) is something I feel should be explored much further.
What are some alternatives?
rustpad - Efficient and minimal collaborative code editor, self-hosted, no database required
lispy - Short and sweet LISP editing
silver_editor - A small editor for quicksilver and Mergui
elisp-tree-sitter - Emacs Lisp bindings for tree-sitter
xedel - Keyboard-centric modal code editor, built with nodejs and GTK
smartparens - Minor mode for Emacs that deals with parens pairs and tries to be smart about it.
amp - A complete text editor for your terminal.
gopcaml-mode
lynx - A basic text editor in Rust.
emacs - Mirror of GNU Emacs
kibi - A text editor in ≤1024 lines of code, written in Rust
typescript.el - TypeScript-support for Emacs