Re: cljs.test :after fixture not called if test errors

Makes sense. Thanks all! On Wed, Nov 25, 2020, 6:46 PM David Nolen wrote: > In the async case just handle the error yourself and fail the test. > There's really not a good way to detect async errors since there isn't one > way to. do async (promises, core.async, etc.). > > David

Re: cljs.test :after fixture not called if test errors

In the async case just handle the error yourself and fail the test. There's really not a good way to detect async errors since there isn't one way to. do async (promises, core.async, etc.). David On Wed, Nov 25, 2020 at 1:19 AM Stuart Campbell wrote: > That unfortunately doesn't work for as

Re: cljs.test :after fixture not called if test errors

(finally (println "after") > > O mércores, 25 de novembro de 2020 á/s 00:17:03 UTC+1, > stuart.will...@gmail.com escribiu: > >> Hello, >> >> I'm experimenting with fixtures and it seems like :after fixtures aren't >> run if a test un

Re: cljs.test :after fixture not called if test errors

:after fixtures aren't > run if a test unexpectedly errors. E.g.: > > (use-fixtures :once {:before #(println "before") > :after #(println "after")}) > > (deftest a-test > (raise (js/Error. "oops"))) > >

cljs.test :after fixture not called if test errors

Hello, I'm experimenting with fixtures and it seems like :after fixtures aren't run if a test unexpectedly errors. E.g.: (use-fixtures :once {:before #(println "before") :after #(println "after")}) (deftest a-test (raise (js/Error. "oops")

ANN: Promenade - Elegant handling of errors and other oddities (Clojure/ClojureScript)

Hi, I am pleased to announce Promenade - a Clojure/ClojureScript library to elegantly handle errors and other oddities: Project: https://github.com/kumarshantanu/promenade Docs: https://github.com/kumarshantanu/promenade/blob/master/doc/intro.md Promenade helps one express odd conditions

Re: Cider - emacs lisp errors reported

On Sunday, 10 December 2017 14:14:05 UTC, Bozhidar Batsov wrote: > > It might have been changed upstream. Not sure what's your Emacs version. A > while ago we backported this macro in whatever its current form was for > compatibility with older Emacsen. > > File a ticket on GitHub and we'll

Cider - emacs lisp errors reported

I encountered the same problem some years ago. In my case the problem was solved by removing (require 'cl-lib) line in my init.el file. The cl-lib package defined when-let as well. I hope that this will help you out! -- You received this message because you are subscribed to the Google

Re: Cider - emacs lisp errors reported

It might have been changed upstream. Not sure what's your Emacs version. A while ago we backported this macro in whatever its current form was for compatibility with older Emacsen. File a ticket on GitHub and we'll investigate. On 10 December 2017 at 13:44, Peter Hull

Cider - emacs lisp errors reported

I noticed this when updating cider via melpa, and I wasn't sure if it's already known about or whether it is even an problem. I thought I'd ask here before submitting an issue to github. Compiling file /Users/peterhull/.emacs.d/elpa/cider-20171209.1602/cider-browse-spec.el at Sun Dec 10

Re: Errors

ss sensitive > there than in calls during the runtime. Colin's talk from last year's conj > gives a good idea of some of the challenges in working on this stuff. > https://www.youtube.com/watch?v=kt4haSH2xcs > >> And my favorite response from Alex: >> >> > If I can

Re: Errors

f the challenges in working on this stuff. https://www.youtube.com/watch?v=kt4haSH2xcs > And my favorite response from Alex: > > > If I can make a request, it would be that instead of saying "errors are > bad" (which is honestly, not helpful by itself), but to step

Re: Errors

nstead of saying "errors are bad" > (which is honestly, not helpful by itself), but to step back and either take > a broader approach towards systemic issues This is so reasonable I’m embarrassed I was a bit glib in my first note. I mean it’s not like they are C++ template errors from 1

Re: Errors

On Monday, December 5, 2016 at 10:36:59 PM UTC-6, Sean Corfield wrote: > > Several of the Clojure/core folks have said at various times over the > years that Clojure is deliberately not optimized for novices, on the > grounds that whilst everyone starts out as a novice, most of your time >

Re: Errors

ability and threading are smart. I've been able > to finish a hobby project in clojure which I've been mulling for a long > time and never found the right environment. Super stuff. > > And the error messages are not good. > If I can make a request, it would be that instead of saying

Re: Errors

On Tuesday, 6 December 2016 10:47:42 UTC+8, James Reeves wrote: > > On 6 December 2016 at 01:28, wrote: >> >> And the error messages are not good. >> >> So I was wondering: Is this a philosophical thing? Or is it an effort >> thing? And if it is an effort thing, is there some

Re: Errors

> I cherrypicked a case where the runtime difference would be tiny I wouldn’t be so sure of that. Adding any additional code to the function call logic is going to impact almost every single expression in Clojure and that “tiny” difference is going to add up pretty fast. As others have

Re: Errors

Yeah I understand that tradeoff. I cherrypicked a case where the runtime difference would be tiny but others are harder I’m sure. I guess I will go figure out how spec applies to my project. Thanks as always. This group is so responsive. Appreciated. - Paul > On Dec 5, 2016, at 9:46

Re: Errors

On 6 December 2016 at 01:28, wrote: > > And the error messages are not good. > > So I was wondering: Is this a philosophical thing? Or is it an effort > thing? And if it is an effort thing, is there some sort of plan for what > effort to put in? And if so, can I help by closing

Re: Errors

I think it has been rehashed often and core is very conservative about changes, but the current latest and greatest for improving many kinds of errors is going to be clojure.spec, which runs parallel to the actual execution path, so as not to effect things like performance or old code that depends

Errors

Hi! Boy I really think you've all done a nice job with Clojure. I've used quite a few environments over the years and clojure + CIDER + etc is a great experience. The immutability and threading are smart. I've been able to finish a hobby project in clojure which I've been mulling for a long

Re: Common runtime errors in clojure

Compiling a list of these common errors is a great idea (particularly if then turned into some kind of How-To guide for interpreting errors) I think anyone who learns Clojure learns to subconsciously internalize these errors and what they mean. However, for somewhat just starting out

Common runtime errors in clojure

Hi group, I was googling for enumeration of commons runtime errors in clojure, but i couldnt find anything much. Stuart Sierra has a couple of blog post on do/donts in clojure, but is not an exhaustive listing. I understand that using interop will inherit most of the runtime errors you

Re: Common runtime errors in clojure

them out and see. Andy On Sat, Feb 6, 2016 at 2:26 PM, kovas boguta <kovas.bog...@gmail.com> wrote: > Compiling a list of these common errors is a great idea (particularly if > then turned into some kind of How-To guide for interpreting errors) > > I think anyone who lea

Re: Manifold streams/deferreds raising errors downstream of a sink

Hi Andy, To give you some context on this, `put!` will return true if the thing directly downstream accepts the value (in this case, the stream). The fact that the callback in `consume` fails is between the stream and the callback, and is not propagated all the way back (though the exception

Re: Manifold streams/deferreds raising errors downstream of a sink

Hi Andy, I would provide a function that wraps put!. It would still return a deferred, but not the result of put!. It would create a deferred, representing the result of the computation and pass it down the stream together with the input. Consumers would set its value once the computation is

Manifold streams/deferreds raising errors downstream of a sink

Hey All, I'm trying to build a library that exposes manifold streams for data producing applications. The intention would be for these apps to s/put! to a sink stream returned by the producer function. However, I need to take the value that is put in and pipe it into some other function before

Re: Complete lack of helpful compilation errors with :gen-class

-5, Mars0i wrote: I don't have anything helpful to say, but: I've often gotten a useful stacktrace from compile-time errors using 'lein compile' with :gen-class. Not always. Sometimes I have to use the guess-and-comment-out method. So I think that whatever's happening is not just an issue

Re: Complete lack of helpful compilation errors with :gen-class

compile-time errors using 'lein compile' with :gen-class. Not always. Sometimes I have to use the guess-and-comment-out method. So I think that whatever's happening is not just an issue with compilation of gen-class. Maybe an issue involving libraries? This page http

Re: Complete lack of helpful compilation errors with :gen-class

wrote: I don't have anything helpful to say, but: I've often gotten a useful stacktrace from compile-time errors using 'lein compile' with :gen-class. Not always. Sometimes I have to use the guess-and-comment-out method. So I think that whatever's happening is not just an issue

Re: Complete lack of helpful compilation errors with :gen-class

in between the two tests. And this only happens when my Clojure file is subclassing a Java object. Very, very strange... On Monday, August 3, 2015 at 12:27:38 AM UTC-5, Mars0i wrote: I don't have anything helpful to say, but: I've often gotten a useful stacktrace from compile-time errors using 'lein

Re: Complete lack of helpful compilation errors with :gen-class

a useful stacktrace from compile-time errors using 'lein compile' with :gen-class. Not always. Sometimes I have to use the guess-and-comment-out method. So I think that whatever's happening is not just an issue with compilation of gen-class. Maybe an issue involving libraries? This page http

Re: Complete lack of helpful compilation errors with :gen-class

Yay, this is the kind of insight I was hoping for! ^_^ On Monday, August 3, 2015 at 9:49:17 AM UTC-5, Mars0i wrote: Ah--if that's the problem, it sounds familiar. Try doing 'lein clean' before 'lein compile' and see whether you get the same error. That's assuming you have

Re: Complete lack of helpful compilation errors with :gen-class

happens when my Clojure file is subclassing a Java object. Very, very strange... On Monday, August 3, 2015 at 12:27:38 AM UTC-5, Mars0i wrote: I don't have anything helpful to say, but: I've often gotten a useful stacktrace from compile-time errors using 'lein compile' with :gen-class

Re: Complete lack of helpful compilation errors with :gen-class

is lost. Then when something tries tor refer to the class which was supposed to have been compiled and fails, the linkage error happens. But now that you have pointed me at a way to just invoke the compiler directly on my problem source file, I bet I will be able to see the compilation errors when I

Complete lack of helpful compilation errors with :gen-class

I don't know if this is an issue with the compiler in general, with Leiningen more specifically, or something I am doing wrong in trying to use them, but I have wasted many hours over the last couple weeks while working on afterglow-max https://github.com/brunchboy/afterglow-max#afterglow-max

Re: Complete lack of helpful compilation errors with :gen-class

I don't have anything helpful to say, but: I've often gotten a useful stacktrace from compile-time errors using 'lein compile' with :gen-class. Not always. Sometimes I have to use the guess-and-comment-out method. So I think that whatever's happening is not just an issue with compilation

Re: Testing macros that throw errors at compile time?

* exception is being thrown. On Thu, Jan 22, 2015 at 4:41 PM, Scott Rabin scott...@gmail.com javascript: wrote: We have a few macros in my employer's codebase that throw compile-time errors when you've given them invalid configurations, and have generally simply tested the result of these macros

Re: Testing macros that throw errors at compile time?

: We have a few macros in my employer's codebase that throw compile-time errors when you've given them invalid configurations, and have generally simply tested the result of these macros and not necessarily the direct expansion of said macros. What we would like to do is *test* that the macro

Re: Testing macros that throw errors at compile time?

employer's codebase that throw compile-time errors when you've given them invalid configurations, and have generally simply tested the result of these macros and not necessarily the direct expansion of said macros. What we would like to do is *test* that the macro blows up; but unfortunately

Testing macros that throw errors at compile time?

We have a few macros in my employer's codebase that throw compile-time errors when you've given them invalid configurations, and have generally simply tested the result of these macros and not necessarily the direct expansion of said macros. What we would like to do is *test* that the macro

Warnings as errors

Hi list, Is there a way to get Clojure warnings to act as errors and abort the attempted operation? For now, I'm mainly interested in doing this in the repl, because I will often do something like this: (defn fn [x] (+ 1 x)) ; WARNING: fn already refers to: #'clojure.core/fn ... Oops

Re: handling agent errors

input), so I do a try/catch in the agent, log any errors, and continue with the next job. First question: how to deal with OOM (the Xmx limit, not the OS out of mem)? The try/catch doesn't appear to help, here. The agent dies, and all subsequent jobs never run. Is there some way to prevent

Re: handling agent errors

fail in any number of unanticipated ways (due to user input), so I do a try/catch in the agent, log any errors, and continue with the next job. First question: how to deal with OOM (the Xmx limit, not the OS out of mem)? The try/catch doesn't appear to help, here. The agent dies, and all

handling agent errors

Two questions, really. I'm running large batch jobs with an agent. The jobs may fail in any number of unanticipated ways (due to user input), so I do a try/catch in the agent, log any errors, and continue with the next job. First question: how to deal with OOM (the Xmx limit, not the OS out

Re: handling agent errors

On Mon, Aug 11, 2014 at 3:07 PM, Brian Craft craft.br...@gmail.com wrote: Two questions, really. I'm running large batch jobs with an agent. The jobs may fail in any number of unanticipated ways (due to user input), so I do a try/catch in the agent, log any errors, and continue with the next

Data Literals: How to handle read errors?

Hey there, I upgraded to JDK8 and wanted to start using the new java.time.* packages. I started by implementing reader functions to get rid of #inst like: #time/local-date [2014 4 13] #time/local-datetime [2014 4 13 14 23] While that works fine and as expected, one thing I ran into is

Re: Data Literals: How to handle read errors?

On Apr 13, 2014, at 8:31 AM, Thomas Heller th.hel...@gmail.com wrote: [...] confusing error messages. user= (pr-str #time/local-datetime [2014 4 1 0 0 2 999]) [...] RuntimeException Unmatched delimiter: ) clojure.lang.Util.runtimeException (Util.java:221) Using default #inst

Re: Data Literals: How to handle read errors?

Ah, didn't even think about the REPL causing trouble here. Thanks. On Sunday, April 13, 2014 5:30:09 PM UTC+2, squeegee wrote: On Apr 13, 2014, at 8:31 AM, Thomas Heller th.h...@gmail.comjavascript: wrote: […] confusing error messages. user= (pr-str #time/local-datetime [2014 4 1 0 0 2

lein script installation errors on CentOS 6.5

The lein script is producing errors when I try to install it on CentOS 6.5: $ lein /sw/bin/lein: command substitution: line 93: syntax error near unexpected token `)' /sw/bin/lein: command substitution: line 93: `dirname $PWD)' /sw/bin/lein: command substitution: line 110: syntax error near

Re: lein script installation errors on CentOS 6.5

Scripts in Red Hat ought to begin with #!/bin/bash which is writable only by root and kept updated by system updates. But lein uses #!/usr/bin/env bash -- use whatever bash executable is on my path -- which is less well controlled and might be different. Try which bash to see what shell is

Re: lein script installation errors on CentOS 6.5

Resolved, thanks. Still puzzled as Red Hat's /bin/bash is 4.1.2 and my custom /sw/bin/bash is 4.2.24. Surely such a minor version difference should not result in such a catastrophe? gvim On 14/01/2014 01:31, Matching Socks wrote: Scripts in Red Hat ought to begin with #!/bin/bash which is

Re: sending errors to the ui - web development using luminus

messages. You can also write custom validation rules in case the basic set isn't what you need. On Fri, Aug 9, 2013 at 2:02 AM, Abraham abev...@gmail.com wrote: Dear How to send validate the input and then send all errors at a time .? I am using luminus , the doc shows send one error at a time

sending errors to the ui - web development using luminus

Dear How to send validate the input and then send all errors at a time .? I am using luminus , the doc shows send one error at a time. Thanks in advance A -- -- You received this message because you are subscribed to the Google Groups Clojure group. To post to this group, send email to clojure

Why are errors in nested futures suppressed?

Hi all, If the function executed in a future throws an error it is printed out in the repl immediately. If that function is executed in a future which itself is executed in a future then it isn't. For example, imagine somebody wrote the following code (please, suspend belief and just accept

Re: Why are errors in nested futures suppressed?

= (future (swap! atom inc 0)) #core$future_call$reify__6267@38db2b7e: :pending = @(future (swap! atom inc 0)) ClassCastException clojure.core$atom cannot be cast to clojure.lang.Atom clojure.core/swap! (core.clj:2161) (both in ccw, but i notice that the first statement does throw in lein repl)

Re: Namespaced symbols, and errors

Here's another mental model that you can use. (Not sure it is 100% accurate with the actual implementation, but it has served me well so far.) Keywords are not bound, in the same sense that numbers are not bound. 1 is 1, just as 2 is 2, whatever the namespace you are into. 1 from the user

Re: Namespaced symbols, and errors

On Friday, March 8, 2013 4:56:03 PM UTC+1, nick rothwell wrote: Typing the following at a REPL: (str ::junk/junk) (where there's no alias for junk) gives me: RuntimeException Invalid token: ::junk/junk clojure.lang.Util.runtimeException (Util.java:219) RuntimeException Unmatched

Re: Namespaced symbols, and errors

The reader basically transforms :: into :namespace/, which means that the remaining part must be an unqualified symbol (i.e. no / in it). The character / is not allowed in unqualified symbols. As the documentation [1] says : '/' has special meaning, it can be used once in the middle of a symbol to

Re: Namespaced symbols, and errors

Gary, ::foo/bar is valid syntax if foo is a valid namespace alias. Try: (alias 'foo 'clojure.core) ::foo/bar Il giorno 09/mar/2013 09.36, Gary Verhaegen gary.verhae...@gmail.com ha scritto: The reader basically transforms :: into :namespace/, which means that the remaining part must be an

Re: Namespaced symbols, and errors

On 9 March 2013 12:27, Bronsa brobro...@gmail.com wrote: Gary, ::foo/bar is valid syntax if foo is a valid namespace alias. Try: (alias 'foo 'clojure.core) ::foo/bar I did not know that. Is that documented anywhere ? I was under the impression that :: was just intended as a shorthand to

Re: Namespaced symbols, and errors

I understand that ::foo is a keyword bound into the local namespace. I also understand (according to the docs) that :my.namespace/foo is the keyword foo in the namespace my.namespace. ::nsalias/foo is the keyword foo in the namespace my.namespace if I've aliased my.namespace to nsalias. But

Namespaced symbols, and errors

Typing the following at a REPL: (str ::junk/junk) (where there's no alias for junk) gives me: RuntimeException Invalid token: ::junk/junk clojure.lang.Util.runtimeException (Util.java:219) RuntimeException Unmatched delimiter: ) clojure.lang.Util.runtimeException (Util.java:219) A couple

Re: ClojureCLR errors on Mono Linux

running in VirtualBox on my Win7 PC. I installed Mono 2.10.8. I downloaded the zip for ClojureCLR 1.4.0 Debug-4.0. Extracted. mono Clojure.Main.exe Runs with no problem. mono Clojure.Compile.exe test.junk Runs with no problem. From the errors you report, I can only guess that some

Re: ClojureCLR errors on Mono Linux

. mono Clojure.Compile.exe test.junk Runs with no problem. From the errors you report, I can only guess that some pre-1.4 DLLs are being found somehow and loaded. For example, the field clojure.lang.RT.OutVar did not exist in ClojureCLR 1.3. I do not know how else to help. -David

Re: ClojureCLR errors on Mono Linux

for ClojureCLR 1.4.0 Debug-4.0. Extracted. mono Clojure.Main.exe Runs with no problem. mono Clojure.Compile.exe test.junk Runs with no problem. From the errors you report, I can only guess that some pre-1.4 DLLs are being found somehow and loaded. For example, the field clojure.lang.RT.OutVar

Re: ClojureCLR errors on Mono Linux

Shantanu, I created an Ubuntu 12.10 VM running in VirtualBox on my Win7 PC. I installed Mono 2.10.8. I downloaded the zip for ClojureCLR 1.4.0 Debug-4.0. Extracted. mono Clojure.Main.exe Runs with no problem. mono Clojure.Compile.exe test.junk Runs with no problem. From the errors you

Re: ClojureCLR errors on Mono Linux

with no problem. From the errors you report, I can only guess that some pre-1.4 DLLs are being found somehow and loaded. For example, the field clojure.lang.RT.OutVar did not exist in ClojureCLR 1.3. I do not know how else to help. -David On Saturday, December 15, 2012 10:17:59 PM

Re: ClojureCLR errors on Mono Linux

ClojureCLR errors using Mono 2.10 on Ubuntu 12.04 (they do not happen on Windows using either .NET or Mono): 1. when running Clojure.Compile.exe: Exception: System.MissingFieldException: Field 'clojure.lang.RT.OutVar' not found. 2. when using Clojure.Main.exe: Exception

ClojureCLR errors on Mono Linux

Hi, I noticed the following ClojureCLR errors using Mono 2.10 on Ubuntu 12.04 (they do not happen on Windows using either .NET or Mono): 1. when running Clojure.Compile.exe: Exception: System.MissingFieldException: Field 'clojure.lang.RT.OutVar' not found. 2. when using Clojure.Main.exe

Re: ClojureCLR errors on Mono Linux

This is when using ClojureCLR 1.4.0 Debug-4.0 version. Shantanu On Sunday, 16 December 2012 09:45:21 UTC+5:30, Shantanu Kumar wrote: Hi, I noticed the following ClojureCLR errors using Mono 2.10 on Ubuntu 12.04 (they do not happen on Windows using either .NET or Mono): 1. when running

Re: Reader errors with Datomic free

I've that result (with same config): ___ user #db/id[:db.part/db] #db/id[:db.part/db -125] ___ The # char is a special char for the reader. Be careful to have redefined it in your namespace ?.. Le jeudi 26 juillet 2012 00:02:50 UTC+2, tbc++ a écrit :

Re: Reader errors with Datomic free

In Leiningen, the reader side is in a different process (owned by Leiningen, without your project code on the classpath), than the execution side. So I think you see this error due to classpath separation: the lein side doesn't have data_readers.clj specification, or the reader functions

Reader errors with Datomic free

I'm using the new Clojars version of datomic-free: (defproject clj-lobapp 0.1.0-SNAPSHOT :description FIXME: write description :url http://example.com/FIXME; :license {:name Eclipse Public License :url http://www.eclipse.org/legal/epl-v10.html} :plugins [[lein-localrepo

Re: Clojurescript One Errors

On Mar 16, 10:19 pm, John Collins johnben...@gmail.com wrote: I copied the clojurescript one project and made changes to the html files. When I do (go) after `lein repl` I get errors in the browser about not being able to resolve some namespaces. And also the wiki makes no mention how

Clojurescript One Errors

I copied the clojurescript one project and made changes to the html files. When I do (go) after `lein repl` I get errors in the browser about not being able to resolve some namespaces. And also the wiki makes no mention how to compile the project after any modifications to the files. So please

Re: Clojure CDT up, cont, down, local-names throws arity errors after hitting breakpoint

I know. The church of emacs is becoming more compelling each day. As a convert from Vim, I have some baggage. I hope that won't be an issue. On Sat, Feb 11, 2012 at 10:50 AM, George Jahad cloj...@blackbirdsystems.net wrote: SeanC is referring to is the fact that swank-cdt now works seamlessly

Re: Clojure CDT up, cont, down, local-names throws arity errors after hitting breakpoint

SeanC is referring to is the fact that swank-cdt now works seamlessly with clojure-jack-in, thanks to the efforts @tavisrudd and the indefatigable technomancy. On Feb 9, 9:18 am, Sean Corfield seancorfi...@gmail.com wrote: On Wed, Feb 8, 2012 at 10:16 PM, George Jahad

Re: Clojure CDT up, cont, down, local-names throws arity errors after hitting breakpoint

On Thu, Feb 9, 2012 at 8:20 PM, Phil Hagelberg p...@hagelb.org wrote: Sean Neilan s...@seanneilan.com writes: It's on the github page at the top. Forgive me if I'm slow, but I can't find it. Can you be more specific? The canonical page for swank-clojure is

Re: Clojure CDT up, cont, down, local-names throws arity errors after hitting breakpoint

On Wed, Feb 8, 2012 at 10:16 PM, George Jahad cloj...@blackbirdsystems.net wrote: If you use Emacs and Swank-clojure, it is much easier to use swank-cdt, as your UI: http://georgejahad.com/clojure/swank-cdt.html I just want to chime in and say swank-clojure 1.4.0 has made this process so much

Re: Clojure CDT up, cont, down, local-names throws arity errors after hitting breakpoint

It works! Thank you so much for looking into this! I really appreciate what you have done. I went through the rest of the documentation and found three other minor misnomers. One, if you set a breakpoint on a function defined in the repl, you'll have problems. As long as anything you set a

Re: Clojure CDT up, cont, down, local-names throws arity errors after hitting breakpoint

I agree. I'm a Vim user currently but with Lisp/Clojure, Emacs is the way to go. On Thu, Feb 9, 2012 at 11:18 AM, Sean Corfield seancorfi...@gmail.comwrote: On Wed, Feb 8, 2012 at 10:16 PM, George Jahad cloj...@blackbirdsystems.net wrote: If you use Emacs and Swank-clojure, it is much

Re: Clojure CDT up, cont, down, local-names throws arity errors after hitting breakpoint

There's so much documentation about how to set up emacs with clojure but not a lot of sources saying which documentation works. Should I trust the readme for swank-clojure, the dev.clojure.org site, the comments on dev.clojure.org, the blog post at technomancy.us/149 or the radically simplified

Re: Clojure CDT up, cont, down, local-names throws arity errors after hitting breakpoint

Sean Neilan s...@seanneilan.com writes: Should I trust the readme for swank-clojure, the dev.clojure.org site, the comments on dev.clojure.org, the blog post at technomancy.us/149 or the radically simplified setup here? The swank-clojure readme should be the most reliable. You may find a

Re: Clojure CDT up, cont, down, local-names throws arity errors after hitting breakpoint

On Thu, Feb 9, 2012 at 7:06 PM, Phil Hagelberg p...@hagelb.org wrote: Sean Neilan s...@seanneilan.com writes: Should I trust the readme for swank-clojure, the dev.clojure.org site, the comments on dev.clojure.org, the blog post at technomancy.us/149 or the radically simplified setup here?

Re: Clojure CDT up, cont, down, local-names throws arity errors after hitting breakpoint

Sean Neilan s...@seanneilan.com writes: It's on the github page at the top. Forgive me if I'm slow, but I can't find it. Can you be more specific? The canonical page for swank-clojure is https://github.com/technomancy/swank-clojure Are you talking about instructions for using swank-clojure.el

Clojure CDT up, cont, down, local-names throws arity errors after hitting breakpoint

Hi All, I'm using Clojure 1.3.0 with CDT 1.2.6.2 on OSX Lion with Java 1.6. I want to set a breakpoint on -main on the program to be debugged. So, run lein repl on this program. It opens up port 8030 successfully. (This is based off the documentation here:

Re: Clojure CDT up, cont, down, local-names throws arity errors after hitting breakpoint

Sorry about that. As you noticed the doc here was out of date: http://georgejahad.com/clojure/cdt.html It should be fixed now. Just for your reference however that doc only describes the command line version of CDT. If you use Emacs and Swank-clojure, it is much easier to use swank-cdt, as

Re: Clojure CDT up, cont, down, local-names throws arity errors after hitting breakpoint

forgot to mention that Hugo Duncan is also working on a debugger which can be found here: https://github.com/pallet/ritz On Feb 8, 10:16 pm, George Jahad cloj...@blackbirdsystems.net wrote: Sorry about that.  As you noticed the doc here was out of date: http://georgejahad.com/clojure/cdt.html

Re: Errors w/ dynamic symbols in macro-utils or monads?

Does this still happen for you? It appears to still be the case in my environment. Dropping back to Clojure *1.2.1* seems to work but in addition to trying out monads, I need to use a library (clj-webdriver) that relies on Clojure *1.3.0* What to do? -- You received this message because

Re: Errors w/ dynamic symbols in macro-utils or monads?

ah: http://dev.clojure.org/display/design/Where+Did+Clojure.Contrib+Go clojure.contrib.monads - Migrated to clojure.algo.monads - lead Konrad Hinsenhttp://dev.clojure.org/jira/secure/ViewProfile.jspa?name=khinsen . - Status: latest build

good ways to deal with compiler errors in SLIME (emacs)

Hi, How can I see the error line number in SLIME? Or even somehow place editor point on the place of the error? For example when I load file in a lein repl, it prints: java.lang.Exception: Unable to resolve symbol: dd in this context (mytest.clj:447) However when I load this file in the SLIME

Re: good ways to deal with compiler errors in SLIME (emacs)

On Tue, Sep 13, 2011 at 1:55 AM, Sergey Didenko sergey.dide...@gmail.com wrote: How can I see the error line number in SLIME? Or even somehow place editor point on the place of the error? However when I load this file in the SLIME repl it just prints: Unable to resolve symbol: dd in this

Re: good ways to deal with compiler errors in SLIME (emacs)

Thanks, Phil ! That's it. I was using slime-load-file instead of slime-compile-and-load-file If you compile using C-c C-k (where it sends the filename instead of the contents of the file) then it can determine line numbering. -- You received this message because you are subscribed to the

Re: http-client and ignoring ssl errors

, I am trying to add some functionality to http-client. Basically, I need the ability to do get requests on a server while ignoring ssl errors. Once I figure out how to get it working, I'll put it up on github and people can pull it if they'd like. I am working from a fork of http-client

http-client and ignoring ssl errors

Hello All, I am trying to add some functionality to http-client. Basically, I need the ability to do get requests on a server while ignoring ssl errors. Once I figure out how to get it working, I'll put it up on github and people can pull it if they'd like. I am working from a fork of http

Re: ClojureScript Compile errors

On Wed, Aug 10, 2011 at 7:39 AM, Rich Hickey richhic...@gmail.com wrote: :use … :only doesn't have the problems of full :use. Enhancement ticket and patch for :use … :only welcome. Note it must support :use … :only only, i.e. :only is required. Rich

Errors in Clojure

Hello Clojurians, I'm struggling to work with errors in Clojure. This is one example, one case, but I had many like these before: user= (load-file /Users/pupeno/Projects/mgr/src/lobos/migrations.clj) org.postgresql.util.PSQLException: FATAL: role lobos does not exist (config.clj:1) It just

Re: Errors in Clojure

with errors in Clojure. This is one example, one case, but I had many like these before: user= (load-file /Users/pupeno/Projects/mgr/src/lobos/migrations.clj) org.postgresql.util.PSQLException: FATAL: role lobos does not exist (config.clj:1) It just gives one line, no stack trace. config.clj

Re: Errors in Clojure

:) 2011/8/19 J. Pablo Fernández pup...@pupeno.com: Hello Clojurians, I'm struggling to work with errors in Clojure. This is one example, one case, but I had many like these before: user= (load-file /Users/pupeno/Projects/mgr/src/lobos/migrations.clj) org.postgresql.util.PSQLException: FATAL: role

  1   2   3   >