Re: XPATH/XSLT like access to Clojure data structures?
Thanks. But I'm looking for something that may (a) clojure.walk a clojure data structure (b) let me use clojure.match rules to say what I'm interested in (like xpath does) and (c) use zippers to 'mutate'. - Henrik -- 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.
Is this the right way to prevent repetitive code
I need some things that are almost the same. I solved that in this way: (def search-fields [ [Search Quotes (Case Independent) #(show-search-quotes %)] [Search Quotes Not (Case Independent) #(show-search-quotes-not %)] [Search Quotes Word Bounderies #(show-search-quotes-word-boundary %)] [Search Quotes Begin (Case Independent) #(show-search-quotes-begin %)] [Search Quotes End (Case Independent) #(show-search-quotes-end %)] [Search Quotes Java Regular Expression #(show-search-quotes-java-regex %)] [Search Quotes Java Regular Expression Not #(show-search-quotes-java-regex %)] ]) (dotimes [i (count search-fields)] (let [ description (nth (nth search-fields i) 0) function(nth (nth search-fields i) 1) ] (grid-bag-layout search-panel :fill GridBagConstraints/HORIZONTAL :ipadx 8 :ipady 4 :gridy i :gridx 0 ^JLabel (label description) :gridx 1 ^JTextField (text :columns 40 :listen [:action (fn [e] (let [ search-str (text e) ] (when (not (empty? search-str)) (function search-str ] Is that the correct way, or can it be done better? -- Cecil Westerhof -- 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: Is this the right way to prevent repetitive code
You can pass your functions around directly; you don't need to wrap them in #(). That will get rid of most of the rest of the duplication you've got. (def search-fields [ [Search Quotes (Case Independent) show-search-quotes] [Search Quotes Not (Case Independent) show-search-quotes-not] [Search Quotes Word Bounderies show-search-quotes-word-boundary] [Search Quotes Begin (Case Independent) show-search-quotes-begin] [Search Quotes End (Case Independent) show-search-quotes-end] [Search Quotes Java Regular Expression show-search-quotes-java-regex] [Search Quotes Java Regular Expression Not show-search-quotes-java-regex] ]) Also, please consider doseq instead of dotimes. (doseq [[description function] search-fields] (grid-bag-layout search-panel :fill GridBagConstraints/HORIZONTAL :ipadx 8 ...)) You could extract the doseq into a var-args function, then call it with the items like so: (def-grids [Search Quotes (Case Independent) show-search-quotes] [Search Quotes Not (Case Independent) show-search-quotes-not] [Search Quotes Word Bounderies show-search-quotes-word-boundary] [Search Quotes Begin (Case Independent) show-search-quotes-begin] [Search Quotes End (Case Independent) show-search-quotes-end] [Search Quotes Java Regular Expression show-search-quotes-java-regex] [Search Quotes Java Regular Expression Not show-search-quotes-java-regex]) Chris On Feb 28, 2015 4:50 AM, Cecil Westerhof cldwester...@gmail.com wrote: I need some things that are almost the same. I solved that in this way: (def search-fields [ [Search Quotes (Case Independent) #(show-search-quotes %)] [Search Quotes Not (Case Independent) #(show-search-quotes-not %)] [Search Quotes Word Bounderies #(show-search-quotes-word-boundary %)] [Search Quotes Begin (Case Independent) #(show-search-quotes-begin %)] [Search Quotes End (Case Independent) #(show-search-quotes-end %)] [Search Quotes Java Regular Expression #(show-search-quotes-java-regex %)] [Search Quotes Java Regular Expression Not #(show-search-quotes-java-regex %)] ]) (dotimes [i (count search-fields)] (let [ description (nth (nth search-fields i) 0) function(nth (nth search-fields i) 1) ] (grid-bag-layout search-panel :fill GridBagConstraints/HORIZONTAL :ipadx 8 :ipady 4 :gridy i :gridx 0 ^JLabel (label description) :gridx 1 ^JTextField (text :columns 40 :listen [:action (fn [e] (let [ search-str (text e) ] (when (not (empty? search-str)) (function search-str ] Is that the correct way, or can it be done better? -- Cecil Westerhof -- 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 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.
:reload does not always work correctly in leiningen
I discovered: (require 'project.core :reload) Very handy indeed and a big time saver. But it does not always work correctly. At a certain moment I got strange results. An exit and a new 'lein repl' solved the problems. -- Cecil Westerhof -- 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: Is Caribou Dormant ?
On 27/02/2015 07:26, Sven Richter wrote: Hi, Please have a look at: https://github.com/sveri/closp/ and tell me what you are missing. You might as well open feature / pull requests and I will consider adding them. Best Regards, Sven Great work, Sven. Just what I was looking for. Next - THE BOOK :) gvim -- 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: Is this the right way to prevent repetitive code
You might wonder how to get 'i' if you remove the dotimes. Here is one way: (doall (map-indexed (fn [i [description f]] ...) search-fields)) doall is to force side-effects, assuming you need to do that. And like Chris said above, you might consider moving the anonymous fn into an explicit function defined with defn. marc On Sat, Feb 28, 2015 at 10:43 AM, Chris Freeman cwfree...@gmail.com wrote: You can pass your functions around directly; you don't need to wrap them in #(). That will get rid of most of the rest of the duplication you've got. (def search-fields [ [Search Quotes (Case Independent) show-search-quotes] [Search Quotes Not (Case Independent) show-search-quotes-not] [Search Quotes Word Bounderies show-search-quotes-word-boundary] [Search Quotes Begin (Case Independent) show-search-quotes-begin] [Search Quotes End (Case Independent) show-search-quotes-end] [Search Quotes Java Regular Expression show-search-quotes-java-regex] [Search Quotes Java Regular Expression Not show-search-quotes-java-regex] ]) Also, please consider doseq instead of dotimes. (doseq [[description function] search-fields] (grid-bag-layout search-panel :fill GridBagConstraints/HORIZONTAL :ipadx 8 ...)) You could extract the doseq into a var-args function, then call it with the items like so: (def-grids [Search Quotes (Case Independent) show-search-quotes] [Search Quotes Not (Case Independent) show-search-quotes-not] [Search Quotes Word Bounderies show-search-quotes-word-boundary] [Search Quotes Begin (Case Independent) show-search-quotes-begin] [Search Quotes End (Case Independent) show-search-quotes-end] [Search Quotes Java Regular Expression show-search-quotes-java-regex] [Search Quotes Java Regular Expression Not show-search-quotes-java-regex]) Chris On Feb 28, 2015 4:50 AM, Cecil Westerhof cldwester...@gmail.com wrote: I need some things that are almost the same. I solved that in this way: (def search-fields [ [Search Quotes (Case Independent) #(show-search-quotes %)] [Search Quotes Not (Case Independent) #(show-search-quotes-not %)] [Search Quotes Word Bounderies #(show-search-quotes-word-boundary %)] [Search Quotes Begin (Case Independent) #(show-search-quotes-begin %)] [Search Quotes End (Case Independent) #(show-search-quotes-end %)] [Search Quotes Java Regular Expression #(show-search-quotes-java-regex %)] [Search Quotes Java Regular Expression Not #(show-search-quotes-java-regex %)] ]) (dotimes [i (count search-fields)] (let [ description (nth (nth search-fields i) 0) function(nth (nth search-fields i) 1) ] (grid-bag-layout search-panel :fill GridBagConstraints/HORIZONTAL :ipadx 8 :ipady 4 :gridy i :gridx 0 ^JLabel (label description) :gridx 1 ^JTextField (text :columns 40 :listen [:action (fn [e] (let [ search-str (text e) ] (when (not (empty? search-str)) (function search-str ] Is that the correct way, or can it be done better? -- Cecil Westerhof -- 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 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
XPATH/XSLT like access to Clojure data structures?
instar and balagan are two libs that are in this space. ive been looking for something like youre describing as well - i think something like xslt would be wondrous. -- 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: How do I depend on clojure 1.7.0-master-SNAPSHOT?
Hmm, I've noticed a file named resolver-status.properties is created in ~/.m2/repository/org/clojure/clojure/1.7.0-master-SNAPSHOT with the following contents: #NOTE: This is an internal implementation file, its format can be changed without prior notice. #Sat Feb 28 21:45:36 GMT 2015 maven-metadata-snapshots.xml/default-https\://oss.sonatype.org/content/repositories/snapshots/.lastUpdated=1425159936364 maven-metadata-clojars.xml.error= maven-metadata-snapshots.xml.error=Could not transfer metadata org.clojure\:clojure\:1.7.0-master-SNAPSHOT/maven-metadata.xml from/to snapshots (https\://oss.sonatype.org/content/repositories/snapshots/)\: Checksum validation failed, expected 5c88ee9a5d32a33ad7d16246ec3363fc98631b0a but is c20a0181e802635cf0d33d59a244204188d5e1a5 maven-metadata-clojars.xml.lastUpdated=1425159935986 If I download https://oss.sonatype.org/content/repositories/snapshots/org/clojure/clojure/1.7.0-master-SNAPSHOT/maven-metadata.xml and run openssl sha1 maven-metadata.xml, I get: SHA1(maven-metadata.xml)= c20a0181e802635cf0d33d59a244204188d5e1a5 But https://oss.sonatype.org/content/repositories/snapshots/org/clojure/clojure/1.7.0-master-SNAPSHOT/maven-metadata.xml.sha1 contains: 5c88ee9a5d32a33ad7d16246ec3363fc98631b0a Which makes it seem like an issue with the deployed artifact/metadata? I'm not really sure why it's working for you but not me! Thanks, Michael On Saturday, 28 February 2015 00:18:34 UTC, Sean Corfield wrote: On Feb 27, 2015, at 3:30 PM, Michael Griffiths mikeygr...@gmail.com javascript: wrote: Sean, thanks - but does it still work for you if you remove ~/.m2/ (or just remove 1.7.0-master-SNAPSHOT from here)? I've tried with the trailing slash and am still having no luck (both locally and on Travis CI). Yes — just to test I blew away my ~/.m2/repository/org tree and re-ran my build and Leiningen pulled down the latest snapshot (along with hundreds of other org.* dependencies): [exec] Retrieving org/clojure/clojure/1.7.0-master-SNAPSHOT/clojure-1.7.0-master-20150220.180325-29.pom from sonatype [exec] Retrieving org/clojure/clojure/1.7.0-master-SNAPSHOT/clojure-1.7.0-master-20150220.180325-29.jar from sonatype Sean Corfield -- (904) 302-SEAN An Architect's View -- http://corfield.org/ Perfection is the enemy of the good. -- Gustave Flaubert, French realist novelist (1821-1880) -- 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: XPATH/XSLT like access to Clojure data structures?
Sorry, I misread your email. -- 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: Is this the right way to prevent repetitive code
2015-02-28 16:43 GMT+01:00 Chris Freeman cwfree...@gmail.com: You can pass your functions around directly; you don't need to wrap them in #(). That will get rid of most of the rest of the duplication you've got. That did not work in the beginning, but that probably had to do that I was first using a list instead of a vector. (I spend quite some time getting it to work. But I learned from it.) Also, please consider doseq instead of dotimes. (doseq [[description function] search-fields] (grid-bag-layout search-panel :fill GridBagConstraints/HORIZONTAL :ipadx 8 ...)) That does not work because I need the i. But with the comment from Marc I made the following. In a let I have (not in a def of-course): search-fields [ [Search Quotes (Case Independent) show-search-quotes] [Search Quotes Not (Case Independent) show-search-quotes-not] [Search Quotes Word Bounderies show-search-quotes-word-boundary] [Search Quotes Begin (Case Independent) show-search-quotes-begin] [Search Quotes End (Case Independent) show-search-quotes-end] [Search Quotes Java Regular Expression show-search-quotes-java-regex] [Search Quotes Java Regular Expression Not show-search-quotes-java-regex-not] [nil nil] [Search Authors (Case Independent) show-search-authors] ] The code (it is extended to have also an empty line): (doall (map-indexed (fn [i [description function]] (if (nil? description) (grid-bag-layout search-panel :fill GridBagConstraints/HORIZONTAL :ipadx 8 :ipady 4 :gridy i :gridx 0 ^JLabel (label )) (grid-bag-layout search-panel :fill GridBagConstraints/HORIZONTAL :ipadx 8 :ipady 4 :gridy i :gridx 0 ^JLabel (label description) :gridx 1 ^JTextField (text :columns 40 :listen [:action (fn [e] (let [ search-str (text e) ] (when (not (empty? search-str)) (function search-str ] search-fields)) The only 'problem' is that there is a little duplication of code, but I can live with that I think. In the attachment is a screendump of the frame as it has become. You could extract the doseq into a var-args function, then call it with the items like so: (def-grids [Search Quotes (Case Independent) show-search-quotes] [Search Quotes Not (Case Independent) show-search-quotes-not] [Search Quotes Word Bounderies show-search-quotes-word-boundary] [Search Quotes Begin (Case Independent) show-search-quotes-begin] [Search Quotes End (Case Independent) show-search-quotes-end] [Search Quotes Java Regular Expression show-search-quotes-java-regex] [Search Quotes Java Regular Expression Not show-search-quotes-java-regex]) I do not understand what you mean by this. On Feb 28, 2015 4:50 AM, Cecil Westerhof cldwester...@gmail.com wrote: I need some things that are almost the same. I solved that in this way: (def search-fields [ [Search Quotes (Case Independent) #(show-search-quotes %)] [Search Quotes Not (Case Independent) #(show-search-quotes-not %)] [Search Quotes Word Bounderies #(show-search-quotes-word-boundary %)] [Search Quotes Begin (Case Independent) #(show-search-quotes-begin %)] [Search Quotes End (Case Independent) #(show-search-quotes-end %)] [Search Quotes Java Regular Expression #(show-search-quotes-java-regex %)] [Search Quotes Java Regular Expression Not #(show-search-quotes-java-regex %)] ]) (dotimes [i (count search-fields)] (let [ description (nth (nth search-fields i) 0) function(nth (nth search-fields i) 1) ] (grid-bag-layout search-panel :fill GridBagConstraints/HORIZONTAL :ipadx 8 :ipady 4 :gridy i :gridx 0 ^JLabel (label description) :gridx 1 ^JTextField (text :columns 40 :listen [:action (fn [e] (let [ search-str (text e) ] (when (not (empty? search-str)) (function search-str ] Is that the correct way,
[ANN] Understanding the Persistent Vector
Hello fellow Clojurians, I am happy to announce that I have finished my blogpost series on the persistent vector. It consists of five parts: 1. The basic algorithms http://hypirion.com/musings/understanding-persistent-vector-pt-1 2. Indexing http://hypirion.com/musings/understanding-persistent-vector-pt-2 3. The tail optimisation http://hypirion.com/musings/understanding-persistent-vector-pt-3 4. Transients http://hypirion.com/musings/understanding-clojure-transients 5. Performance http://hypirion.com/musings/persistent-vector-performance-summarised (which is a summary of this detailed blogpost http://hypirion.com/musings/persistent-vector-performance) I hope this will help you to get a good understanding of how the algorithms on the data structure work, how the optimisations work, and how efficient it is on the JVM. Constructive criticism, both positive and negative, is appreciated. Enjoy! (NB: I haven't gotten around to fix the illustrations in part 3, so unfortunately it will be a bit hard to read if you print it out in grayscale. It's on my todo-list.) -- Jean Niklas L'orange -- 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: Is Caribou Dormant ?
I'm one of the core devs of the Caribou project. Caribou has been less actively developed, but I still use it frequently. We previously were funded to work on Caribou, but the company funding us decided to discontinue using Clojure (except for supporting some clients where Clojure code was deployed). Now we've all moved on to other employment situations, and I'm the only one actively using Caribou out of the core team. Bug reports and pull requests will be acknowledged, and likely acted on. There has been some work quite recently on polaris, our routing lib. On Saturday, February 28, 2015 at 9:11:52 AM UTC-8, Sven Richter wrote: I am glad you like it. It is still pretty young, so like I said, just open issues if you need more. Best Regards, Sven Am Samstag, 28. Februar 2015 16:22:41 UTC+1 schrieb g vim: On 27/02/2015 07:26, Sven Richter wrote: Hi, Please have a look at: https://github.com/sveri/closp/ and tell me what you are missing. You might as well open feature / pull requests and I will consider adding them. Best Regards, Sven Great work, Sven. Just what I was looking for. Next - THE BOOK :) gvim -- 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: :reload does not always work correctly in leiningen
does not always work correctly in what context? In the REPL, `(require '[my.ns :as mine] :reload-all)` should work. `defonce` and `defmulti` might also be causing confusion. You could also look into `clojure.tools.namespace.repl` (https://github.com/clojure/tools.namespace#reloading-code-usage). On Saturday, February 28, 2015 at 9:25:56 AM UTC-5, Cecil Westerhof wrote: I discovered: (require 'project.core :reload) Very handy indeed and a big time saver. But it does not always work correctly. At a certain moment I got strange results. An exit and a new 'lein repl' solved the problems. -- Cecil Westerhof -- 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: :reload does not always work correctly in leiningen
The :reload directive re-evaluated the namespace, but does not remove any existing definitions, or reload any dependent namespaces. This may be the cause of your strange results. The tools.namespace library https://github.com/clojure/tools.namespace contains a refresh function that will clear and reload your namespaces from scratch. This doesn't take into account things like background threads, but is generally more reliable that the :reload directive when working in a REPL. - James On 28 February 2015 at 14:25, Cecil Westerhof cldwester...@gmail.com wrote: I discovered: (require 'project.core :reload) Very handy indeed and a big time saver. But it does not always work correctly. At a certain moment I got strange results. An exit and a new 'lein repl' solved the problems. -- Cecil Westerhof -- 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 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: Is Caribou Dormant ?
I am glad you like it. It is still pretty young, so like I said, just open issues if you need more. Best Regards, Sven Am Samstag, 28. Februar 2015 16:22:41 UTC+1 schrieb g vim: On 27/02/2015 07:26, Sven Richter wrote: Hi, Please have a look at: https://github.com/sveri/closp/ and tell me what you are missing. You might as well open feature / pull requests and I will consider adding them. Best Regards, Sven Great work, Sven. Just what I was looking for. Next - THE BOOK :) gvim -- 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: :reload does not always work correctly in leiningen
2015-02-28 17:26 GMT+01:00 Sam Raker sam.ra...@gmail.com: does not always work correctly in what context? One time when I did the reload my forms got an empty area around them. After an exit and a new start everything was OK again. I use it since today, so I do not know if it is a gremlin or a real problem. I just keep using it and if I get strange results I just have to remember to exit and start again. If I need to restart once every four hours, it still is a good improvement. I just thought to mention it: if a lot of people would reply with: yes, I have the same problem, then we would know that something was broken. For the moment I think it was a gremlin and not a real problem. On Saturday, February 28, 2015 at 9:25:56 AM UTC-5, Cecil Westerhof wrote: I discovered: (require 'project.core :reload) Very handy indeed and a big time saver. But it does not always work correctly. At a certain moment I got strange results. An exit and a new 'lein repl' solved the problems. -- Cecil Westerhof -- 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: Is this the right way to prevent repetitive code
2015-02-28 16:51 GMT+01:00 Marc Limotte mslimo...@gmail.com: You might wonder how to get 'i' if you remove the dotimes. Here is one way: (doall (map-indexed (fn [i [description f]] ...) search-fields)) Done, see other reply. -- Cecil Westerhof -- 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.
