Fork me on GitHub
#juxt
<
2017-04-12
>
imre10:04:52

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?

ul10:04:53

either i3wm or kde depending on the mood 馃槂

imre10:04:42

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

ul10:04:33

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

ul10:04:51

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

ul10:04:21

KDE5 is much better than 4th was

imre10:04:32

sounds nice

imre10:04:42

I'm getting a little fed up with gnome

imre10:04:59

might give it a shot

dominicm10:04:19

I use bspwm

jonpither20:04:57

you are running mach main plan

dominicm20:04:40

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

dominicm20:04:44

This might be OK behaviour.

jonpither20:04:47

you would expect Mach to not run the latter target

jonpither20:04:56

yeah, unsure what should exactly happen

jonpither20:04:00

I'll spin up a Make

dominicm20:04:11

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

dominicm20:04:17

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

jonpither20:04:43

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

dominicm20:04:50

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

dominicm20:04:00

Yeah, you get it I think 炉\(銉)/炉

dominicm20:04:02

Might be okay.

jonpither20:04:39

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

dominicm20:04:47

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

dominicm20:04:03

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

jonpither20:04:42

working up the courage to tackle your async streaming output thing

jonpither20:04:44

[[email protected] git]$ make foo echo "baz" baz echo "bar" bar [[email protected] git]$ make foo baz echo "baz" baz echo "bar" bar make: 'baz' is up to date.

jonpither20:04:05

foo depends on baz

dominicm20:04:10

make has inherent freshness.

jonpither20:04:12

that's quite cool isn't it

jonpither20:04:41

what do you mean? inherent freshness

dominicm20:04:55

everything has a file it produces

dominicm20:04:10

you used phony targets, not file writing

dominicm20:04:12

or did you?

jonpither20:04:36

just echoing "baz" and "bar"

dominicm20:04:51

so make knows it already ran it

jonpither20:04:21

it keeps track

dominicm20:04:03

very clever

jonpither20:04:19

easy enough for us to do tho

jonpither20:04:58

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