While I did have all the time Emacs Manual, and probably Emacs Lisp manual in front of me, I have not read it for many years, definitely over a decade. There was no need for me and I did not program in Emacs Lisp at the time.
If I remember well I have first read this book: http://www.gigamonkeys.com/book/
And that helped me understand how Common Lisp works. From there I have discovered Guile as Scheme programming language, dialect of LISP “LISP”). But there were few problems before some years on using PostgreSQL database, so for that simple reason I gave up. It was not well integrated. GNU CLISP is Common Lisp implementation that had a built-in PostgreSQL bindings, that was great and majority of programs I have developed with it.
Side note: I was used and I may still be inclined to use the Common Lisp REPL on console without using Emacs and without evaluating through Emacs. Even writing functions on REPL works and such can be automatically saved and later formed into a program.
As people constantly referred me to use SLIME for Common Lisp I have tried out SLIME, and there is SLY today for Common Lisp. Without Common Lisp I would be still using Emacs and not really discover Emacs Lisp. My overall impression was that Emacs Lisp was some kind of shortened LISP used only for configurations. Why would I need that?
And that is where I have read the Emacs Lisp Introduction first and got aware that it exists and where I started using scratch buffer for Emacs Lisp instead for snippets.
It was all in front of me and as I did not find it important in those times I have not put attention on it.
As of date of writing this text I am transitioning all Common Lisp programs to Emacs Lisp as I find it better integrated.
That is how I came to read Emacs Lisp manual and from there on started programming in the favorite editor.
lisp emacs common-lisp manual read book
Copyright © 2020-11-27 06:46:44.458095+01 by Jean Louis.
Verbatim copying and distribution of this entire article are permitted worldwide, without royalty, in any medium, provided the copyright notice, the document’s official hyperlink and this permission notice are preserved. It is not required to retain page headings and footers or other formatting features. Retention of weblinks in both hyperlinked and non-hyperlinked media (as notes or some other form of printed URL in non-HTML media) is required.