On Thu, Aug 18, 2011 at 08:05:05PM -0700, dmiller spake thus:
Several comments:
(c) It could be changed to something like CLOJURE_LOAD_PATH instead.
Would that cause a problem for anyone?
-David
+1
-Al
--
-
a l a n d.
On Fri, Aug 19, 2011 at 05:53:59AM -0700, dmiller spake thus:
I would be concerned about this group, if there was any evidence of
existence.
Same here, but even with such evidence I would not be so concerned that
I would not make the change.
This calls to mind Stuart Feldman's explanation as
On Thu, Aug 18, 2011 at 06:40:50PM -0400, Ken Wesson spake thus:
On Thu, Aug 18, 2011 at 4:56 PM, D L lio...@gmail.com wrote:
On Thu, Aug 18, 2011 at 7:34 PM, Ken Wesson kwess...@gmail.com wrote:
On Wed, Aug 17, 2011 at 4:25 PM, Dimitre Liotev lio...@gmail.com wrote:
you can not set
Nothing to add to this discussion, but please *please* realise how
destructive these type of posts are. They significantly increase the noise
and make us all look like muppets.
I respect most of the usual suspects in these threads, but please - let's
keep this on topic.
Alternatively maybe this
On Sun, Aug 21, 2011 at 3:14 AM, Alan D. Salewski salew...@att.net wrote:
That presumption is at least partially incorrect. Native apps (cmd.exe,
for instance) launched from a cygwin bash command prompt can see
environment variables exported by the parent bash process.
I never claimed there
On Thu, Aug 18, 2011 at 11:05 PM, dmiller dmiller2...@gmail.com wrote:
Several comments:
(a) 'clojure.load.path' is not new in 1.3. It's been in the code
since at least May, 2009.
(b) Regarding Dimitre's comment below, I probably did have Java system
properties on my mind at the time. I
I would be concerned about this group, if there was any evidence of
existence.
On Aug 19, 2:59 am, Ken Wesson kwess...@gmail.com wrote:
And, maybe, the ones who have to go and reconfigure everything when
they upgrade ...
--
You received this message because you are subscribed to the Google
On Thu, Aug 18, 2011 at 01:39:21AM -0400, Ken Wesson spake thus:
On Thu, Aug 18, 2011 at 12:32 AM, Alan D. Salewski salew...@att.net wrote:
On Wed, Aug 17, 2011 at 01:47:53PM -0400, Ken Wesson spake thus:
On Wed, Aug 17, 2011 at 9:48 AM, Alan D. Salewski salew...@att.net wrote:
I
On Wed, Aug 17, 2011 at 4:25 PM, Dimitre Liotev lio...@gmail.com wrote:
you can not set and query such a variable in a Bash script.
Code has already been posted to this thread that does exactly that.
--
Protege: What is this seething mass of parentheses?!
Master: Your father's Lisp REPL.
On Thu, Aug 18, 2011 at 7:34 PM, Ken Wesson kwess...@gmail.com wrote:
On Wed, Aug 17, 2011 at 4:25 PM, Dimitre Liotev lio...@gmail.com wrote:
you can not set and query such a variable in a Bash script.
Code has already been posted to this thread that does exactly that.
Let me rephrase
On Thu, Aug 18, 2011 at 4:56 PM, D L lio...@gmail.com wrote:
On Thu, Aug 18, 2011 at 7:34 PM, Ken Wesson kwess...@gmail.com wrote:
On Wed, Aug 17, 2011 at 4:25 PM, Dimitre Liotev lio...@gmail.com wrote:
you can not set and query such a variable in a Bash script.
Code has already been
Several comments:
(a) 'clojure.load.path' is not new in 1.3. It's been in the code
since at least May, 2009.
(b) Regarding Dimitre's comment below, I probably did have Java system
properties on my mind at the time. I guarantee that I was not
thinking of picking Bash-compliant names. I doubt
The . limitation is in bash vars only; they work fine as environment vars:
$ clojure.load.path=whatever command
Some error message I forget
$ env clojure.load.path=whatever command
Sets env var while running command
You should already have env installed. It's pretty useful if you like working
On Tue, Aug 16, 2011 at 01:23:23PM -0400, Ken Wesson spake thus:
On Tue, Aug 16, 2011 at 1:20 AM, Alan D. Salewski salew...@att.net wrote:
On Tue, Aug 16, 2011 at 12:34:39AM -0400, Ken Wesson spake thus:
On Mon, Aug 15, 2011 at 11:13 AM, mrwizard82d1 mrwizard8...@gmail.com
wrote:
I
Thanks, Stephen.
Although I was aware of the env command, I had never needed it before.
I believe this solution will allow me to solve my immediate problem
(running Clojure-CLR with the classpath configured for a specific
project as I do in Java).
On Aug 17, 6:31 am, Stephen Compall
Alan,
Thanks for fighting for *nix folks.
Although I can solve my singular problem using the solution posted by
Stephen, you reminded me of another reason I wrote my question as I
did.
Although I'm not involved, I understand that people continue to work
on the Mono project which provides the
On Wed, Aug 17, 2011 at 9:48 AM, Alan D. Salewski salew...@att.net wrote:
$ /usr/bin/env -- ALJUNK_CRAP1=junk1 ALJUNK.CRAP2=junk2 /bin/bash -c env |
grep ALJU
ALJUNK.CRAP2=junk2
ALJUNK_CRAP1=junk1
You approached the question from the perspective of one just wanting to
launch
On Wed, Aug 17, 2011 at 01:47:53PM -0400, Ken Wesson spake thus:
On Wed, Aug 17, 2011 at 9:48 AM, Alan D. Salewski salew...@att.net wrote:
$ /usr/bin/env -- ALJUNK_CRAP1=junk1 ALJUNK.CRAP2=junk2 /bin/bash -c env
| grep ALJU
ALJUNK.CRAP2=junk2
ALJUNK_CRAP1=junk1
You
On Thu, Aug 18, 2011 at 12:32 AM, Alan D. Salewski salew...@att.net wrote:
On Wed, Aug 17, 2011 at 01:47:53PM -0400, Ken Wesson spake thus:
On Wed, Aug 17, 2011 at 9:48 AM, Alan D. Salewski salew...@att.net wrote:
I approached the question from the perspective of one wanting to invoke
On Tue, Aug 16, 2011 at 12:34:39AM -0400, Ken Wesson spake thus:
On Mon, Aug 15, 2011 at 11:13 AM, mrwizard82d1 mrwizard8...@gmail.com wrote:
I understand that the 1.3 beta plans to add an environment variable
named clojure.load.path to provide a CLASSPATH mechanism for Clojure
on the CLR.
On Tue, Aug 16, 2011 at 1:20 AM, Alan D. Salewski salew...@att.net wrote:
On Tue, Aug 16, 2011 at 12:34:39AM -0400, Ken Wesson spake thus:
On Mon, Aug 15, 2011 at 11:13 AM, mrwizard82d1 mrwizard8...@gmail.com
wrote:
I understand that the 1.3 beta plans to add an environment variable
named
I understand that the 1.3 beta plans to add an environment variable
named clojure.load.path to provide a CLASSPATH mechanism for Clojure
on the CLR.
Although I use Windows, I have installed cygwin because I prefer the
Unix tool set to that provided by Windows. Although a Windows console
allows
On Mon, Aug 15, 2011 at 11:13 AM, mrwizard82d1 mrwizard8...@gmail.com wrote:
I understand that the 1.3 beta plans to add an environment variable
named clojure.load.path to provide a CLASSPATH mechanism for Clojure
on the CLR.
Although I use Windows, I have installed cygwin because I prefer
23 matches
Mail list logo