Hacker News Reader

Comment by ode | Hacker News Reader

1. To understand Clojure stacktraces you should read https://8thlight.com/blog/connor-mendenhall/2014/09/12/cloju.... Although I agree the lengthy huge Java dump when crashing is pretty awful, you can ignore most of it.

3. I would recommend you look into Parinfer - https://shaunlebron.github.io/parinfer/. You can manage scopes with levels of indentation, rather than having to move parens around. It works with most major editors, including Emacs.

View on HN

I couldn't get Parinfer to work with Vim. There's a port but it's buggy.

But the Neovim port is great. Installation requires a little patience, but it works well.

In any case, one should read the Clojure style guide on GitHub [0] and get used to writing code in normal editing modes first. Then move on to Parinfer or Paredit once you feel the shape of the code and sense why it's like that.

[0]https://github.com/bbatsov/clojure-style-guide

Hi - I'm the author of the Parinfer Vimscript port.

If you've found a bug with the port, please report it here: https://github.com/oakmac/parinfer-viml/issues/new

Thanks :)

Is it impossible to implement restarts (a la CL) in Clojure? They are way better than when the interpreter tells me that my program is dead and here's what happened. It's sad that interactive debugging within the repl is not embraced by everybody.

There are some libraries for this. A great overview of the problem and some of the libs is https://www.youtube.com/watch?v=zp0OEDcAro0 and a good set of corresponding notes at https://gist.github.com/msgodf/6f4e43c112b8e89eee3d

Reply on news.ycombinator.com