Fork me on GitHub
#shadow-cljs
<
2018-01-25
>
tony.kay01:01:59

@thheller I don’t actually need the figwheel status…it’s also my REPL. With no HUD I have to have a status window AND another one open for a REPL. I can also close the REPL with a keystroke and reclaim that dead space without it affecting my flow.

mhuebert08:01:32

so, i’ve (1) changed the semicolons to &&’s, and (2) added a sleep 2 after shadow-cljs start (one second didn’t seem to be enough)

mhuebert08:01:36

it seems to work

mhuebert08:01:50

still have the lingering-process issue

thheller10:01:54

@mhuebert that is so strange. the lingering java process issue for me was solved by this weird trick https://github.com/thheller/shadow-cljs/blob/master/src/main/shadow/cljs/npm/cli.cljs#L562-L568

thheller10:01:08

which node version/jvm version are you on?

mhuebert10:01:48

node v7.8.0,

mhuebert10:01:09

java version "1.8.0_45"
Java(TM) SE Runtime Environment (build 1.8.0_45-b14)
Java HotSpot(TM) 64-Bit Server VM (build 25.45-b02, mixed mode)

thheller10:01:47

can you try upgrading node? the java version is fine.

thheller10:01:09

I’m on v8.9.0 but v9 also works

thheller10:01:23

shouldn’t make a difference though

thheller10:01:04

$ npx shadow-cljs start; npx shadow-cljs stop;
shadow-cljs - config: /Users/zilence/code/tmp/cljs-bg/shadow-cljs.edn version: 2.0.143
shadow-cljs - server starting ........................................... ready!
shadow-cljs - config: /Users/zilence/code/tmp/cljs-bg/shadow-cljs.edn version: 2.0.143

thheller10:01:33

no lingering processes. macOS. no idea what else could be different

thheller10:01:38

macOS version?

thheller11:01:15

I plan on rewriting the process handling of the node script soon so I hope that issues goes away then

mhuebert16:01:05

mac os 10.13.2