News for hackers. Stuff that matters.
Re:How to write Common Lisp in 2017 – an initiation manual by macco on Tuesday March 28, 2017 @03:35PM (#13979900)
If somebody is not comfortable to use emacs (I am), there is a atom plugin for use with CL: https://atom.io/packages/atom-slime

It doesn't replace emacs, but it works as a first Lisp ide.

Re:How to write Common Lisp in 2017 – an initiation manual by pnathan on Tuesday March 28, 2017 @04:16PM (#13980250)
Really! Do you use it? Would you feel comfortable submitting a PR explaining how to set it up? I HATE recommending emacs as the IDE for Common Lisp if it's not something people are comfortable with already.
Re:How to write Common Lisp in 2017 – an initiation manual by baggers on Wednesday March 29, 2017 @07:10AM (#13984980)
It's very promising but still very young. I manage to break it very quickly each time I have tried using it.

Eventually though this will be a huge boon.

Re:How to write Common Lisp in 2017 – an initiation manual by snowcrshd on Tuesday March 28, 2017 @04:45PM (#13980507)
Hmm, this just gave me an idea: Visual Studio Code Common Lisp plugin might also be a good way to expose the language to people unfamiliar to the language.
Re:How to write Common Lisp in 2017 – an initiation manual by int_19h on Tuesday March 28, 2017 @10:57PM (#13982969)
Every time I tried to get into CL, having to use Emacs/SLIME (which, let's face it, is the development environment for it for all practical purposes) has been a huge turn-off.

So, yes. Please?

Re:How to write Common Lisp in 2017 – an initiation manual by provemewrong on Wednesday March 29, 2017 @05:18AM (#13984534)
I had (and still have) a similar aversion to emacs, so I used to use Sublime with SublimeREPL plugin, which allowed me to run Common Lisp and Clojure (or any other language with a REPL) inside the editor. Pretty much a makeshift IDE, with an interface you're already used to. I've since moved on to VSCode, and I bet there must already be a way to replicate this in it, I just haven't had the need to work with Lisp since to explore this.
Re:How to write Common Lisp in 2017 – an initiation manual by baggers on Wednesday March 29, 2017 @07:09AM (#13984977)
It would be a very good idea. Be sure to make it talk to swank (the server side of the current editor tooling) so you can benefit from all the work that has been done there