Re: Are there file watchers that can tell me when a file is done uploading?

2016-12-14 Thread Michael Wood
Yes, exactly. Move and rename are the same thing :) On 14 Dec 2016 08:41, "Torsten Uhlmann" wrote: ... or renames it. That's what browsers do for instance when downloading stuff. Michael Wood schrieb am Mi., 14. Dez. 2016 um 02:25 Uhr: > Another option: Whatever accepts the upload (e.g. a cgi

Re: spurious clojurescript require exception: Namespace does not exist

2016-12-14 Thread dbraun86
Try running this instead: (cljs.core/require '[test.my-greeting :as t]) On Saturday, January 30, 2016 at 7:17:49 PM UTC+2, Gregg Reynolds wrote: > > I'm following the "browser REPL" section in the Clojurescript Quickstart > . Everythi

Re: spurious clojurescript require exception: Namespace does not exist

2016-12-14 Thread David Nolen
`require` only works if your namespace is in a file that respects Java classpath conventions. You may have missed this detail in the way all the Quick Start examples are structured. HTH, David On Sat, Jan 30, 2016 at 12:17 PM, Gregg Reynolds wrote: > I'm following the "browser REPL" section in

apply arguments

2016-12-14 Thread Rafo Ufoun
Hi everyone, I'm new to clojure and I try to understand the apply function. >From the clojure sources, I can see that there are several signatures for this method: with or without additional arguments before the sequence. According to these signatures, we can have 4 arguments MAX before gettin

Re: apply arguments

2016-12-14 Thread James Reeves
Clojure functions can take a collection of arguments by using the "&" symbol. So for instance: (defn print-all [& args] (doseq [arg args] (println arg))) If we run this function with: (print-all "Hello" "World") Then it will print: Hello World But dealing with se

Re: apply arguments

2016-12-14 Thread Rafo Ufoun
Hi, thank you for your response ! I know the '& args' notation, but I thought that this notation expected a collection *after *the &, so in the apply signature, we expect a fn, 4 args and then, a sequence. In this call : (apply + 1 1 1 1 1 1 1 1 1 1 1 [2 3]), the & should be here : (apply + 1

Re: apply arguments

2016-12-14 Thread James Reeves
On 14 December 2016 at 17:38, Rafo Ufoun wrote: > Hi, thank you for your response ! > > I know the '& args' notation, but I thought that this notation expected a > collection *after *the &, so in the apply signature, we expect a fn, 4 > args and then, a sequence. > > In this call : (apply + 1 1 1

Re: apply arguments

2016-12-14 Thread Rafo Ufoun
Ok now I understand ! So this implementation of apply act like this, and all implementations need, as the last arg of all the list, a sequence. Thank you Le mercredi 14 décembre 2016 13:59:40 UTC-5, James Reeves a écrit : > > On 14 December 2016 at 17:38, Rafo Ufoun > wrote: > >> Hi, thank y

Re: Elegant way to do lazy infinite list with custom step

2016-12-14 Thread Ghadi Shayban
If you really want to have _exactly_ what Haskell does (derives the range from an example) -- yes, you could do a macro. Clojure's new spec facility (in 1.9-alphas) makes the macro arguments checked at load time too, which is extra nice: (set! *print-length* 5) ;; avoid printing infinite lists