On Tue 28 Jun 2022 at 10:07, Quiliro Ordóñez <quil...@riseup.net> wrote: > But, upon several attempts to learn EEV, I have > given up every time.
For me, the ideas in eev are interesting. eev changes my emacs settings too much so I use eev-beginner only (subset of eev). There are a few things I learned to use quickly: - duplicate line with M-h M-2 - eepitch for executable notes F8 I like that Eduardo calls a sexp a button and pressing M-e executes that sexp. Before eev, I used to do something similar, having sexp in comments and pressing C-e (go to end of line) and then C-x C-e (evaluate last sexp), but Eduardo named it properly, gave it a key (M-e) and built whole way of thinking around that. eepitch blocks are much more useable than for example org-mode code blocks, where it is difficult to figure out, how to specify/configure the code block. With eepitch, it is simply all commands, and if you for example tunnel ssh or run stuff in various languages non-homogenously, it is just lines of texts run on a key press F8. Most of the time I do not use debian and globally installed packages so the predefined eepitch commands are not useable for me, but it is trivial to redefine them or define my own eepitch commands. I also use vertically split emacs window since ages ago so eev has been a natural fit for my screen habits. However, I find that most of the stuff in eev is rather Eduardo-specific so it is probably better strategy to cherry pick the good, reuseable parts that fit your way. For example, a lot of things are redundant: (find-man "find") vs (man "find") or too long and not so readable (many of those find- functions for example). It is easier to define my own functions, e.g. (rg-notes "foo") which searches foo in my notes, etc. There are also already existing ways of hyperlinking so for many things I prefer ffap style M-f jumping or M-. and M-, code jumping on the actual text rather than eev style button.