Clojurians Log v2

question to you arch-ers: do you use desktop/window managers (or ecosystems) and which one do you find most pleasant to work with daily?

either i3wm or kde depending on the mood 😃

how's kde these days? I know it used to be bloated as hell a good few years ago

quite nice as of my taste: performant and stable enough, though you have all the stuff like automount/network/energy saving etc. without need for installing and tuning too much by hand

from the UX endpoint, still doesn't catch up with MacOS

KDE5 is much better than 4th was

sounds nice

I'm getting a little fed up with gnome

might give it a shot

I use bspwm

@dominicm not sure I get https://github.com/juxt/mach/issues/24

you are running mach main plan

hmm

@jonpither plan depends on main. main gets called twice.

This might be OK behaviour.

you would expect Mach to not run the latter target

yeah, unsure what should exactly happen

I'll spin up a Make

Make doesn't have this problem, because it's based on file freshness.

If you have novelty set, this isn't a problem.

funnily enough tho, in trying to reproduce, I find a related bug with the new mach/props, the props get evalled per rule invocation (which may again.... be OK

Not sure if mach should assume non-freshness in the case of it already being run in the same process.

Yeah, you get it I think ¯\(ツ)/¯

Might be okay.

Might not.

yeah. If you get my new bug also, then we have 2 bugs of similar class

not got brain power to figure out what mach/props are right now. but it wouldn't surpirse me.

I can think of a solution of kind (surrounding putting everything in a delay)

yeah

working up the courage to tackle your async streaming output thing

[jon@juxtxps07 git]$ make foo echo "baz" baz echo "bar" bar [jon@juxtxps07 git]$ make foo baz echo "baz" baz echo "bar" bar make: 'baz' is up to date.

foo depends on baz

make has inherent freshness.

that's quite cool isn't it

what do you mean? inherent freshness

everything has a file it produces

Oh wait

you used phony targets, not file writing

or did you?

phony yeah

just echoing "baz" and "bar"

so make knows it already ran it

yes

it keeps track

very clever

easy enough for us to do tho

the bug is slightly worse also, mach foo bar (and foo depends on tar depends on bar, and foo depends on bar), then bar prints out 3 times - no de-duping