4 ms·
> I encourage others to learn lisp. It’s really not a hard language, and the parentheses don’t get in the way after a brief period of acclimation. Every time I
by ofrzeta 8y ago
> I encourage others to learn lisp. It’s really not a hard language, and the parentheses don’t get in the way after a brief period of acclimation.
Every time I try this, like twice a year, I get annoyed while setting up a development environment that supports the particular Lisp (usually Clojure), its syntax and the REPL. Last time I tried it was Spacemacs that didn't work as announced, on both Linux and macOS.
I am a Vi user and I would prefer to use that instead of learning a new environment such as Emacs. I want to set this up and have it work as frictionless as possible because learning a new programming language and its ecosystem is already enough work. However the Vim plugins (e.g. fireplace) also didn't "just work".
- kazinator 8y agoTXR Lisp comes with an accurate syntax definition file for Vim (and only Vim). Well, not exactly "comes with": txr.vim is in the root directory of the source tree. Some distros seem to package that, like Arch. The whole project was developed using Vim. Vim supports normal Common Lisp out-of-the-box. Just save your file under a .cl or .lisp suffix. In 18 years of working with Lisp in Vim, I never had a problem. Never installed a plugin or did anything special (other than developing that syntax file for TXR Lisp). At most I played with the content of :lispwords; that's about it.
- uadjet 8y agoWhile I truly appreciate emacs and vim, I had the same problem. Ultimately I went with IntelliJ IDEA and a plug-in for Clojure called Cursive. It's served me well; getting past the environment challenges and into the language itself was a godsend.