20 comments

[ 0.25 ms ] story [ 14.5 ms ] thread
I tried this thing on Linux yesterday, and when searching for a plugin, I got the chrome dev tools open and present me with an error...I'm surprised it came out of beta. Does this problem happen in Windows?
It's not out of beta on Linux, so I'm not sure what you're surprised about.
It is? The readme/installation instructions (github) don't mention that anywhere. But actually, I got it working, so all good.
It is pre-1.0, and only official builds are provided for OSX so far. That said people are having a lot of luck getting things working on disparate configurations so I am feeling optimistic about the progress of lin/win!
Works great for me on Win8.1 x64. Thanks for doing this.
Thank you kind sire. Works perfectly fine.
does anyone have a mirror?
Power of making something open source !
Thanks. I tried building from the source and it worked without errors but then I couldn't figure out how to actually run it? How did you compile the executable?
When you run script\build it automatically tries to install it in program files. If it failed to do that, you can also copy %temp%\atom-build and run the exe from there.
Thanks for this.

If you get errors while extracting with WinRar, like "Total path and file name length must not exceed 260 characters", then use the advice here[0] to work around it.

[0] http://stackoverflow.com/questions/13178377/winrar-total-pat...

> I recommend extracting it so that the base directory is C:\Atom or whichever drive you prefer, as this prevents long path name errors.

The issue I am referring to is not the same as the issue at the end of the post. I'm referring to an issue with the temp folder that WinRar uses, and not the path to which you are extracting.

One more edit: Working well on Win7 Pro SP1.

Strange. It seems to extract to C:\Atom fine over here, it refuses to extract to my desktop though, Surely my Desktop is shorter than AppData\Local\Temp o_O