lambdart/el-init

Just another Emacs '(lisp-machine) configuration written in literate programming format

VLM

Just another Emacs configuration written in org that has a simple goal: be just a configuration file, i.e, set custom values and hooks for the libraries/modes of interest.

Some people have started to refer to Emacs as a LISP MACHINE. It is not strictly a lisp machine because, clearly, it is a software program and not a physical computer, but as that line starts to blur it seems like a useful epithet for Emacs, because these days it looks more and more like a VIRTUAL LISP MACHINE.

A little tip for newcomers, Lisp Machines users are Lisp Developers, a hard truth that can be overwhelming for some and formidable by others.

Present Day, heh… Present Time

Goal

Use EMACS as a LISP MACHINE: a unify interface to perform DATA transformations, a bridge between the human mind and logical electric gates.

Mantras

1. Data driven/oriented design: is all about the data and how its organized to do less transformations as possible when solving a given problem, resulting in a great degree of optimization, clearness and simplicity.
2. Avoid late time decisions.
3. Always go in the opposite direction: SCALE DOWN, i.e, use less resource as possible (reduce, reuse, recycle)!
4. Simple is better.
5. Less is more.
6. For the LISP MACHINE everything is a just data to be s-expressed and/or evaluated.
7. Lazy load (autoloads) everywhere.
8. Byte-compile warnings not allowed!
9. Use as few libraries as possible and always try to use libraries already installed on Emacs to meet our needs. If you can withdraw a library, do so! Most of the time it takes little or no effort, and the gain is considerable. So, be alert to identify these situations!
10. Prioritize Emacs’s native libraries (builtin) over third-party ones. If any demand comes to light, try to solve it with these libraries first, then third-party ones already installed and finally (A HUGE MAYBE) the internet! Sometimes a little extension on these blotted-code-base is everything that’s needed to bring a new feature to life or solve an issue.
11. If something is bothering you, fix it, right now!
12. Few mapped keybinds as possible! Implies the constant usage of the minibuffer (or any other dynamic front-end menu) to eval less often used commands, but a huge pain relief, dwim style!
13. Use the same action flow logic, for the same class of commands.
14. Global behavior always available, do not change states (erase this silly idea), we have just one state and its VERY DYNAMIC!
15. Successive refinements: in constant refactoring! Always improve, never fear the winds of change!
16. I must not fear. Fear is the mind killer…

References

1. https://www.gnu.org/software/emacs/manual
2. https://www.gnu.org/software/emacs/manual/html_node/elisp/index.html
3. https://www.gnu.org/software/emacs/manual/html_node/emacs/Keymaps.html
4. https://en.wikipedia.org/wiki/Lisp_machine
5. https://www.emacswiki.org/emacs/LispMachine

LICENSE

MIT

EOF

And you don't seem to understand
A shame you seemed an honest man
And all the fears you hold so dear
Will turn to whisper in your ear

Duvet, Boa