Clojure shell calls results inconsistent with actual shell calls.

2012-07-11 Thread Eric in San Diego
In a shell, I can call > app arg1 arg2 arg3 arg4 arg5 arg6 arg7 and get my expected results. However, if I make what I think is the same call programmatically in clojure: (ns ... (:require [clojure.java.shell :as sh] )) (defn test [] (sh/sh "app" "arg1" "arg2" "arg3" "arg4" "arg5" ar

Re: Clojure shell calls results inconsistent with actual shell calls.

2012-07-11 Thread Eric in San Diego
Wednesday, July 11, 2012 3:23:38 PM UTC-7, Michael Klishin wrote: > > Eric in San Diego: > > > my app is throwing an error > > How about posting the error (and a snippet of your code)? Bonus points for > a Github repository that can be used > to reproduce. > > MK

Re: Clojure shell calls results inconsistent with actual shell calls.

2012-07-11 Thread Eric in San Diego
at all, it must have some knowledge of the PATH. Does (null *sh-env*) then mean 'no changes to the default environment'? On Wednesday, July 11, 2012 3:53:48 PM UTC-7, Michael Klishin wrote: > > Eric in San Diego: > > > That's why I'm hoping there is some way I can

Re: Clojure shell calls results inconsistent with actual shell calls.

2012-07-16 Thread Eric in San Diego
Thanks for everyone's input. I think at this point I've concluded that this is not a clojure problem, but rather something going on with the program I'm calling in the shell. I'm talking to the support community there. In the meantime I've found a work-around. Thanks again for everyone's hel

Logger conflicts

2012-07-23 Thread Eric in San Diego
I'm in the process of upgrading some oldish code, and I'm encountering some compatibility problems with the loggers required by various libraries. See the *appendix* below for my project.clj, which loads a number of libraries and to which I've recently added statements like this: [com.

Re: Logger conflicts

2012-07-24 Thread Eric in San Diego
Thanks for your response. I look forward to trying out your lib. As it happens, my problem seems magically to have vanished on its own, and I can't think of anything I did that might have shaken it loose. Gotta love problems that magically fix themselves (until they magically unfix themselve

Unexpected behavior with satisfies?

2011-10-15 Thread Eric in San Diego
Hi all - I'm experiencing some unexpected behavior with protocols. Stripping out extraneous details... ; (ns my.ns1 ...) (defprotocol pro-1 ...) (deftype T1 [...] pro-1 ...) (defn fun [p] ^{:pre [(satisfies? pro-1 p) ] } ...) Then in another file: (

Re: Unexpected behavior with satisfies?

2011-10-16 Thread Eric in San Diego
Update: This appears to have been the product of a funky state. Restarting with a new swank service seems to have removed the problem. - e in sd On Oct 15, 8:04 am, Eric in San Diego wrote: > Hi all - > > I'm experiencing some unexpected behavior with protocols. Stripping &g

Re: Unexpected behavior with satisfies?

2011-10-19 Thread Eric in San Diego
;old" version of pro-1, > while fun will be testing for satisfaction of the "current" version. > > On Oct 15, 8:04 am, Eric in San Diego wrote: > > > > > > > > > Hi all - > > > I'm experiencing some unexpected behavior with prot

Type hints for ^map migrating from 1.2 to 1.3

2011-12-06 Thread Eric in San Diego
I'm migrating some code from 1.2 to 1.3, and one of the things I've encountered is that it no longer accepts ^map as a type hint. It's happy if I use ^clojure.lang.PersistentArrayMap, but that's quite a mouthful. Is there a more compact abbreviation I can use? Where are such things documented? T