Re: State of the Art in Clojure Debugging

2015-03-30 Thread Paul deGrandis
Because of the blocking nature of vim-fireplace (really of vim itself), you'll have to run most of the debuggers from a live, dedicated repl. I've been slowly evolving my own debug-repl for a few years now. It works in a `user.clj` setting or in a project related file. At a quick glance, it s

Re: State of the Art in Clojure Debugging

2015-03-30 Thread Lee Spector
Thanks for this Bozhidar. I just took a look at clj-debugger and am excited about several of its features, especially the ability to print locals. Does anyone know if it supports (or could easily support -- I'd post an issue if it seems possible) a w

Re: State of the Art in Clojure Debugging

2015-03-30 Thread Vijay Kiran
I've been using Spacemacs with great success https://github.com/syl20bnr/spacemacs and I heard some rave things from Vim aficionados. So you can get all the good stuff from bbastov's hardwork and still use Vim like environment :) ./Vijay On Monday, March 30, 2015 at 4:27:32 PM UTC+2, Bozhida

Re: State of the Art in Clojure Debugging

2015-03-30 Thread Bozhidar Batsov
This is a newish REPL debugger that's editor agnostic - https://github.com/razum2um/clj-debugger (and accidentally it's powering CIDER's own debugger). I'm pretty sure Cursive has the most sophisticated debugger right now, so the question is whether you dislike Intellij IDEA as much as Emacs. :-)

State of the Art in Clojure Debugging

2015-03-30 Thread Matthew West
What is the current preferred strategy for debugging Clojure code? I'd prefer a solution that doesn't involve Emacs, as I already know vim pretty well and don't really want to switch. What are my options that are still actively maintained? -- You received this message because you are subscribe