Fork me on GitHub
#chlorine-clover
<
2020-04-15
>
fabrao02:04:14

so, I´ll try to create some script to start it up inside init.coffee

seancorfield17:04:43

@mauricio.szabo I updated to Chlorine 0.5.2 and go-to-var is broken (macOS).

mauricio.szabo18:04:32

Ok, let me see what's wrong...

seancorfield18:04:18

Downgraded to 0.5.1 and it works just fine. Let me know if/how I can assist with debugging.

mauricio.szabo18:04:49

Does something appears on the Atom devtools console, for example?

seancorfield18:04:38

How/where do I see that? The symptom is that it ends up opening an empty file with the same name as where the definition would be, so this feels like the path is broken.

mauricio.szabo18:04:59

Right, so it does open something, but its an empty file without anything on it... Can you click on the filename on Atom, and see if the full path is correct? I think Atom will copy the full path to clipboard

seancorfield18:04:45

It looks like it's removing the leading / on the file path and concatenating it with the project root. Which suggests the fix for Windows has broken macOS.

seancorfield18:04:42

How can I debug what os.platform() is returning?

mauricio.szabo18:04:43

Yes, it seems so. While you're on the devtools (I think its the command "Window: Toggle Dev Tools"), can you evaluate a command?

seancorfield18:04:55

Yup, what should I run?

mauricio.szabo18:04:18

require('os').platform()

seancorfield18:04:19

Which matches win in your norm-result function.

mauricio.szabo18:04:07

Yes, I'll fix this 😄. I don't believe it. I kept with win only because Node sends win32 for windows, even when it's a 64-bit machine, so I imagined that future versions could break it 😄

mauricio.szabo18:04:44

Will publish a new version 🙂

seancorfield18:04:09

I wonder if #"^win" would be safer?

seancorfield18:04:04

According to the Node.js docs: "Possible values are 'aix', 'darwin', 'freebsd', 'linux', 'openbsd', 'sunos', and 'win32'."

mauricio.szabo18:04:22

Yes, I missed the case for darwin

mauricio.szabo18:04:50

I think I'll keep at #"^win\d+"

seancorfield18:04:03

(but, yeah, it's weird that it returns win32 on 64-bit systems... I assume because Node itself is only 32 bit and doesn't have a 64-bit version?)

mauricio.szabo18:04:05

Not really... on node's download page, it does list 32 and 64-bit versions

seancorfield18:04:24

Even weirder. But... Node... 🙂

seancorfield18:04:34

Thanks for the quick fix. I'll keep mashing the "Check for updates" button until it appears 🙂

mauricio.szabo18:04:49

Just published 🙂

seancorfield18:04:05

Confirmed fixed!! ❤️

fabrao23:04:42

@mauricio.szabo In Windows still ok !!!

upside_down_parrot 4