Re: [ClojureScript] Re: ANN: Om 0.8.6, Hello CLJSJS
Let's go with `data` then. I posted the rewrite to Figwheel. Please take a look. https://github.com/swannodette/om/wiki/Basic-Tutorial On Monday, February 2, 2015 at 2:02:35 PM UTC+1, Dan Kersten wrote: I personally like data. om-tools also calls it data. On 2 February 2015 at 12:55, Khalid Jebbari khalid@gmail.com javascript: wrote: Indeed, data is better than app. Khalid aka DjebbZ @Dj3bbZ On Mon, Feb 2, 2015 at 10:49 AM, Sebastian Bensusan sbe...@gmail.com javascript: wrote: Thanks Khalid, The way I see it, Om has three concepts regarding state: 1. The global state defined with atom. Named `app-state` 2. The cursor passed to each component with the relevant parts of the global state. Named `app` 3. Local state of each component, initialized in `IInitState` and manipulated with `(set-state! owner korks v)` and `(get-state owner)`. It is a property of the owner object so it is not directly referenced. I agree that `app` is ambiguous for 2 but I wouldn't like to call it `app-state` nor `state` since those could also be confused with 1 and 3. Nothing better than `cursor` or `data` comes to mind. Some other parts of the Documentation (the Example in https://github.com/swannodette/om) use `data` and I think it works even if it is a meaningless term for a fn argument. If you agree and nobody raises objections I'll change `app` to `data`. Sebastian -- Note that posts from new members are moderated - please be patient with your first post. --- You received this message because you are subscribed to a topic in the Google Groups ClojureScript group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/clojurescript/bruQ9os5wmM/unsubscribe. To unsubscribe from this group and all its topics, send an email to clojurescrip...@googlegroups.com javascript:. To post to this group, send email to clojur...@googlegroups.com javascript:. Visit this group at http://groups.google.com/group/clojurescript. -- Note that posts from new members are moderated - please be patient with your first post. --- You received this message because you are subscribed to the Google Groups ClojureScript group. To unsubscribe from this group and stop receiving emails from it, send an email to clojurescrip...@googlegroups.com javascript:. To post to this group, send email to clojur...@googlegroups.com javascript:. Visit this group at http://groups.google.com/group/clojurescript. -- 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 unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups Clojure group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [ClojureScript] Re: ANN: Om 0.8.6, Hello CLJSJS
I personally like data. om-tools also calls it data. On 2 February 2015 at 12:55, Khalid Jebbari khalid.jebb...@gmail.com wrote: Indeed, data is better than app. Khalid aka DjebbZ @Dj3bbZ On Mon, Feb 2, 2015 at 10:49 AM, Sebastian Bensusan sbe...@gmail.com wrote: Thanks Khalid, The way I see it, Om has three concepts regarding state: 1. The global state defined with atom. Named `app-state` 2. The cursor passed to each component with the relevant parts of the global state. Named `app` 3. Local state of each component, initialized in `IInitState` and manipulated with `(set-state! owner korks v)` and `(get-state owner)`. It is a property of the owner object so it is not directly referenced. I agree that `app` is ambiguous for 2 but I wouldn't like to call it `app-state` nor `state` since those could also be confused with 1 and 3. Nothing better than `cursor` or `data` comes to mind. Some other parts of the Documentation (the Example in https://github.com/swannodette/om) use `data` and I think it works even if it is a meaningless term for a fn argument. If you agree and nobody raises objections I'll change `app` to `data`. Sebastian -- Note that posts from new members are moderated - please be patient with your first post. --- You received this message because you are subscribed to a topic in the Google Groups ClojureScript group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/clojurescript/bruQ9os5wmM/unsubscribe. To unsubscribe from this group and all its topics, send an email to clojurescript+unsubscr...@googlegroups.com. To post to this group, send email to clojurescr...@googlegroups.com. Visit this group at http://groups.google.com/group/clojurescript. -- Note that posts from new members are moderated - please be patient with your first post. --- You received this message because you are subscribed to the Google Groups ClojureScript group. To unsubscribe from this group and stop receiving emails from it, send an email to clojurescript+unsubscr...@googlegroups.com. To post to this group, send email to clojurescr...@googlegroups.com. Visit this group at http://groups.google.com/group/clojurescript. -- 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 unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups Clojure group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [ClojureScript] Re: ANN: Om 0.8.6, Hello CLJSJS
Indeed, data is better than app. Khalid aka DjebbZ @Dj3bbZ On Mon, Feb 2, 2015 at 10:49 AM, Sebastian Bensusan sbe...@gmail.com wrote: Thanks Khalid, The way I see it, Om has three concepts regarding state: 1. The global state defined with atom. Named `app-state` 2. The cursor passed to each component with the relevant parts of the global state. Named `app` 3. Local state of each component, initialized in `IInitState` and manipulated with `(set-state! owner korks v)` and `(get-state owner)`. It is a property of the owner object so it is not directly referenced. I agree that `app` is ambiguous for 2 but I wouldn't like to call it `app-state` nor `state` since those could also be confused with 1 and 3. Nothing better than `cursor` or `data` comes to mind. Some other parts of the Documentation (the Example in https://github.com/swannodette/om) use `data` and I think it works even if it is a meaningless term for a fn argument. If you agree and nobody raises objections I'll change `app` to `data`. Sebastian -- Note that posts from new members are moderated - please be patient with your first post. --- You received this message because you are subscribed to a topic in the Google Groups ClojureScript group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/clojurescript/bruQ9os5wmM/unsubscribe. To unsubscribe from this group and all its topics, send an email to clojurescript+unsubscr...@googlegroups.com. To post to this group, send email to clojurescr...@googlegroups.com. Visit this group at http://groups.google.com/group/clojurescript. -- 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 unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups Clojure group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [ClojureScript] Re: ANN: Om 0.8.6, Hello CLJSJS
Sure, I'll explore Figwheel's new REPL and add that instead. What about adding/configuring Figwheel? Should it be step by step inside the tutorial, from mies-om to mies-om + Figwheel? Or it should just start with a ready to go template mies-om-wheel? Thanks Sebastian Bensusan On Saturday, January 31, 2015 at 1:26:34 AM UTC+1, David Nolen wrote: I would prefer just Figwheel. Relying only on Figwheel also means you could probably go out with an updated tutorial much sooner. Thanks, David On Fri, Jan 30, 2015 at 4:10 PM, Sebastian Bensusan sbe...@gmail.com wrote: Hi David and Dan, I edited Om's Basic Tutorial (https://github.com/swannodette/om/wiki/Basic-Tutorial) to be used with Chestnut. Most of the work (not much!) was changing evaluate in LightTable to save in your text editor. I don't know what the procedure is for updating a Wiki and having this conversation, should I open an issue on Om? I have it as a standalone repo in case someones wants to propose a change or make a pull request: https://github.com/bensu/basic-om-tut Two issues: 1. Chestnut 0.6.0 (current stable version) uses Om 0.7.3 and I needed to deref a cursor inside a go loop in order for things to work. See https://github.com/swannodette/om/issues/315 and https://github.com/swannodette/om/commit/92a3e0cf698769fb59bb3744faddaea40b37412d. Om version is bumped to 0.8.3 beta in v0.7.0-SNAPSHOT-20141226 2. Chestnut's 0.6.0 doesn't reload the index.html (not on save, not on refresh). The whole process needs to be restarted. See: https://github.com/plexus/chestnut/issues/84 This was addressed in v0.7.0-SNAPSHOT-20141207. I would wait until Chestnut 0.7.0 stable is published in Clojars before adding this tutorial to the Om Wiki. Otherwise, if you feel the extra dependency on Chestnut is also too much, I'll fork mies-om and add Figwheel there for the tutorial. After revising this work, I'll move on to the next tutorial. Best Sebastian Bensusan On Tuesday, January 27, 2015 at 5:25:09 PM UTC+1, David Nolen wrote: I think expecting every last thing to work especially from third parties who may be wisely lagging behind is unlikely at least for the near future. I haven't kept up with Light Table and what issues it may have. Now is probably a good time to remove the Light Table centric nature of the Om tutorials and switch to a Figwheel based thing that doesn't require anything more than your text editor of choice. The wiki has always been community editable and I would love to see people push it forward especially with stuff like this. I will have less time for such things as I focus more on Om core and ClojureScript enhancements. David On Tue, Jan 27, 2015 at 10:46 AM, Olav Nymoen ol...@comoyo.com wrote: Just testing clojurescript out so many possible pitfalls on my side here. Does the new javascript externals stuff break lighttables live external browser functionality? Following the basic intro tutorial I cannot get live updates to work. The mies-om om-tut is based on 0.8.4 , and it cannot reference com.facebook.react, while 0.8.6 cannot find cljsjs.react. It compiles nicely with lein, but I can't seem to get the lighttable live REPL stuff to work. Olav On Tuesday, January 27, 2015 at 1:57:19 AM UTC+1, David Nolen wrote: The only significant change is that Om now relies on the cljsjs.react artifact instead of the one I maintained myself. cljsjs.react has the benefit that usage of React with addons instead of plain React may be configured via Maven in your pom.xml or your project.clj. It's exciting to see that we are already reaping the benefits of :foreign-libs and Maven over existing JavaScript solutions for managing dependencies. This release also includes a fix for a very subtle set-state! bug discovered by Brenton Ashworth. Feedback welcome! https://github.com/swannodette/om David -- Note that posts from new members are moderated - please be patient with your first post. --- You received this message because you are subscribed to the Google Groups ClojureScript group. To unsubscribe from this group and stop receiving emails from it, send an email to clojurescrip...@googlegroups.com. To post to this group, send email to clojur...@googlegroups.com. Visit this group at http://groups.google.com/group/clojurescript. -- You received this message because you are subscribed to the Google Groups Clojure group. To post to this group, send email to clo...@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+u...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
Re: [ClojureScript] Re: ANN: Om 0.8.6, Hello CLJSJS
Hi David and Dan, I edited Om's Basic Tutorial (https://github.com/swannodette/om/wiki/Basic-Tutorial) to be used with Chestnut. Most of the work (not much!) was changing evaluate in LightTable to save in your text editor. I don't know what the procedure is for updating a Wiki and having this conversation, *should I open an issue on Om?* I have it as a standalone repo in case someones wants to propose a change or make a pull request: https://github.com/bensu/basic-om-tut Two issues: 1. Chestnut 0.6.0 (current stable version) uses Om 0.7.3 and I needed to deref a cursor inside a go loop in order for things to work. See https://github.com/swannodette/om/issues/315 and https://github.com/swannodette/om/commit/92a3e0cf698769fb59bb3744faddaea40b37412d. Om version is bumped to 0.8.3 beta in v0.7.0-SNAPSHOT-20141226 2. Chestnut's 0.6.0 doesn't reload the index.html (not on save, not on refresh). The whole process needs to be restarted. See: https://github.com/plexus/chestnut/issues/84 This was addressed in v0.7.0-SNAPSHOT-20141207. *I would wait until Chestnut 0.7.0 *stable is published in Clojars before adding this tutorial to the Om Wiki. Otherwise, if you feel the extra dependency on Chestnut is also too much, I'll fork mies-om and add Figwheel there for the tutorial. After revising this work, I'll move on to the next tutorial. Best Sebastian Bensusan On Tuesday, January 27, 2015 at 5:25:09 PM UTC+1, David Nolen wrote: I think expecting every last thing to work especially from third parties who may be wisely lagging behind is unlikely at least for the near future. I haven't kept up with Light Table and what issues it may have. Now is probably a good time to remove the Light Table centric nature of the Om tutorials and switch to a Figwheel based thing that doesn't require anything more than your text editor of choice. The wiki has always been community editable and I would love to see people push it forward especially with stuff like this. I will have less time for such things as I focus more on Om core and ClojureScript enhancements. David On Tue, Jan 27, 2015 at 10:46 AM, Olav Nymoen ol...@comoyo.com javascript: wrote: Just testing clojurescript out so many possible pitfalls on my side here. Does the new javascript externals stuff break lighttables live external browser functionality? Following the basic intro tutorial I cannot get live updates to work. The mies-om om-tut is based on 0.8.4 , and it cannot reference com.facebook.react, while 0.8.6 cannot find cljsjs.react. It compiles nicely with lein, but I can't seem to get the lighttable live REPL stuff to work. Olav On Tuesday, January 27, 2015 at 1:57:19 AM UTC+1, David Nolen wrote: The only significant change is that Om now relies on the cljsjs.react artifact instead of the one I maintained myself. cljsjs.react has the benefit that usage of React with addons instead of plain React may be configured via Maven in your pom.xml or your project.clj. It's exciting to see that we are already reaping the benefits of :foreign-libs and Maven over existing JavaScript solutions for managing dependencies. This release also includes a fix for a very subtle set-state! bug discovered by Brenton Ashworth. Feedback welcome! https://github.com/swannodette/om David -- Note that posts from new members are moderated - please be patient with your first post. --- You received this message because you are subscribed to the Google Groups ClojureScript group. To unsubscribe from this group and stop receiving emails from it, send an email to clojurescrip...@googlegroups.com javascript:. To post to this group, send email to clojur...@googlegroups.com javascript:. Visit this group at http://groups.google.com/group/clojurescript. -- 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 unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups Clojure group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [ClojureScript] Re: ANN: Om 0.8.6, Hello CLJSJS
I would prefer just Figwheel. Relying only on Figwheel also means you could probably go out with an updated tutorial much sooner. Thanks, David On Fri, Jan 30, 2015 at 4:10 PM, Sebastian Bensusan sbe...@gmail.com wrote: Hi David and Dan, I edited Om's Basic Tutorial ( https://github.com/swannodette/om/wiki/Basic-Tutorial) to be used with Chestnut. Most of the work (not much!) was changing evaluate in LightTable to save in your text editor. I don't know what the procedure is for updating a Wiki and having this conversation, *should I open an issue on Om?* I have it as a standalone repo in case someones wants to propose a change or make a pull request: https://github.com/bensu/basic-om-tut Two issues: 1. Chestnut 0.6.0 (current stable version) uses Om 0.7.3 and I needed to deref a cursor inside a go loop in order for things to work. See https://github.com/swannodette/om/issues/315 and https://github.com/swannodette/om/commit/92a3e0cf698769fb59bb3744faddaea40b37412d. Om version is bumped to 0.8.3 beta in v0.7.0-SNAPSHOT-20141226 2. Chestnut's 0.6.0 doesn't reload the index.html (not on save, not on refresh). The whole process needs to be restarted. See: https://github.com/plexus/chestnut/issues/84 This was addressed in v0.7.0-SNAPSHOT-20141207. *I would wait until Chestnut 0.7.0 *stable is published in Clojars before adding this tutorial to the Om Wiki. Otherwise, if you feel the extra dependency on Chestnut is also too much, I'll fork mies-om and add Figwheel there for the tutorial. After revising this work, I'll move on to the next tutorial. Best Sebastian Bensusan On Tuesday, January 27, 2015 at 5:25:09 PM UTC+1, David Nolen wrote: I think expecting every last thing to work especially from third parties who may be wisely lagging behind is unlikely at least for the near future. I haven't kept up with Light Table and what issues it may have. Now is probably a good time to remove the Light Table centric nature of the Om tutorials and switch to a Figwheel based thing that doesn't require anything more than your text editor of choice. The wiki has always been community editable and I would love to see people push it forward especially with stuff like this. I will have less time for such things as I focus more on Om core and ClojureScript enhancements. David On Tue, Jan 27, 2015 at 10:46 AM, Olav Nymoen ol...@comoyo.com wrote: Just testing clojurescript out so many possible pitfalls on my side here. Does the new javascript externals stuff break lighttables live external browser functionality? Following the basic intro tutorial I cannot get live updates to work. The mies-om om-tut is based on 0.8.4 , and it cannot reference com.facebook.react, while 0.8.6 cannot find cljsjs.react. It compiles nicely with lein, but I can't seem to get the lighttable live REPL stuff to work. Olav On Tuesday, January 27, 2015 at 1:57:19 AM UTC+1, David Nolen wrote: The only significant change is that Om now relies on the cljsjs.react artifact instead of the one I maintained myself. cljsjs.react has the benefit that usage of React with addons instead of plain React may be configured via Maven in your pom.xml or your project.clj. It's exciting to see that we are already reaping the benefits of :foreign-libs and Maven over existing JavaScript solutions for managing dependencies. This release also includes a fix for a very subtle set-state! bug discovered by Brenton Ashworth. Feedback welcome! https://github.com/swannodette/om David -- Note that posts from new members are moderated - please be patient with your first post. --- You received this message because you are subscribed to the Google Groups ClojureScript group. To unsubscribe from this group and stop receiving emails from it, send an email to clojurescrip...@googlegroups.com. To post to this group, send email to clojur...@googlegroups.com. Visit this group at http://groups.google.com/group/clojurescript. -- 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 unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups Clojure group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- 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 unsubscribe from
Re: [ClojureScript] Re: ANN: Om 0.8.6, Hello CLJSJS
A figwheel-based tutorial would be fantastic. I don't have an awful lot of time to convert it right now, but if nobody does before I do get time, I'll happily take a stab at it. Will likely be a month or two though. On 27 January 2015 at 16:24, David Nolen dnolen.li...@gmail.com wrote: I think expecting every last thing to work especially from third parties who may be wisely lagging behind is unlikely at least for the near future. I haven't kept up with Light Table and what issues it may have. Now is probably a good time to remove the Light Table centric nature of the Om tutorials and switch to a Figwheel based thing that doesn't require anything more than your text editor of choice. The wiki has always been community editable and I would love to see people push it forward especially with stuff like this. I will have less time for such things as I focus more on Om core and ClojureScript enhancements. David On Tue, Jan 27, 2015 at 10:46 AM, Olav Nymoen o...@comoyo.com wrote: Just testing clojurescript out so many possible pitfalls on my side here. Does the new javascript externals stuff break lighttables live external browser functionality? Following the basic intro tutorial I cannot get live updates to work. The mies-om om-tut is based on 0.8.4 , and it cannot reference com.facebook.react, while 0.8.6 cannot find cljsjs.react. It compiles nicely with lein, but I can't seem to get the lighttable live REPL stuff to work. Olav On Tuesday, January 27, 2015 at 1:57:19 AM UTC+1, David Nolen wrote: The only significant change is that Om now relies on the cljsjs.react artifact instead of the one I maintained myself. cljsjs.react has the benefit that usage of React with addons instead of plain React may be configured via Maven in your pom.xml or your project.clj. It's exciting to see that we are already reaping the benefits of :foreign-libs and Maven over existing JavaScript solutions for managing dependencies. This release also includes a fix for a very subtle set-state! bug discovered by Brenton Ashworth. Feedback welcome! https://github.com/swannodette/om David -- Note that posts from new members are moderated - please be patient with your first post. --- You received this message because you are subscribed to the Google Groups ClojureScript group. To unsubscribe from this group and stop receiving emails from it, send an email to clojurescript+unsubscr...@googlegroups.com. To post to this group, send email to clojurescr...@googlegroups.com. Visit this group at http://groups.google.com/group/clojurescript. -- Note that posts from new members are moderated - please be patient with your first post. --- You received this message because you are subscribed to the Google Groups ClojureScript group. To unsubscribe from this group and stop receiving emails from it, send an email to clojurescript+unsubscr...@googlegroups.com. To post to this group, send email to clojurescr...@googlegroups.com. Visit this group at http://groups.google.com/group/clojurescript. -- 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 unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups Clojure group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [ClojureScript] Re: ANN: Om 0.8.6, Hello CLJSJS
I think expecting every last thing to work especially from third parties who may be wisely lagging behind is unlikely at least for the near future. I haven't kept up with Light Table and what issues it may have. Now is probably a good time to remove the Light Table centric nature of the Om tutorials and switch to a Figwheel based thing that doesn't require anything more than your text editor of choice. The wiki has always been community editable and I would love to see people push it forward especially with stuff like this. I will have less time for such things as I focus more on Om core and ClojureScript enhancements. David On Tue, Jan 27, 2015 at 10:46 AM, Olav Nymoen o...@comoyo.com wrote: Just testing clojurescript out so many possible pitfalls on my side here. Does the new javascript externals stuff break lighttables live external browser functionality? Following the basic intro tutorial I cannot get live updates to work. The mies-om om-tut is based on 0.8.4 , and it cannot reference com.facebook.react, while 0.8.6 cannot find cljsjs.react. It compiles nicely with lein, but I can't seem to get the lighttable live REPL stuff to work. Olav On Tuesday, January 27, 2015 at 1:57:19 AM UTC+1, David Nolen wrote: The only significant change is that Om now relies on the cljsjs.react artifact instead of the one I maintained myself. cljsjs.react has the benefit that usage of React with addons instead of plain React may be configured via Maven in your pom.xml or your project.clj. It's exciting to see that we are already reaping the benefits of :foreign-libs and Maven over existing JavaScript solutions for managing dependencies. This release also includes a fix for a very subtle set-state! bug discovered by Brenton Ashworth. Feedback welcome! https://github.com/swannodette/om David -- Note that posts from new members are moderated - please be patient with your first post. --- You received this message because you are subscribed to the Google Groups ClojureScript group. To unsubscribe from this group and stop receiving emails from it, send an email to clojurescript+unsubscr...@googlegroups.com. To post to this group, send email to clojurescr...@googlegroups.com. Visit this group at http://groups.google.com/group/clojurescript. -- 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 unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups Clojure group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
