Fork me on GitHub
#leiningen
<
2020-04-02
>
mikerod15:04:47

@zikajk I haven’t looked too closely but can you see what is happening with lein with-profile dev pprint

👍 4
mikerod15:04:20

Should show you what all is merged into the project map (look at top level keys). Should see :main there and be sure it is not what you want.

jlt20:04:17

Can anyone suggest a good way to get separators printed out between tasks in `lein do` ? ie. I'll use some pseudo `lein eval` task to illustrate the behaviour I'd like to achieve:

:aliases {"all" ["do"
                 "eval \"(println \"running foo\")\","
                 "foo,"
                 "eval \"(println \"running bar\")\","
                 "bar,"
                 "eval \"(println \"running baz\")\","
                 "baz"]}

mikerod20:04:54

@jameslintaylor I am not positive I understand - but you could potentially have use for lein-shell

mikerod20:04:19

this plugin

jlt20:04:29

That's perfect, thanks 🙂

🎉 4
mikerod20:04:04

it can do a lot of cool stuff

mikerod20:04:55

for your case, something like this:

:aliases {"all" ["do"
                 ["shell" "echo" "running foo"] 
                 ["foo"]
                 ["shell" "echo" "running bar"]
                 ["bar"]
                 ["shell" "echo" "running baz"]
                 ["baz"]]}

👍 4
jlt20:04:39

I had no idea you could use vectors here! Feels good to not have those commas dangling around, awesome 😄

mikerod20:04:22

yeah, I prefer vectors for structuring within :aliases

mikerod20:04:36

and I’ve found the best results to just wrap each “segment” in it’s own vector for do

mikerod20:04:03

composes better that way, if for examples you had

"bar" ["do" <stuff here>]