Fix auto-install of pnpm and node on mode init

[stephanmax]

Changes

• Introduce new method probeCommand to check for presence of critical tools pnpm and node
• Introduce helper closure to stack notices in the status line of PDE
• Make directory for builder optional

Fixes #14

[Stefterv]

I suspect this doesn't work because my shell env first prints my lovely terminal art before running anything else

[stephanmax]

That IS lovely! Interesting, I will check how I can distinguist command output and general shell output.

(Ah yes, I remember now, I am using a full-on interactive shell so we can have all the env variables, but that of course also triggers any user-defined shell startup code in .bashrc or equivalent.)

[catilac]

@stephanmax this is working for me on gentoo/zsh/wayland /cc @lee2sman

[lee2sman]

how can i test? do i need to build from source? i don't have a kotlin or java environment set up for example.

[catilac]

let us know what you're thinking for handling running shell commands @stephanmax

@lee2sman ooops nevermind. ill let you know when this is merged. i forgot you're not building

[Stefterv]

[stephanmax]

I think the easiest workaround is only considering the last line of the command output. This is not as rigorous a solution as I’d like, but my other ideas fall short as well.

• We could redirect the command output to std error and read that stream. User-defined output would still go to std out and we could dinstinguish them.
• We could just consider the error code. But I like the debugging information that pnpm and Node version give us.
• Come up with a more clever test for a certain binary (without relying on an interactive shell)?!