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
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
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
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
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 C-u C-M-x, and
>
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
> 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 message because y
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/
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 multiple functions in
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
Oh! Yes, I think that's it. I didn't realize the uberjar would include
source, which clojure would attempt to re-compile. I'm not sure why that
would be useful in an uberjar.
I tried the lein :omit-source flag, which does indeed omit the source for
my project, but still includes the source for
Hello,
I think it does for deciding whether to use the class file found on disk,
or to recompile the namespace in memory from the .clj file.
Does the above make sense ?
Laurent
Le mercredi 10 décembre 2014, Brian Craft a écrit :
> This exception is related to the pack200 -m option, which alter
This exception is related to the pack200 -m option, which alters class file
timestamps.
Do clojure class loaders depend on class file timestamps?
On Monday, December 8, 2014 9:15:57 AM UTC-8, Brian Craft wrote:
>
> Assuming this is something to do with class loaders going wrong, how would
> I a
Assuming this is something to do with class loaders going wrong, how would
I approach finding the code paths involved? Could I identify where the
class is being loaded; set breakpoints at those places to get the stack
traces? Something else?
In my case it seems to be triggered by a type hint on
Not sure if I followed the non-interactive case. Is it just
1) deftype or defrecord in one file
2) import the class in a different file
3) AOT compile (e.g. uberjar)?
On Saturday, December 6, 2014 11:07:36 PM UTC-8, Ambrose Bonnaire-Sergeant
wrote:
>
> Perhaps this issue is biting you
> http://
Perhaps this issue is biting you http://dev.clojure.org/jira/browse/CLJ-979
Thanks,
Ambrose
On Sat, Dec 6, 2014 at 5:22 PM, Brian Craft wrote:
> Yes, I know. ;) In this case it's happening with an uberjar, not with the
> repl. I do "java -jar myapp.jar", and later, while it is processing data,
Yes, I know. ;) In this case it's happening with an uberjar, not with the
repl. I do "java -jar myapp.jar", and later, while it is processing data,
get this exception. No repl involved.
On Saturday, December 6, 2014 2:02:01 PM UTC-8, juan.facorro wrote:
>
> Hi Brian,
>
> This problem usually hap
Hi Brian,
This problem usually happens when working on the REPL and you redefine a
record or type (derecord and deftype), but there are still some existing
instances lying around, that belong to the previous definition of that same
type.
See this thread for more
information:
https://groups.g
I'd like to see Ritz with cider too. :)
Just for reference...
there is already an issue on the Ritz
repo: https://github.com/pallet/ritz/issues/112
and there are a number of Ritz related issues on the Cider repo:
https://github.com/clojure-emacs/cider/search?q=ritz&ref=cmdform&type=Issues
On T
Should I file a bug report at this point?
(Correcting the email title.)
On Fri, Aug 9, 2013 at 3:04 AM, Jozef Wagner wrote:
> This ticket may be related, http://dev.clojure.org/jira/browse/CLJ-1093
>
>
> On Friday, August 9, 2013 12:08:06 AM UTC+2, Jozef Wagner wrote:
>>
>> It may be a bug somew
This ticket may be related, http://dev.clojure.org/jira/browse/CLJ-1093
On Friday, August 9, 2013 12:08:06 AM UTC+2, Jozef Wagner wrote:
>
> It may be a bug somewhere in a Compiler. I've lost track at
> https://github.com/clojure/clojure/blob/master/src/jvm/clojure/lang/Compiler.java#L6624
>
> af
It may be a bug somewhere in a Compiler. I've lost track at
https://github.com/clojure/clojure/blob/master/src/jvm/clojure/lang/Compiler.java#L6624
after debugging this:
user> (def x `(quote ~(list 1 (clojure.lang.PersistentTreeMap/create (seq
[1 2 3 4])
#'user/x
user> x
(quote (1 #sorted-m
I'd really appreciate if others could take a look. I wonder if it may
be a Clojure reader bug.
On Thu, Aug 8, 2013 at 3:55 PM, Jozef Wagner wrote:
> It seems there is something else in data reader which causes this change.
>
> user=> (class '#foo/sm (1 2 3 4))
> clojure.lang.PersistentArrayMap
>
It seems there is something else in data reader which causes this change.
user=> (class '#foo/sm (1 2 3 4))
clojure.lang.PersistentArrayMap
user=> (class (read-string "#foo/sm (1 2 3 4)"))
clojure.lang.PersistentTreeMap
It's quite puzzling. In both cases the evaluation does not take place, but
s
That's a good point about:
user=> eval (to-sorted-map '(1 2 3 4)))
{1 2, 3 4}
But this should work, right?
user=> (assoc #sorted-map (:a 1 :b 2) :c 3)
{:c 3, :a 1, :b 2} ; incorrect
--
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this
The problem is the evaluation. PersistentTreeMap evaluates to the
PersistentArrayMap (or PersistentHashMap).
user=> (class (to-sorted-map '(1 2 3 4)))
clojure.lang.PersistentTreeMap
user=> (class #sorted-map (1 2 3 4))
clojure.lang.PersistentArrayMap
user=> (class #sorted-map (1 2 3 4 5 6 7 8 9 0
Thanks!
To confirm my understanding: in my original version I defined (using def) a
reference to a lazy sequence. I then evaluated it, using nth to pick a
value from the sequence. Because I have a reference to the beginning of the
sequence all the lazily generated items are retained. I.e. the lazy
Hi,
this is a “hold unto head” problem.
Am 17.11.2011 um 15:06 schrieb Julian Kelsey:
> (def seq-3s-n-5s
> (filter
> (fn [n] (or (= 0 (mod n 5)) (= 0 (mod n 3)) ) )
> (iterate inc 1)))
Here you keep a reference to the head of the generated by iterate. Make it a
function:
You could consider contributing your improvements to the logging library.
On Nov 11, 2011 10:27 AM, "finbeu" wrote:
> Thanks. I think when I tried it (correct me if I'm wrong) it was not
> possible to set the debug level dynamic. For instance I usually have a port
> where I can send messages to (
Thanks. I think when I tried it (correct me if I'm wrong) it was not
possible to set the debug level dynamic. For instance I usually have a port
where I can send messages to (simple UDP datagram packet), the message
string is a map which I read-string and eval and upon that event, I reset
some
On Fri, Nov 11, 2011 at 9:25 AM, finbeu wrote:
> yes, when starting my project, I was looking at the logging library which
> resides (resided) in clojure.contrib and I didn't like it at that point in
> time. I think because it was trying to do too many things at once. If my use
> case can be solve
yes, when starting my project, I was looking at the logging library which
resides (resided) in clojure.contrib and I didn't like it at that point in
time. I think because it was trying to do too many things at once. If my
use case can be solved with some small java wrappers, I try to do it on my
On Fri, Nov 11, 2011 at 8:53 AM, finbeu wrote:
> no, not yet. I stick with my own simple logging ns which works nice so far.
> Just have to fix this ...)
I just wondered whether using a well-maintained "standard" library
might be an easier path than rolling your own...
> (but I use clojure.java.
Yes! That's it. With pr-str it works. Thx!!
--
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 post.
To uns
Hi Sean
no, not yet. I stick with my own simple logging ns which works nice so far.
Just have to fix this ...)
(but I use clojure.java.jdbc with Sybase ASE 15.0.3. I hope I will find
some time soon to contribute some testcases.)
Finn
--
You received this message because you are subscribed to
Hi,
what happens is probable that the logger tries to turn the lazy seq object
itself into a string. Try calling pr-str on the seq before passing it to
debug: (debug (pr-str your-seq-object)).
Sincerely
Meikel
--
You received this message because you are subscribed to the Google
Groups "Cloju
Have you tried clojure.tools.logging to see whether you get the same behavior?
On Fri, Nov 11, 2011 at 8:15 AM, finbeu wrote:
> Hello,
> I'm using log4j and have some a simple wrappers in clojure that work well so
> far.
> Actually, I do
> (def *logger* (Logger/getRootLogger))
>
> Then I set logl
On Wed, Sep 14, 2011 at 12:05 AM, Sergey Didenko
wrote:
> Also bear in mind that due to the functional nature of Clojure you can
> debug a lot of problems using tracing, like clojure.contrib.trace (for
> < 1.3)
Coming soon to 1.3! Luc Prefontaine has volunteered to maintain this
library as clojur
Also bear in mind that due to the functional nature of Clojure you can
debug a lot of problems using tracing, like clojure.contrib.trace (for
< 1.3), C-c C-t in Emacs, or this handy macro:
(defmacro dbg[x] `(let [x# ~x] (println "dbg:" '~x "=" x#) x#))
(func1 (func2 arg1) arg2) -> (dbg (func1 (db
Eclipse with CounterClockwise is ok (relatively speaking). With it one
can do the usual:
- breakpoints (no conditional)
- stepping in/out
- examine variables from different call frames
But thats pretty much what it can do now. Neither Changing variable's
value nor expression evaluation works,
Sort of.
http://georgejahad.com/clojure/cdt.html
Jonathan
On Sat, Sep 10, 2011 at 5:36 PM, Dennis Haupt wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
> hi there,
>
> what's the currently best way to debug a clojure program?
> ideally, i want to see all vars, symbols, functions et
The basic observation was as follows :
Suppose I have a java project called "tinyJava" and a clojure project
called "tiny". To use the clojure code in java, I had to export the
clojure as a jar (say ttt.jar), and then in the java project I had to
do the following :
a)Rightclick on project tinyJav
That did the trick.
The keys on my keyboard that spell out "println" thank you.
On Sun, Jan 30, 2011 at 2:25 PM, George Jahad
wrote:
> Hey Daniel:
>
> I'm embarrassed to say I've never tried it before on 1.3. You've
> found a real bug. I'll try to get a proper patch out later today, but
> if y
Hey Daniel:
I'm embarrassed to say I've never tried it before on 1.3. You've
found a real bug. I'll try to get a proper patch out later today, but
if you're in a hurry, you might try changing this line in cdt.clj:
(def ge (memoize #(first (find-methods (va) #"get"
to this:
(def ge (memoiz
you may want to also post this on the jetbrains la clojure forum
http://devnet.jetbrains.net/community/idea/clojure?view=discussions
On Wed, Dec 15, 2010 at 12:00 AM, HiHeelHottie wrote:
>
> I'm using IntelliJ Idea 10 with the La Closure plugin version 0.3.15
> and Java 6 I've added Clojure 1.2
interesting. thanks for the thoughtful reply.
On Sun, Jan 24, 2010 at 2:08 PM, Richard Newman wrote:
> That said (and I'm not trying to make this a "charged" statement ... just a
>> way to learn more) I had always thought that one of the key things that made
>> lisp so complete was that program
That said (and I'm not trying to make this a "charged" statement ...
just a way to learn more) I had always thought that one of the key
things that made lisp so complete was that programs don't just
crash ... that debugging is fully-baked into the *core* of
everything. Now, I don't remembe
It has confused me since the day I tried to mess around with clojure that
this topic isn't brought up more (not that I follow clj regularly) ... so
I'm happy to learn that someone added trace capabilities.
That said (and I'm not trying to make this a "charged" statement ... just a
way to learn mor
Be careful of deftrace. It has a bug that crashes when the defn'ed
funcs have string comment on the top of the func
On Jan 23, 7:02 am, ataggart wrote:
> On Jan 22, 6:27 pm, Mike Meyer
>
>
> 620...@mired.org> wrote:
> > On Fri, 22 Jan 2010 17:25:39 -0800
>
> > ajay gopalakrishnan wrote:
> > > I
2010/1/23 ataggart :
> If the authors of of c.c.trace are
> amenable, I'm inclined to add this functionality to a variant of the
> c.c.logging/spy macro
Great idea!
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to
On Jan 22, 1:40 pm, Krukow wrote:
> Please don't top post.
Seriously, people still complain about this? It's the default
behavior in Google Groups, so I think you just have to live with it.
Find a news reader that doesn't suck.
--
You received this message because you are subscribed to the Goo
On Jan 22, 6:27 pm, Mike Meyer wrote:
> On Fri, 22 Jan 2010 17:25:39 -0800
>
> ajay gopalakrishnan wrote:
> > I dont mind using println. The problem is that needs to be inside a do or
> > when ... and that is not really part of my code. When the time comes to
> > remove the prints, i need to re
On Fri, 22 Jan 2010 17:25:39 -0800
ajay gopalakrishnan wrote:
> I dont mind using println. The problem is that needs to be inside a do or
> when ... and that is not really part of my code. When the time comes to
> remove the prints, i need to remove all these do blocks too. I can leave
> them as
Hi,
On Jan 22, 2:14 am, ajay gopalakrishnan wrote:
> I usually debug by adding println statements.
if you use Emacs is this statement is true for other programming
languages, too, you might be interested in using lldebug. I'm pretty
sure, that when you ask the author to add support for Clojure
On Jan 22, 5:25 pm, ajay gopalakrishnan wrote:
> I dont mind using println. The problem is that needs to be inside a do or
> when ... and that is not really part of my code. When the time comes to
> remove the prints, i need to remove all these do blocks too. I can leave
> them as it is I guess,
I dont mind using println. The problem is that needs to be inside a do or
when ... and that is not really part of my code. When the time comes to
remove the prints, i need to remove all these do blocks too. I can leave
them as it is I guess, but then it is not neat and non-idiomatic. From all
the r
On Jan 22, 4:13 pm, Mike Meyer wrote:
> On Fri, 22 Jan 2010 10:08:45 +0200
>
>
>
>
>
> Miron Brezuleanu wrote:
> > Hello,
>
> > On Fri, Jan 22, 2010 at 3:14 AM, ajay gopalakrishnan
> > wrote:
>
> > > Hi,
>
> > > I usually debug by adding println statements. How can I achieve the same
> > > eff
On Fri, 22 Jan 2010 10:08:45 +0200
Miron Brezuleanu wrote:
> Hello,
>
> On Fri, Jan 22, 2010 at 3:14 AM, ajay gopalakrishnan
> wrote:
>
> > Hi,
> >
> > I usually debug by adding println statements. How can I achieve the same
> > effect in Clojure. I don't think I can introduce println at arbit
On Jan 22, 2:27 am, ajay gopalakrishnan wrote:
> Is this the preferred way of debugging in Clojure?
Please don't top post.
I've heard people have success with regular debuggers, e.g. JSwat,
although I haven't tried this myself...
/Karl
--
You received this message because you are subscribed
(comment) and #_ are pretty useful to disable forms when debugging:
(+ 3 #_4) -> 3
(comment println "hi") -> nil
Excerpts from David Nolen's message of Fri Jan 22 02:38:29 -0300 2010:
> I find that injecting print statements is painful if you're not using
> something like paredit (Emacs). With pa
On Jan 22, 2010, at 9:08 , Miron Brezuleanu wrote:
> I also use 'do's as others have suggested. Another trick is to add dummy
> variables in lets just to be able to print something. For instance,
>
> (let [a 1
>b 2
>dummy1 (println "stuff")
>c 3]
> ...)
Isn't the ideo
Hello,
On Fri, Jan 22, 2010 at 3:14 AM, ajay gopalakrishnan wrote:
> Hi,
>
> I usually debug by adding println statements. How can I achieve the same
> effect in Clojure. I don't think I can introduce println at arbitrary places
> to figure out at which step is the algorithm failing.
>
I also us
I find that injecting print statements is painful if you're not using
something like paredit (Emacs). With paredit it's quite simple.
On Thu, Jan 21, 2010 at 8:27 PM, ajay gopalakrishnan wrote:
> Is this the preferred way of debugging in Clojure?
>
>
> On Thu, Jan 21, 2010 at 5:25 PM, Richard New
Logging side-effects usually occur within a do block, or the
equivalent, e.g., when, catch. For production code, I'd suggest a
logging library instead of filling your code with printlns. Contrib
has a logging lib that delegates to common java logging libraries, but
allows for writing them in a mo
I don't know about *the* preferred way, but it's my preferred way.
It's a no-brainer to add print statements. I believe there is at
least one logging library available too.
On Jan 21, 7:27 pm, ajay gopalakrishnan wrote:
> Is this the preferred way of debugging in Clojure?
>
> On Thu, Jan 21, 201
Is this the preferred way of debugging in Clojure?
On Thu, Jan 21, 2010 at 5:25 PM, Richard Newman wrote:
> I usually debug by adding println statements. How can I achieve the same
>> effect in Clojure. I don't think I can introduce println at arbitrary places
>> to figure out at which step is t
I usually debug by adding println statements. How can I achieve the
same effect in Clojure. I don't think I can introduce println at
arbitrary places to figure out at which step is the algorithm failing.
Sure you can. You might need to add a (do ) block if you're wanting to
add them in an (
Hi,
On Dec 16, 11:14 am, George Jahad
wrote:
> It can be tough debugging macros in Clojure. Here's a quick demo of
> using the debug-repl to do
> so:http://georgejahad.com/clojure/debug-repl-macros.html
Very cool.
Sincerely
Meikel
--
You received this message because you are subscribed to t
Forgot to mention that the debug-repl seems to work fine with slime,
if you use the *inferior-lisp* buffer
On Dec 16, 2:14 am, George Jahad wrote:
> It can be tough debugging macros in Clojure. Here's a quick demo of
> using the debug-repl to do
> so:http://georgejahad.com/clojure/debug-repl-ma
select returns a set, so you need to call seq/vec before calling nth.
user> (nth (seq (clojure.set/select #(zero? (mod % 2)) #{1 2 5 10}))
0)
2
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post
Hi Jose,
> ; trying to get the first element of an unordered set
> (nth (clojure.set/select #(= 0 (mod % 2)) #{1 2 5 10}) 0)
> Why do I get different messages running from the REPL or loading from a clj
> file ?
I tried it from REPL and file using the from source Clojure 1.1.0-
alpha-SNAPSHOT,
a
oh yeah . . . .been down the prn road for many many hours, myself.
seems like a lot of nice people here ready to help so i'll get back
into it soon and post specific problems. . . . there are a lot lot lot of
them, so i am sure it will take some time.
Thanks for the ideas.
On Mon, Jun 29,
My negative experience with debugging touches on a number of things, but the
biggest is the way that lazy evaluation makes it hard to determine cause and
effect while debugging. This has been a problem, and I've had to do a lot of
(prn) calls to try and identify what's going on.
I eventually have
> If you're finding that you're managing a lot of state, and thus have
> trouble debugging, then you're probably not taking a sufficiently
> functional approach. (A big hint is if you find yourself wanting a
> stepping debugger to watch values change. It's the "change" part
> that's worrying!)
pe
> at the risk of sounding negative and (-; thus getting
> "moderated" ;-) ... I'm very interested in taking another stab at
> clojure after putting it down for a while, but I had real trouble
> debugging my programs. I'm looking for advice and/or an approach.
Aside from two areas — JVM pro
On Mar 11, 2009, at 19:04, Jerry K wrote:
> I had thought a while back about digging into building some math code
> for clojure contrib for applications like algebra and number theory,
> since Clojure's Lispyness makes it well suited for that, but wasn't
> sure anybody else was especially interes
On Mar 11, 2009, at 11:04 AM, Jerry K wrote:
>
> Also, I've not looked at any of the math code in clojure contrib, but
> expressed as such, I wouldn't expect the idiom "(mod (expt n exp) m)"
> to be at all fast for reasons largely independent of the numeric
> implementation underneath.
>
> Compu
Jerry K writes:
Hi Jerry,
> Also, I've not looked at any of the math code in clojure contrib, but
> expressed as such, I wouldn't expect the idiom "(mod (expt n exp) m)"
> to be at all fast for reasons largely independent of the numeric
> implementation underneath.
Yes, you're right. And afte
Mark Engelberg writes:
Hi Mark,
> On Wed, Mar 11, 2009 at 12:21 AM, Tassilo Horn wrote:
>
>> Investigated it a bit more (doing the algorithm step by step in the
>> repl) and now I know what's the culprit: The `expt' function from
>> the math contrib library is dead slow.
>
> Dead slow? Compa
Also, I've not looked at any of the math code in clojure contrib, but
expressed as such, I wouldn't expect the idiom "(mod (expt n exp) m)"
to be at all fast for reasons largely independent of the numeric
implementation underneath.
Computing the entire power and then reducing it modulo m is going
On Wed, Mar 11, 2009 at 12:21 AM, Tassilo Horn wrote:
> Investigated it a bit more (doing the algorithm step by step in the
> repl) and now I know what's the culprit: The `expt' function from the
> math contrib library is dead slow.
Dead slow? Compared to what? A naive expt function just mult
Just updated, working like a charm.
On Tue, Mar 10, 2009 at 5:17 PM, CuppoJava wrote:
>
> Have you updated to the latest version?
>
> If it's setup properly, you should be able to set breakpoints by
> clicking on the grey column on the left side of your code.
>
> Also, not every line can be brea
Probably. The Java BigInteger classes are not particularly fast, and do not
seem to be a priority to Sun. Therefore Clojure is not competitive on large
integer algorithms.
On Wed, Mar 11, 2009 at 2:21 AM, Tassilo Horn wrote:
>
> Phil Hagelberg writes:
>
> Hi Phil,
>
> >> If not, is there bette
Phil Hagelberg writes:
Hi Phil,
>> If not, is there better way than inserting gazillions of printlns to
>> check why and where a function doesn't do the right thing?
>
> Most definitely! Break your functions up into smaller pieces, then
> write tests for them using test-is. If your functions a
Joshua writes:
Hi Joshua,
> The eclipse plugin also provides some debugging support.
Ok, so Eclipse & IntelliJ support debugging. Does SLIME do, too?
Bye,
Tassilo
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Have you updated to the latest version?
If it's setup properly, you should be able to set breakpoints by
clicking on the grey column on the left side of your code.
Also, not every line can be breakpointed. Try breakpointing some
different lines if you're having problems there.
-Patrick
--~--~--
On Tue, Mar 10, 2009 at 2:44 PM, CuppoJava wrote:
>
> The IntelliJ plugin supports debugging.
>
I must have missed this; the UI didn't seem to allow for setting of breakpoints.
> And using JSwat is also possible, but a little less streamlined.
> -Patrick
> >
>
--
Howard M. Lewis Ship
Cre
The eclipse plugin also provides some debugging support.
Joshua
On Mar 10, 5:33 pm, Tassilo Horn wrote:
> Hi all,
>
> is there any debugging support for clojure which lets one step though a
> function? If not, is there better way than inserting gazillions of
> printlns to check why and where a
The IntelliJ plugin supports debugging.
And using JSwat is also possible, but a little less streamlined.
-Patrick
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Clojure" group.
To post to this group, send email t
Tassilo Horn writes:
> If not, is there better way than inserting gazillions of printlns to
> check why and where a function doesn't do the right thing?
Most definitely! Break your functions up into smaller pieces, then write
tests for them using test-is. If your functions are hard to test,
it'
Oh I'm sorry, I was still accidentally running the previous version.
Indentation works perfectly.
Thank you very much for this plugin. Debugging support is so
invaluable to me.
May I ask how long you think the Surround-With feature will take?
-Patrick
PS: I found your profile on the IntelliJ t
Hello.
What do you mean by "automatically indent"? If you press enter inside
a Sexpr, vector or map, indentation will be ferformed automatically.
Kind regards,
Ilya
On Mar 1, 1:37 am, CuppoJava wrote:
> Wow it's incredible how fast your progressing on the plugin. It's
> already a joy to use. T
Wow it's incredible how fast your progressing on the plugin. It's
already a joy to use. Thank you very much.
Is there a way to automatically indent when I press Enter?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
As a follow-on to this, it turns out that debugging works *only* when
I pull the files in via require; neither slime-load-file nor
slime-eval-buffer nor load-file result in breakpoints getting hit.
On Fri, Oct 24, 2008 at 1:27 PM, Craig Andera <[EMAIL PROTECTED]> wrote:
>>> It's very likely/nearl
On Fri, Oct 24, 2008 at 10:31 AM, Craig Andera <[EMAIL PROTECTED]> wrote:
>
>>> It's very likely/nearly certain I'm still doing something wrong - I
>>> appreciate the help.
>
> Indeed it was me: everything started working as soon as I made sure my
> .clj files were in CLASSPATH the way require des
>> It's very likely/nearly certain I'm still doing something wrong - I
>> appreciate the help.
Indeed it was me: everything started working as soon as I made sure my
.clj files were in CLASSPATH the way require describes they should be.
I'm sure it doesn't help that I'm a Java n00b in addition to
On Fri, Oct 24, 2008 at 8:16 AM, Craig Andera <[EMAIL PROTECTED]> wrote:
>
>> No, that's not enough. You didn't specify the port that you want to
>> connect to JSwat on. add "address=" (or something similar) to this
>> to specify which port you want to use. In my blog example, I'm using
>> "88
> No, that's not enough. You didn't specify the port that you want to
> connect to JSwat on. add "address=" (or something similar) to this
> to specify which port you want to use. In my blog example, I'm using
> "":
> -Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=
>
Hi Craig,
On Fri, Oct 24, 2008 at 7:55 AM, Craig Andera <[EMAIL PROTECTED]> wrote:
>
>> Are you doing all of the following:
>>
>> 1. Specify the appropriate debug options when you start Clojure (see
>> step #4 in my blog post)
>
> Yep. Here's the full command line:
>
> c:\WINDOWS\system32\java.ex
> Are you doing all of the following:
>
> 1. Specify the appropriate debug options when you start Clojure (see
> step #4 in my blog post)
Yep. Here's the full command line:
c:\WINDOWS\system32\java.exe -Xdebug
-Xrunjdwp:transport=dt_socket,server=y,suspend=n -cp
"C:/bin/clojure/clojure/svn/cloju
1 - 100 of 108 matches
Mail list logo
