Re: [ANN] Clojure/ClojureScript debugging library debux 0.4.0 is out.

Debux library is now upgraded to version 0.4.1. 2017년 12월 7일 목요일 오후 7시 34분 29초 UTC+9, Philos Kim 님의 말: > > * https://github.com/philoskim/debux > > * https://clojars.org/philoskim/debux > -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to thi

[ANN] Clojure/ClojureScript debugging library debux 0.4.0 is out.

* https://github.com/philoskim/debux * https://clojars.org/philoskim/debux -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patien

Re: Releasing scope-capture, a library for easing REPL-based debugging

regarding ClojureScript support. Please tell me if you still have issues. > > Cheers, > > Val > > On Saturday, 14 October 2017 20:31:35 UTC+2, Mike Rodriguez wrote: >> >> I really like this library already. I only had to give it about 5 minutes >> of time to i

Re: Releasing scope-capture, a library for easing REPL-based debugging

ell me if you still have issues. Cheers, Val On Saturday, 14 October 2017 20:31:35 UTC+2, Mike Rodriguez wrote: > > I really like this library already. I only had to give it about 5 minutes > of time to immediately see how it simplified quick REPL-driven debugging > workflows fo

Re: Releasing scope-capture, a library for easing REPL-based debugging

I really like this library already. I only had to give it about 5 minutes of time to immediately see how it simplified quick REPL-driven debugging workflows for me. The only outstanding issue that is an annoyance for me is the CLJS support, which is discussed at https://github.com

Re: Releasing scope-capture, a library for easing REPL-based debugging

Le 9 oct. 2017 18:17, "Didier" a écrit : What happens with loops? Say if you spy inside a for? It records and logs new information on each iteration :) see `disable!` and/or `brk` if that's inconvenient. -- You received this message because you are subscribed to the Google Groups "Clojure" gro

Re: Releasing scope-capture, a library for easing REPL-based debugging

What happens with loops? Say if you spy inside a for? -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first pos

Re: Releasing scope-capture, a library for easing REPL-based debugging

thub.com/alvalval/scope-capture>. >>>> >>>> https://github.com/alvalval/scope-capture >>>> >>>> Loosely speaking, scope-capture makes it trivial to reproduce from the >>>> REPL the context of a piece of code after it executed.

Re: Releasing scope-capture, a library for easing REPL-based debugging

ary called >>> scope-capture <https://github.com/alvalval/scope-capture>. >>> >>> https://github.com/alvalval/scope-capture >>> >>> Loosely speaking, scope-capture makes it trivial to reproduce from the >>> REPL the context of a pi

Re: Releasing scope-capture, a library for easing REPL-based debugging

fter it executed. >> >> It was inspired by Stuart Halloway's article *REPL Debugging: no >> stacktrace required >> <http://blog.cognitect.com/blog/2017/6/5/repl-debugging-no-stacktrace-required>*. >> Thanks Stu! >> >> I've been using it professi

Re: Releasing scope-capture, a library for easing REPL-based debugging

/scope-capture > > Loosely speaking, scope-capture makes it trivial to reproduce from the > REPL the context of a piece of code after it executed. > > It was inspired by Stuart Halloway's article *REPL Debugging: no > stacktrace required > <http://blog.cognitect.

Re: Releasing scope-capture, a library for easing REPL-based debugging

makes it trivial to reproduce from the REPL > the context of a piece of code after it executed. > > It was inspired by Stuart Halloway's article REPL Debugging: no stacktrace > required. Thanks Stu! > > I've been using it professionally for a few weeks now, and it's been

Releasing scope-capture, a library for easing REPL-based debugging

de after it executed. It was inspired by Stuart Halloway's article *REPL Debugging: no stacktrace required <http://blog.cognitect.com/blog/2017/6/5/repl-debugging-no-stacktrace-required>*. Thanks Stu! I've been using it professionally for a few weeks now, and it's been a signi

[ANN] debux(Clojure/ClojureScript debugging library) 0.3.1 is out.

I'm pleased to announce debux version 0.3.1. # Debux is a library for debugging Clojure and ClojureScript. # The new added feature is to show you every evaluated results of a form. https://github.com/philoskim/debux https://clojars.org/philoskim/debux -- You received this me

[ANN] debux(Clojure/ClojureScript debugging library) 0.3.1 is out.

I'm pleased to announce debux version 0.3.0. # Debux is a library for debugging Clojure and ClojureScript. # The new added feature is to show you every evaluated results of a form. https://github.com/philoskim/debux https://clojars.org/philoskim/debux -- You received this me

[ANN] debux(Clojure/ClojureScript debugging library) 0.3.0 is out.

I'm pleased to announce debux version 0.3.0. # Debux is a library for debugging Clojure and ClojureScript. # The new added feature is to show you every evaluated results of a form. https://github.com/philoskim/debux https://clojars.org/philoskim/debux -- You received this message becaus

New to Clojure - productivity and debugging with Emacs

Not much to add here, but if you're digging into Emacs and the modes you've listed, I've started to document my emacs config here: https://github.com/chadhs/dotfiles/blob/master/editors/emacs-config.org If you're curious about common feature uses; head to the keybindings section and look at the

Re: New to Clojure - productivity and debugging with Emacs

gt; >> ahawk, >> >> I've been using clojure for years, but can still relate to the issues you >> are facing, which is why I wrote a debugging/development tool to help. It's >> called sayid. It can be used directly from the repl, but has an emacs/cider >>

Re: New to Clojure - productivity and debugging with Emacs

ay is that I find it difficult to know exactly what to expect from >> > these >> > libraries and many other, unless, of course, I read and understand their >> > source. That is a challenge in its own right for a less advanced >> > programmer >> > such as

Re: New to Clojure - productivity and debugging with Emacs

Bill Piel: > > ahawk, > > I've been using clojure for years, but can still relate to the issues you > are facing, which is why I wrote a debugging/development tool to help. It's > called sayid. It can be used directly from the repl, but has an emacs/cider > int

Re: New to Clojure - productivity and debugging with Emacs

On Jan 8, 2017 1:52 AM, "ahawk" wrote: .. I find it difficult to know exactly what to expect from these libraries and many other, unless, of course, I read and understand their source. That is a challenge in its own right for a less advanced programmer such as myself. The good news is that i

Re: New to Clojure - productivity and debugging with Emacs

x27;t seem very productive to me compared to the debugging features I've been used to from doing OOP years ago. Den søndag den 8. januar 2017 kl. 17.06.34 UTC+1 skrev Matching Socks: > > That is an ambitious project. Divide and conquer. One super duper > benefit of Clojure is that if

Re: New to Clojure - productivity and debugging with Emacs

es for productivity (see below), and > while > > they are very helpful, the code is still not as transparent to me as a > > strongly typed language, where the IDE shows you exactly what type of > data a > > function returns. Part of the problem is probably that I am only using a &

Re: New to Clojure - productivity and debugging with Emacs

Hi ahawk, If you have the time, by all means reach for all the references and books mentioned in this thread, and there is a wealth of free resources out there. However doing both that and learning a powerful tool such as Emacs/CIDER at the same time can be frustrating. If time is of the essenc

Re: New to Clojure - productivity and debugging with Emacs

ahawk, I've been using clojure for years, but can still relate to the issues you are facing, which is why I wrote a debugging/development tool to help. It's called sayid. It can be used directly from the repl, but has an emacs/cider integration that makes it much more powerf

Re: New to Clojure - productivity and debugging with Emacs

st, delegate to the next handler, log its response, and return its response; then stick that handler wherever in the handler stack makes you curious. Using the Emacs CIDER REPL you may change the handler stack and fiddle with logging while the program runs, so logging is a convenient debu

Re: New to Clojure - productivity and debugging with Emacs

gt; web-mode > clj-refactor > > Questions: > Based on the above, could you perhaps suggest any functionality in these or > other packages, which could make the interaction (in lack of a better word) > with other libraries more transparent to me? > > Also, can you tell me if i

New to Clojure - productivity and debugging with Emacs

ojure web app with Ciders debugging feature, or something similar (with break points etc.)? So far I have only been able to use Ciders debugging feature on code running in my local REPL. Therefore, since I am developing a web app, I need to call my functions with mock requests. Best regards

Re: Including debugging information for Clojure code

Thanks for the information. I'll check those out. For others trying to solve the same problem I also found what looks like the relevant code within Counter Clockwise https://github.com/laurentpetit/ccw/blob/fb3a5467087cbe76d6b4fafe36ba7b97f5564228/ccw.core/src/java/ccw/debug/ClojureLineBreakpointAd

Re: Including debugging information for Clojure code

Hi Jason, Things you might be interested in checking out: George Jahad's CDT: https://github.com/georgejahad/cdt. It's kind of old, but the JDI hasn't changed much recently. There's also Ritz: https://github.com/pallet/ritz. Again, I think it's a little bit-rotted these days but there's probably

Re: Including debugging information for Clojure code

FYI, I believe the Clojure compiler always emits classes with Java debug information (line numbers, source files, and local variables). On Monday, March 14, 2016 at 6:43:26 PM UTC-5, James Norton wrote: > > > Thanks for the reply. I was able to get it working when I looked at other > classes. T

Re: Including debugging information for Clojure code

That's awesome that you got it working. If you could share any information you found that would be really helpful for others in the future. On Monday, March 14, 2016 at 7:43:26 PM UTC-4, James Norton wrote: > > > Thanks for the reply. I was able to get it working when I looked at other > classes

Re: Including debugging information for Clojure code

Thanks for the reply. I was able to get it working when I looked at other classes. The first class I tried on the list resulted in the exception, but other classes (including those from my test project) worked. And thanks for the note about CIDER. I had looked at those sources briefly, but now

Re: Including debugging information for Clojure code

I don't have much time right now, but AFAIK Cursive is the only debugger using JDI - CIDER has a source manipulation debugger. I don't generally have to do anything special to debug, although I use an IntelliJ layer on top of JDI. I can try to check if it's doing anything with that flag. You can al

Including debugging information for Clojure code

I'd recommend asking on slack. There's a cider channel where they hang out and may be able to answer your question. You can join here https://clojurians.slack.com/ I'd really like to know this information for Proto REPL as well. -- You received this message because you are subscribed to the G

Including debugging information for Clojure code

I have been experimenting with using the Java Debug Interface (JDI) with Clojure, but I am confused about how to get Clojure to include debugging information when compiling to Java byte code. I have created NREPL middleware that is able to attach to the VM using com.sun.jdi.Bootstrap and

Re: Debugging idea for a constrained situation

Hi, We had the same in my team, and we deployed a very similar idea to work around it ! We also have a C++ application that needs to access a lot of (sometimes very heavy) cache files/dbs that vary a lot between environment. The tool we are using now allows us to either record any externally rea

Re: Debugging idea for a constrained situation

If you're in a place where you're hunting for major architectural patterns to consider in what could amount to a rewrite, well, certainly there is no free lunch. But the pattern you mention- capturing external event history- is in the vein of Event Source systems http://martinfowler.com/eaaDev/Eve

Debugging idea for a constrained situation

While not strictly Clojure-related, I thought I'd share this idea with you here because (1) I came up with it while thinking about design from a Clojure / functional point of view and (2) I respect your opinion. It's very likely you'll have better ideas... *I'm in an highly constrained situatio

Power of Clojure/Lisp s-expressions as a debugging aid

As a relative Clojure novice I'm finding Lisp's s-expressions provide a simplified debugging experience, Java stacktraces aside, unparallelled in any other language I've come across. I was recently having trouble with this function: (defn shared-aspects [my-id your-id] (for [

Re: Debugging with Cider

Okay thanks that should be enough. On Wednesday, May 6, 2015 at 12:07:29 PM UTC+2, Artur Malabarba wrote: > > Stepping into a function that wasn't previously isntrumented is not > supported yet. > However, you can just instrument both functions (C-u C-M-x on each one), > and when one function c

Re: Debugging with Cider

Stepping into a function that wasn't previously isntrumented is not supported yet. However, you can just instrument both functions (C-u C-M-x on each one), and when one function calls the other you'll seamlessly step through both. Cheers, Artur -- You received this message because you are subs

Debugging with Cider

Hi everyone, I just discovered after reading the post [1], CIDER has debugging facility for Clojure. It seems to be nice but what I could not find was the step in functionality. Is there such a functionality that you are aware of? Thanks in advance! Regards, Timur [1] http

Re: Debugging in CIDER

Great, thanks Artur, very interesting. Very nice work! On 2 April 2015 at 21:02, Artur Malabarba wrote: > > From a look at how it works, is it fair to say that this is mostly > designed for debugging a function at a time > > You can instrument as many functions as you want with

Re: Debugging in CIDER

Kudos to Bozhidar and all CIDER contributors! I am hyped for CIDER 0.9 On Sunday, 29 March 2015 00:46:33 UTC+7, Bozhidar Batsov wrote: > > Hey everyone, > > Just wanted to let you know that the most requested feature for CIDER (a > debugger, in case you're wondering) has just landed in the mast

Re: Debugging in CIDER

> From a look at how it works, is it fair to say that this is mostly designed > for debugging a function at a time You can instrument as many functions as you want with C-u C-M-x, and debugger will seamlessly jump between them as they're getting executed. -- You received this mess

Re: Debugging in CIDER

Nice work !!! On Sunday, March 29, 2015 at 1:46:33 AM UTC+8, Bozhidar Batsov wrote: > > Hey everyone, > > Just wanted to let you know that the most requested feature for CIDER (a > debugger, in case you're wondering) has just landed in the master branch ( > https://github.com/clojure-emacs/cider/

Re: Debugging in CIDER

This looks nice! In particular the fact that it's expression based makes me jealous. >From a look at how it works, is it fair to say that this is mostly designed for debugging a function at a time, i.e. you can't easily step from one function to another? Or does it instrument multi

Re: Debugging in CIDER

Awesome. +1 for a new release too, lots of other good stuff in there too. - Matt On Saturday, March 28, 2015 at 1:46:33 PM UTC-4, Bozhidar Batsov wrote: > > Hey everyone, > > Just wanted to let you know that the most requested feature for CIDER (a > debugger, in case you're wondering) has just

Re: State of the Art in Clojure Debugging

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

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

t now, so > the question is whether you dislike Intellij IDEA as much as Emacs. :-) > > > > On 30 March 2015 at 15:20, Matthew West > wrote: > >> What is the current preferred strategy for debugging Clojure code? I'd >> prefer a solution that doesn't involv

Re: State of the Art in Clojure Debugging

DEA as much as Emacs. :-) On 30 March 2015 at 15:20, Matthew West wrote: > 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

State of the Art in Clojure Debugging

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

Debugging in CIDER

Hey everyone, Just wanted to let you know that the most requested feature for CIDER (a debugger, in case you're wondering) has just landed in the master branch ( https://github.com/clojure-emacs/cider/pull/1019#issuecomment-87240470). The new CIDER debugger is inspired by edebug (Emacs's own debu

Re: debugging "MyClass cannot be cast to MyClass" exceptions

ype), but there are still >>>>>>> some >>>>>>> existing instances lying around, that belong to the previous definition >>>>>>> of >>>>>>> that same type. >>>>>>> >>>>>>> See t

Re: debugging "MyClass cannot be cast to MyClass" exceptions

definition >>>>>> of >>>>>> that same type. >>>>>> >>>>>> See this thread for more information: https://groups.go >>>>>> ogle.com/forum/#!msg/clojure/N2ivUM8bvB8/xgiFVtsXKnkJ >>>>>> >>>

Re: debugging "MyClass cannot be cast to MyClass" exceptions

gt;> See this thread for more information: https://groups. >>>>> google.com/forum/#!msg/clojure/N2ivUM8bvB8/xgiFVtsXKnkJ >>>>> >>>>> Cheers, >>>>> >>>>> Juan >>>>> >>>>> On Saturday, December 6, 201

Re: debugging "MyClass cannot be cast to MyClass" exceptions

xgiFVtsXKnkJ >>>> >>>> Cheers, >>>> >>>> Juan >>>> >>>> On Saturday, December 6, 2014 5:55:23 PM UTC-3, Brian Craft wrote: >>>>> >>>>> I'm experimenting with jwrapper, and am getting runtime e

Re: debugging "MyClass cannot be cast to MyClass" exceptions

>>> google.com/forum/#!msg/clojure/N2ivUM8bvB8/xgiFVtsXKnkJ >>> >>> Cheers, >>> >>> Juan >>> >>> On Saturday, December 6, 2014 5:55:23 PM UTC-3, Brian Craft wrote: >>>> >>>> I'm experimenting with jwrapper, and am gett

Re: debugging "MyClass cannot be cast to MyClass" exceptions

;> >> Cheers, >> >> Juan >> >> On Saturday, December 6, 2014 5:55:23 PM UTC-3, Brian Craft wrote: >>> >>> I'm experimenting with jwrapper, and am getting runtime exceptions like >>> this, due to some jar manipulation that it's doing. I know

Re: debugging "MyClass cannot be cast to MyClass" exceptions

, due to some jar manipulation that it's doing. I know one of the steps >> is pack200, however running pack200 manually doesn't create these issues. >> >> Anyone have suggestions for debugging this? I've seen this type of error >> countless times in clojure, but o

Re: debugging "MyClass cannot be cast to MyClass" exceptions

of the steps > is pack200, however running pack200 manually doesn't create these issues. > > Anyone have suggestions for debugging this? I've seen this type of error > countless times in clojure, but only when reloading interactively. This is > the first time I've se

debugging "MyClass cannot be cast to MyClass" exceptions

I'm experimenting with jwrapper, and am getting runtime exceptions like this, due to some jar manipulation that it's doing. I know one of the steps is pack200, however running pack200 manually doesn't create these issues. Anyone have suggestions for debugging this? I've see

Re: [ANN] print.foo 1.0.0 - library of print debugging macros

Looks really nice, thanks for sharing! On Thursday, 20 November 2014, Alex Baranosky wrote: > Hi guys, > > I've further refined my print.foo project, and thought I'd share the > latest version here with you all. I get a ton of mileage out of the library > personally and professionally using it e

[ANN] print.foo 1.0.0 - library of print debugging macros

Hi guys, I've further refined my print.foo project, and thought I'd share the latest version here with you all. I get a ton of mileage out of the library personally and professionally using it everyday to enhance my repl-driven development. Here some highlights from the README (you can read a com

Re: [ANN] Prone: Exception/debugging middleware

Fantastic! 2014-09-02 5:35 GMT+01:00 Kurt Schrader : > Outstanding work! > > Just plugged it locally and used it to debug a particularly hairy issue on > my side. This is super useful. > > -Kurt > > > On Mon, Sep 1, 2014 at 10:48 PM, James Reeves > wrote: > >> This looks rather nice. I'll certa

Re: [ANN] Prone: Exception/debugging middleware

Outstanding work!  Just plugged it locally and used it to debug a particularly hairy issue on my side. This is super useful. -Kurt On Mon, Sep 1, 2014 at 10:48 PM, James Reeves wrote: > This looks rather nice. I'll certainly be trying it out. > - James > On 2 September 2014 01:06, Colin

Re: [ANN] Prone: Exception/debugging middleware

This looks rather nice. I'll certainly be trying it out. - James On 2 September 2014 01:06, Colin Fleming wrote: > I don't do any web dev myself, but Prone looks really nice - > congratulations! Great work. > > Cheers, > Colin > > > On 2 September 2014 02:05, Christian Johansen > wrote: > >>

Re: [ANN] Prone: Exception/debugging middleware

I don't do any web dev myself, but Prone looks really nice - congratulations! Great work. Cheers, Colin On 2 September 2014 02:05, Christian Johansen wrote: > Hi, > > Prone (http://clojars.org/prone - http://github.com/magnars/prone) is a > new middleware for Ring apps that replaces the defaul

[ANN] Prone: Exception/debugging middleware

Hi, Prone (http://clojars.org/prone - http://github.com/magnars/prone) is a new middleware for Ring apps that replaces the default exception page with an interactive page that presents the exception, stack trace and environment data in a more easily understandable way. It can also debug arbitra

Re: clojurescript, sourcemaps, and debugging info

On Sun, May 18, 2014 at 7:25 AM, Timothy Baldridge wrote: >>> foo.cljs >>> foo/whatever.cljs >>> bar.cljs >>> bar/stuff.cljs > > yes, do this, it also matches what most of the Clojure community does. > I'm convinced. Using this style now. > > On Sun, May 18, 2014 at 4:16 AM, Thomas Heller wro

Re: clojurescript, sourcemaps, and debugging info

>> foo.cljs >> foo/whatever.cljs >> bar.cljs >> bar/stuff.cljs yes, do this, it also matches what most of the Clojure community does. On Sun, May 18, 2014 at 4:16 AM, Thomas Heller wrote: > Don't think plugins can touch the devtools. > > I tend to organize my code that the public "interface" o

Re: clojurescript, sourcemaps, and debugging info

Don't think plugins can touch the devtools. I tend to organize my code that the public "interface" of foo reside in foo.cljs and the implementation details go into foo/something.cljs so in your case you'd get foo.cljs foo/whatever.cljs bar.cljs bar/stuff.cljs Maybe an alternative solution to y

Re: clojurescript, sourcemaps, and debugging info

flat namespace is ugly. Someone please please tell me there is a better solution. :-) Is there no 10-line chrome-plugin which solves this? On Fri, May 16, 2014 at 7:35 AM, t x wrote: > Bah, I've reverted to a flat namespace, i.e. foo_internal.cljs, > foo_public.cljs, bar_internal.cljs, bar_public

Re: clojurescript, sourcemaps, and debugging info

Bah, I've reverted to a flat namespace, i.e. foo_internal.cljs, foo_public.cljs, bar_internal.cljs, bar_public.cljs ... :-) On Fri, May 16, 2014 at 6:24 AM, Tim Visher wrote: > Seems worth a bug report/feature request to the Chrome Dev Tools team. > > On Thu, May 15, 2014 at 11:45 PM, t x wrote:

Re: clojurescript, sourcemaps, and debugging info

Seems worth a bug report/feature request to the Chrome Dev Tools team. On Thu, May 15, 2014 at 11:45 PM, t x wrote: > Hi, > > * background: > > * I have clojurescript + lein cljsbuild auto working perfectly fine. > > * I have source maps working (when I click on a file in Chrome, it > jumps m

Re: clojurescript, sourcemaps, and debugging info

Its Chrome, no way around it AFAICT. FWIW you can mouseover the filename in the console and the title popup will show the entire URL to the file. On Friday, May 16, 2014 5:45:28 AM UTC+2, t x wrote: > > Hi, > > * background: > > * I have clojurescript + lein cljsbuild auto working perfectly f

clojurescript, sourcemaps, and debugging info

Hi, * background: * I have clojurescript + lein cljsbuild auto working perfectly fine. * I have source maps working (when I click on a file in Chrome, it jumps me to the corresponding *.cljs file) * problem I am facing: * I like to name my modules: foo/public.cljs foo/other-stu

Re: clojure debugging repl

Did anyone ever get this working ? On Saturday, January 25, 2014 10:42:27 AM UTC-5, Magomimmo wrote: > > On Jan 25, 2014, at 2:12 AM, Alexandr Kurilin > > > wrote: > > > > > I'd love to be able to set breakpoints in a running clojure application, > step through the code and inspect locals and

Re: clojure debugging repl

On Jan 25, 2014, at 2:12 AM, Alexandr Kurilin wrote: > > I'd love to be able to set breakpoints in a running clojure application, step > through the code and inspect locals and the referencing environment. Anything > that gets me off of the time-consuming process of adding > timbre/clojure.to

Re: clojure debugging repl

it? >> >> >> >> On Fri, Jan 24, 2014 at 3:46 PM, Jarrod Swart wrote: >> >>> The second version of The Joy of Clojure talks about building a >>> debugging repl that allows insertion of breakpoints into code. Perhaps >>> something similar

Re: clojure debugging repl

pter alone. > > However, looking at http://www.manning.com/fogus2/ I can't seem to find > it. Which chapter is it? > > > > On Fri, Jan 24, 2014 at 3:46 PM, Jarrod Swart > > wrote: > >> The second version of The Joy of Clojure talks about building a debugging >

Re: clojure debugging repl

I am willing to buy the book for this chapter alone. However, looking at http://www.manning.com/fogus2/ I can't seem to find it. Which chapter is it? On Fri, Jan 24, 2014 at 3:46 PM, Jarrod Swart wrote: > The second version of The Joy of Clojure talks about building a debugging >

Re: clojure debugging repl

tended to a generic nrepl handler, but I > don't have the time to do so at the moment. > > > On Friday, January 24, 2014 6:46:23 PM UTC-5, Jarrod Swart wrote: >> >> The second version of The Joy of Clojure talks about building a debugging >> repl that allow

Re: clojure debugging repl

> > The second version of The Joy of Clojure talks about building a debugging > repl that allows insertion of breakpoints into code. Perhaps something > similar could be done here. > > On Friday, January 24, 2014 4:38:59 PM UTC-5, t x wrote: >> >> Found it, apparently

Re: clojure debugging repl

The second version of The Joy of Clojure talks about building a debugging repl that allows insertion of breakpoints into code. Perhaps something similar could be done here. On Friday, January 24, 2014 4:38:59 PM UTC-5, t x wrote: > > Found it, apparently it's > > debug-repl

Re: clojure debugging repl

Found it, apparently it's debug-repl => swank-clojure => CDT => ritz It appears cider does not yet support this, so ritz is probably the "most powerful" at the moment. On Fri, Jan 24, 2014 at 3:39 AM, t x wrote: > Hi, > > One thing I miss from pre-Clojure scheme days is as follows: > > ## W

clojure debugging repl

Hi, One thing I miss from pre-Clojure scheme days is as follows: ## What I want 1 => (foo) ;; I'm calling foo at the repl ... foo executes ... ... at some point, an exception is thrown ... 2 => my interpreter _starts a new repl_ * at the point where the exception was thrown * lets me exam

Re: Debugging with Cider

e=Issues On Thursday, October 31, 2013 12:17:52 PM UTC-7, Matthew O. Smith wrote: > > > Hi all, > > Has anyone gotten debugging in emacs working with cider (was nrepl). I > did fork and update cljdb but it is pretty old school. > https://github.com/m0smith/cljdb > Is ther

Re: Step by step debugging

I would imagine that cinc could side-step any jvm-imposed limitations on developing a reference debugger for clojure. -- -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts fr

Re: Step by step debugging

Colin, Got it--this setting is relevant to use of a debugger. I was trying to see something from vanilla and Leiningen repls. Thank you for taking so much time to explain. (My current debugger is (print (format ...)). Have to upgrade.) -Marshall On Wednesday, November 13, 2013 5:16:27 PM

Re: Step by step debugging

x27;s bound to > {:disable-locals-clearing true} inside the binding form (of course). > > I'm still not clear on what effect this should have. I can refer to a > local variable inside its scope, but that's nothing special. Is > :disable-locals-clearing = true supposed to

Re: Step by step debugging

de its scope, but that's nothing special. Is :disable-locals-clearing = true supposed to allow me to be able to reference a local outside of its scope? (A bad thing in general, but good, sometimes, for debugging?) For example, if I compile this: (defn yo [n] (if (= n 15) (th

Re: Step by step debugging

to look at), especially further up the stack frames, will be set to null even if your code doesn't do so. This can be very confusing and/or frustrating when debugging. *compiler-options* is a dynamic var that controls various compiler options, although I believe disabling locals clearing is

Re: Step by step debugging

Hi Ryan, Ryan Spangler writes: > I'll have an official announcement once it is ready to be released, > but until then I welcome any feedback. I don't have time to test experimental stuff right now but I'm very much looking forward to reading your announcement! Thanks to tacking this. Best, -

Re: Step by step debugging

Lee, Thank you for pointing that out! The README has been updated with more explicit instructions. For those who don't know, to open a dt_socket from your project.clj simply add this line: :jvm-opts ["-agentlib:jdwp=transport=dt_socket,server=y,suspend=n"] Schmetterling is still very ne

Re: Step by step debugging

;> default. You can also set this via command line with >>> -Dclojure.compile.disable-locals-clearing=true >>> >>> >>> On Thursday, November 7, 2013 11:32:29 AM UTC-6, Lee wrote: >>> >>>> >>>> I'd like to chime in here from a back

Re: Step by step debugging

On Tuesday, November 12, 2013 11:15:11 PM UTC-6, Mars0i wrote: > > ... I'm seriously wondering at this moment, though, whether I should stop > and do the rewrite in CL instead, despite several advantages of Clojure for > me. Being able to easily look at any data structure at any time in the CL

Re: Step by step debugging

o set this via command line with >> -Dclojure.compile.disable-locals-clearing=true >> >> >> On Thursday, November 7, 2013 11:32:29 AM UTC-6, Lee wrote: >> >>> >>> I'd like to chime in here from a background that involved a lot of >>> Com

  1   2   3   4   5   >