@micha: re: https://github.com/boot-clj/boot/issues/409 just tried (yada "public") doesn't work

has to be (yada "resources/public") or my :resource-paths has to be #{"resources/public"} which also affects the jar structure

on the bright side 2.6.0-SNAPSHOT works on the most part

@jethroksy: in 2.6.0-SNAPSHOT the fileset no longer makes files read-only, as a workaround for the windows issues

ran into an emacs issue where reload stops working

Exception in thread "Thread-12" java.nio.file.NoSuchFileException: src/tob/.#handler.clj

but if you were running into issues beacuse of it on linux i think you may have worse problems now

is there an equivalent of .gitignore for boot

because writing to any of those files will cause issues in the fileset

yes there is a file you can make, named .bootignore

with one java style regex per line

ah but it doesn't propogate down sub dirs right?

which?

i remember some time ago the pattern matching was rather inflexible

any paths matching a regex will be ignored

so it matches /.#foo.clj but might will not match /bar/.#foo.clj

these are fileset paths

well they're all relative paths for one thing

I'll play around, see what I can do

foo\.jlj$
/bar\.clj$

that will ignore asdf/qwer-foo.clj

in the fileset

for example

or xzcv/qwer/bar.clj

ohh

but not bar.clj

that's great!

so to ignore *.#* it'd be

\.\#

oh the emacs tempfiles

(?=^|/)\.#

yeah haha

thanks!

I'll make a note on the boot wiki

oh wait

something like that

or maybe cleaner just split into 2 lines

^\.#
/\.#

seems like only the latter is necessary?

if you have :source-paths #{"src"}

^ is for multi line strings right

and there is a file named src/.#foop

the path boot will be applying the regex to is .#foop

so

oh

(re-find #"/\.#" ".#foop") => nil

can't I just match all, i.e discard the backslash

\.#

then you could have the file src/hi.#there

and it would be ignored, too

shouldn't be a problem but I'll use the one you posted anyway

thanks for explaining, I'll put up the example matches on boot wiki

awesome, thanks!

regex is hard

i don't think the .bootignore is documented in the wiki anywhere yet

it seems to have fixed all my problems with snapshot!

can you link to a github repo with the yada stuff you're having problems with?

if i could see the setup maybe something will jump out

sure, give me a moment (the repo is private)

or a minimal repro case would be ideal

sent you a DM

apropos recent convo about producing standalone executables by various means, just put together https://github.com/alandipert/docker-mlton today

@alandipert: How do you enjoy writing in ML? Quite a different experience, no?

it's ok, clojure knowledge ported well enough to get going quickly

i like how weird it is, at the very least

also it's refreshing to make a program with no build tool or dependencies 😄

o_O

sounds like assembly based on that description

programming in asm can be fun too

basically, programming :thumbsup:

I think you mean "the most fun!" 😛

+1

@micha: as it happens yesterday I added some .bootignore info at https://github.com/boot-clj/boot/wiki/Configuring-Boot

looks great

wow, https://github.com/boot-clj/boot/wiki/Configuring-Boot looks great, documentation has been improving a lot lately!

@martinklepsch: fwiw, I fixed my cljs repl issue from yesterday by changing BOOT_CLOJURE_VERSION to 1.7.0. I’m surprised the repl isn’t using the project dependency for clojure.

Morning folks. FYI I created a page on Pipelines but have not linked to it from the Home page yet - it needs to be vetted by somebody who knows boot better than I do. If it passes muster, recommend that the link to it be placed just before the Tasks link - in my view the concept of a pipeline is really central to boot, even if pipelines are not first class objects. I explain my reasoning on the page, which is at https://github.com/boot-clj/boot/wiki/Pipelines

@hugod: that's a limitation given by the fact that Boot only uses a single JVM

@hugod: thanks for pinging back will try to think of that next time

@martinklepsch: I think you can get round it by using pods.

I'm sure I've changed the clojure version in my pods when me & micha were figuring out isolated environments

@dominicm: ah yeah, that might be possible but with tasks like boot-cljs you can't easily override it except using BOOT_CLOJURE_VERSION (which is enough most of the time)

@hugod: boot doesn't know about your project depenedncies until clojure is already loaded

since boot is just running your build.boot which is itself a clojure program

so you have a chicken and egg problem

@martinklepsch: I have a fork of boot-cljs where you can run it in a pod, 😛

boot can't know which version to use to run your build.boot until it runs your build.boot

I think I opened a PR

this is why you need to have BOOT_CLOJURE_VERSION be the same as your project clojure dependency

So is it recommended to have a project local boot.properties file specifying BOOT_CLOJURE_VERSION?

yes definitely

and boot version too

so you don't have any surprises

most important if you have unattended builds, like on a CI machine

i suppose boot should add a clojure dependency to your project automatically

Thanks. It seems boot.properties hardly gets a mention in the readme.

you can always set-env! to remove it

So I can't have a task test without getting the redefinition warning?

you can use ns-unmap

Nice! Thanks

it's just a clojure program! lisp can doit

yeah, but there's no ns form at the top, that's why I was wondering

the ns form is generated

you can do boot -vb and see it

the generated namespace

That works, thanks

there are comments delimiteing the places where your code meets generated code

@micha: oh. I wrote my code to read a file from /tmp/ when I couldn't figure out what was happening...

also good!

Tasks were one-lined. Very difficult to debug.

-vb helps there a bit

yeah? does it work with the stacktraces?

because that's where I was struggling

yes you just need to run your tasks with -v

so suppose you do boot -v foobar

and you get a stack trace

you can then do boot -vb |cat -n

and see the matching line numbers

actually you should do boot -vb foobar

to get the exact same generated code

just add -b to the thing that caused the error

That's really neat. Thanks

I give up trying to understand how to set the output directory for boot-cljs. I have no idea what the cljs.edn mentioned in boot-cljs #104 is supposed to look like.

@hugod: https://github.com/adzerk-oss/boot-cljs/wiki/Usage#multiple-builds

@micha thanks - I missed that (I just have a single build)

let's deprecate builds without .cljs.edn (and rework docs accordingly)

Umm, looks like ‘boot-react-native’ is overwriting the output options anyway

is it? couldn't see any indicators at a quick glance /cc @pesterhazy

@hugod, have you had a look at the sample app?

https://github.com/mjmeintjes/boot-react-native/tree/master/example

boot-react-native should not interfere with cljs compilation

Guys do you have the boot logo in svg somewhere so that I can put in ona website?

found!

@richiardiandrea: which website? just curious

I am about to lauch a (small) consultancy company Clojure based, it is actually a "branch" of Scalac: https://github.com/Lambda-X

awesome! happy to add a "companies using boot" to http://boot-clj.com/ also if you wanna PR on https://github.com/boot-clj/boot-clj.github.io

@richiardiandrea: nice! congratulations on launching a business I guess

man i really need to perun-ize http://boot-clj.com some day

so shameful it uses jekyll

cond-let — does such thing exist?

oh yeah - i just made it a few weeks ago

(defmacro cond-let [& clauses]
  (when-let [[binding expr & clauses] (seq clauses)]
    `(if-let ~binding ~expr (cond-let ~@clauses))))

using it together with clout to do simple http request matching

use like

(let [x 123]
  (cond-let
   [y (and (even? x) (inc x))]
   (println "x is even and x+1 = " y)
   [y (and (odd? x) (dec x))]
   (println "x is odd and x-1 = " y)))

nice macro

I thought of it more like this:

(cond-let y
  (thing foo) (println y)
  (thing bar) (slurp y))

but I guess they're pretty close

also a let thing with let like binding vectors makes sense hehe

That doesn't look like a rhombus

It's a big straight

4/10

I put a dependency on my build.boot, and when running in the repl it works fine, but when I try to run a file with that dependency it says "could not locate on classpath"

@arijun: how do you mean "running a file"?

in cursive, right click and click run file

but now I see it must be a cursive issue because cursive seems to explicitly set the classpath

yeah I had to "Refresh Leiningen Projects" my bad

yeah, cursive does not work with boot by default yet

there's some stuff in the wiki about cursive if you're curious

Yeah, I ran the lein-generate task and thought that would do it, didn't realize I also had to do something in cursive. Strange that there can't just be a watch on the project.clj file.

guys if I do:

(comp (target)
        (cljs :compiler-options devel-options))

I don't see core.out in target for instance

the target task can only emit files it can see in the fileset

if you put it before a task, it won't be able to see any files craeted by the task that comes after it

ah crap, rookie mistake

the target task just takes a fileset from the previous task in the pipeline, looks inside to see which files need to be emitted, and it writes them to a directory

so for serve is the same right, it should go after (cljs ...)

that one can go anywhere i think

because it's just for side effects (starting a web server)

i believe it uses a post-wrap style

it doesn't actually look in the fileset, just the classpath

ok tnx @micha

yes, so this one does not serve from fileset, undestood

so I have to dump the compilation somewhere then serve from there

it should serve from the classpath

(serve :port 12345)

usually it Just Works (tm)

lol

nobody knows what it does, but it works

the best kind

in my case: ClojureScript could not load :main, did you forget to specify :asset-path? 😄

but I thought I did not need that anymore 😄

yeah that's coming from the cljs compiler

so I still need it even if I don't have a output-dir

(def devel-options
  {:optimization :none
   :source-map-timestamp true})

so I needed my core.cljs.edn to be: https://github.com/martinklepsch/tenzing/blob/master/resources/leiningen/new/tenzing/app.cljs.edn

i dunno, i always just load the js from a relative path, like "main.js"

the location of the js file is an implementation detail to me

i have a task that craetes the html file and the .cljs.edn file

so i just do cljs and the rest is automated

oh well yes it that case ok 😄

the asset path business makes things complicated and i recommend avoiding it if you can

it's like when you do (require 'clojure.core) in clojure

there is no option to configure an asset path

because if there were then everything would be way more complicated

mmm...I agree I'll see I can avoid it but tenzing does it and I am worried I need it too

because nothing could figure out where the source file is for a given namespace

the namespace 'clojure.core maps to the file clojure/core.clj on the classpath

and that's that.

we need to make web applications with the same kind of discipline

this is how we get out of the tarpit

agree

locating the js file in a well defined location is the start

if you can't even do that then you're building on sand

but it looks like I needed to have:

{:require  [lambdax-web.core]
 :compiler-options {:asset-path "lambdax_web/core.out"}}

gross lol

ahaha

if i remove that, i don't see main.js served

I lied, it is there and working fine 😄

Are there active Boot communities outside of Slack? (just casually thinking about Slackpocalypse)

The CIDER / refactor folks are very active on Gitter (around their respective GitHub project rooms).

I guess when it happens we'll move too 😄

there is #bootclj on freenode

what's boot's equivalent to this? https://github.com/emezeske/lein-cljsbuild/blob/0.2.9/doc/CROSSOVERS.md

i'm attempting to get http://www.mattgreer.org/articles/embedding-svg-into-a-reagent-component/ working in my project

@naomarik: https://github.com/adzerk-oss/boot-cljs

@micha a question, is main.out always written in boot-cljs no big fat main.js ?

`

command I tried: boot cljs -sO advanced -- target

so i guess condensed form of my question: how can i share a clojure macro in clojurescript with boot?

nothing changes, clojure macro always go in clj files and needs to be included in source-paths

ahh i've tried this 😞 and i have (:require-macros [embed.svg :refer [embed-svg]]) in my ns

@richiardiandrea: you get a single file if you have the :optimizations option to boot-cljs as :simple, or :advanced

yeah but I did exactly that: boot cljs -O advanced -- target

with :none you get the whole main.out thing

you should have everything in the one file

if you try with a clean tanzing template you can see the same

with advanced optimiztions

did you look in the js?

yeah

there is still the main.out dir because you need that for source maps

you can use sift to get rid of it if you want

oh, ok so I can delete it safely

your main.js file or whatever should be a big blob of js

unlike the main.js shim you get with :none

thanks, maybe you can add it somewhere in the wiki, or tell where I will add it

the difference should be very visible if you look in the file

yes I know how it generally is, that's why I was surprised to see the .out 😄

I looked and you are right

the .out directory doesn't hurt anything in most cases

but sift can quickly do away with it

well yes, but it is sane to write it somewhere imho, I can do it, I just don't know where is more appropriate

the boot-cljs wiki is probably the best place

strange thing happening too: when i refer to the clojure macro AND try to invoke in the clojurescript, i get an error in boot from a file that's no longer in my project No such namespace: alandipert.storage-atom

i've tried removing .boot/cache and everything in target/

is there another cache dir somewhere?

mmm...not that I know of...but wait for the gurus 😄

@naomarik: the target dir is never looked at by boot ever

so nothing in there can affect a build

it's write-only

good to know was trying to eliminate it as a possibilty

all other state is stored in ~/.boot/cache, but only truly immutable things are stored in there

never anything that could ever change

how would boot know about a file that is removed then?

and the error only comes up when i try to use this macro

when i remove the macro

because it doesn't try to make those kinds of optimizations

it looks every time

it compiles perfectly

that's because of the jvm state

once you compile something it will stay in memory

ahh

so macros are functions

the compiler can still call the function

so my setup is this: i have a clojure macro in src/embed/svg.clj and (:require-macros [embed.svg :refer [embed-svg]]) is a line in my clojurescript file. my build.boot has "src/clj" in the source-paths set

calling

(defn some-svg-component []
  (embed-svg "test.svg"))

from the file that i have removed

a long time ago

boot show -f is your best bet

my setup looks fine though to get the macro working?

all the stuff i want is in boot show -f

you said you have the clj file in src/embed/svg.clj

but your source paths are "src/clj"

src/clj/embed/svg.clj

so something is wrong there

ah

embed └── svg.clj

i get this as part of the output

so that's good?

yee

it's highly unlikely that a stale file is in the classpath

since boot doesn't do that kind of caching anywhere

hmm so what can i do there?

you restarted the jvm right?

to clear old stuff out of memory

kill all java proceses?

lemme try

hmm

my ps aux reveals massive classpath /usr/bin/java -classpath /Users/naomarik/Sites/.... (continues for like 15 lines

)

that's not boot

that is probably leiningen

lol

sorry

how do i restart the jvm on osx?

press ctrl-c

so you're saying just restart boot

yeah

hehehe

i've done that million times throughout this 😛

oh

hm

(:require-macros [embed.svg :refer [embed-svg]]) if i edit this line slightly to include the wrong path it will give me a sensible error

so i can infer that it IS finding this

invoking the macro though still gives me an error from the file that no longer exists

and you did a git grep for references to the old namespace?

the onlything in the macro file is this

(ns embed.svg
  (:require [pl.danieljanus.tagsoup :as ts]))

(defmacro embed-svg [svg-file]
  (let [hiccup (ts/parse-string (slurp svg-file))]
    `~hiccup))

it's definitely something in your source somewhere that's referencing the old file

or something

i did ag -a alandipert and got nothing

in my project

git grep alandipert

try that

lol i bet he's getting alerted by slack right now

hmmmm

that returned nothing but at some point this started working

i may have been an idiot regarding this

test.svg (No such file or directory) this is what i like to see 😉

hahah

sorry @micha for the silliness.. i'm using tmux and somehow i scrolled up in my terminal without tmux-scrolling... somehow the stack trace looks perfect with what the real output is and some old output

the continuity is perfect

hahaha it happens

you should see it lol

maybe should sleep at some point , 2:30 am here

night 😉

later!