Clojurians Log v2

re: many println forms -- had some success with using breakpoints in cljs source in dev tools inside atom to observe execution. i wonder how long this has worked...may be it was the result of thheller's recent source map efforts.

may be you know this already, but fwiw i wrote up my observations about using the devtools debugger: https://gist.github.com/sogaiu/025ce011b60c6636446ad3ec6e593d84 -- i am not finding it to be reliable, but it's nice when it works

running the plugin from a shadow-cljs watch build, i am not seeing the settings button for chlorine -- is anyone else seeing this?

i do see the settings button if i install from within atom

Wow, that's strange. Which OS / Atom version are you using?

@mauricio.szabo i'm using atom 1.40.1 x64 on manjaro linux

Okay, I had some problems with MacOSX, but its not your case here...

ah, i can try on macos at some point -- will try later

Well, the problem I had was on macosx so things should be working on Linux

I also develop Chlorine on Linux, and I'm not seeing this behavior. Does the lib/main.js and lib/cmds.js exist on the plugin dir?

yes, i see them both

the plugin seems to function appropriately otherwise -- just don't know how to get to the settings ui 🙂

If you run atom.packages.getActivePackage('chlorine').mainModule.config on the Atom devtools, do you get back a JS object?

yes -- once i attempt a repl connection, that does give me a js object. before that, i get something about mainModule not found. however, even after i get a js object and going to look for the settings button, i don't see it. i also closed the overall settings tab first before looking.

Okay, sometimes Atom gets completely lost on some configurations. I would suggest to close Atom, open it with --safe flag once, see if Chlorine is really deactivated (or if it even appears on the settings tab), then close and open again. Maybe even before you re-open Atom, you could delete all caches (`.shadow-cljs`, lib/js and lib/cmds.js) and trigger another watch. I know it's kinda tedious, but I did solve lots of problems with Atom inconsistencies with it, so....

thanks for the tips, will try -- fwiw, i'm testing in a dummy user account with a fresh slate

did: atom --safe # saw that chlorine was listed as a package, but there is only a button for installation i removed: .shadow-cljs, lib/js. lib/cmds.js, node_modules then: npm install && npx shadow-cljs watch dev quit atom and restarted with atom --safe (still only an install button) start atom (missing settings button)

Oh well... no idea

I'll see if I can reproduce here

thanks -- do you know if there's a way to run atom where it gives verbose tracing about its activities?

There are some flags like --foreground, some variables like ELECTRON_ENABLE_LOGGING=true that will log to the console, but other than that only flags like --dev and --enable-electron-logging that don't do much to help

I only saw a similar problem with yours is that while I was developing the Enable experimental features config, sometimes the Atom didn't honor the config, but after I upgraded it isn't happening anymore

thanks for the tips