I'm using #Emacs since 2008, I've been maintaining an Emacs bundle since 2010 (currently working on v4.1). Emacs is genuinely one of the programs that still gives me the goosebumps. After all these years, I still learn new stuff about it that blows my mind.
@lxsameer that's cool! I recently started using #emacs because I found file navigation annoying in other IDEs. I know how to touch type, so now I literally just have to type in what I want (with all the autocompletion benefits just like a shell). Still learning the basics but finding even that awesome!
By the way, I've been programming a bit of #Clojure too, although right now I prefer the #clisp vibes :clojure: :lisp:
1 - Learn the emacs dialect of lisp called #elisp, to get you started there are docs & a simple tutorial via C-h-i [just scroll down & look for Elisp & Elisp intro]
2 - Learn a dialect of Common Lisp [#CL] such as #clisp, #sbcl or there is the famous MIT #SICP course based on #Scheme
@dekkzz76 Thanks for this. How easy is it to learn #elisp and then migrate to #clisp? Is the difference like Py2.7 vs 3 or something like Py 3.7 and 3.11?
@dekkzz76 Thanks for clarification. I read that elisp reads the entire file into it's buffer instead of line by line. Not sure if that's the case with #clisp but for my use cases, that's not a problem.
TIL: every run of #SBCL has the same initial *random-state*, so sequences of pseudo-random numbers are not so random. The solution is super simple: (setf *random-state* (make-random-state t)).
It makes sense considering what a #Lisp image is... but it's still pretty surprising compared to other programming languages. (And doesn't happen in #ECL or #clisp 😅)