fructure VS evil

Even the racket teachpack libraries designed for education are very capable; I was able to make this structured editor with only using teachpack content without external deps: https://github.com/disconcision/fructure

Right, it's fine, and is a pretty basic macro. Doubly linked lists are pretty basic data structures too, even the Rust versions once you figure it out. I like your sibling comment making it look like the CL version. I still want to know in more detail though why you think that doing things this way instead of the CL way is less likely to be "fragile and break down" for the complicated stuff, it would help to have a specific complicated example to showcase. Perhaps the linked https://github.com/disconcision/fructure in another comment would be a good study? The author there claimed they might not have been able to manage with defmacro, maybe someone familiar with both could articulate the challenges in detail. Is it just an issue of some things benefit a lot from pattern matching, and if so, does using CL's Trivia system mitigate that at all (in the same way that using gensym+packages+Lisp-2ness can mitigate hygiene issues)?

see also: fructure

evil mode

Since we already have vyper-mode, why not add Evil to the stack?

2 stripe blue belt here! I used to use Vim for everything other than Java development and have now adopted Emacs in the same way. I am using it for Clojure and Common Lisp development along with org mode, irc, rss, git and file management

I started with Evil mode and then moved to Xah fly keys before sticking to the emacs bindings. Having the caps lock key bound to CTRL helped me a lot. I don't know if it makes that much of a difference for Emacs but using the DVORAK layout has helped my fingers

There are other bindings you can try like Meow or God mode but I don't know what the adoption rate is like for them. Emacs gives you the flexibility to set it up as you please. As others have mentioned, there may be other keyboard options that might be more helpful as well

https://github.com/emacs-evil/evil

If you already know Vim, you should probably not use Emacs without Evil:

https://github.com/emacs-evil/evil

It gives you comprehensive Vim bindings so what you need to learn to be comfortable in Emacs is very little. As a bonus, it also keeps your RSI risk unchanged.

Emacs is a text ecosystem. And it's trivial to add these shortcuts. Evil[0] basically rewires everything to be Vim.

[0]: https://github.com/emacs-evil/evil

I would *highly* recommend using vim keybindings if you're just getting into it (Doom or just evil). I switched from vim to emacs and tried to rough it with the default keybindings thinking that otherwise I wasn't /really/ using emacs, but I was wrong! I've been using org-mode/emacs for ~2 years now and I've slowly been migrating everything into it as I find useful tools/modes/etc (and now thanks to u/ilemming I have ~12 more to experiment with 😂)

Despite using Emacs as my main editor, I was extremely familiar with Vim since I also used it frequently, and was able to use it quite well, especially because I also used [evil](https://github.com/emacs-evil/evil) in Emacs since Emacs's native keybindings are uncomfortable to use. I never used Vim as my primary editor though because it was cumbersome to configure. As many people say, Vimscript just feels wrong, so I gave up on trying to customize Vim.

uhm... this maybe? https://github.com/emacs-evil/evil

doom is a set of configuration files (to put it lightly 😅) for emacs, a text editor with really really powerful configuration abilities -- your "config files" are actually code in a full-fledged programming language, so people have done things like built package managers in it, or written full emulators for other text editors

Does it look like this? https://github.com/emacs-evil/evil/issues/1778