Package Details: atom-editor 1.11.2-1

Git Clone URL: (read-only)
Package Base: atom-editor
Description: Chrome-based text editor from Github
Upstream URL:
Keywords: atom
Licenses: MIT
Conflicts: atom, atom-editor-bin, atom-editor-git
Submitter: jreese
Maintainer: jugs (samueloph)
Last Packager: samueloph
Votes: 680
Popularity: 21.502352
First Submitted: 2014-05-06 18:29
Last Updated: 2016-10-23 03:33

Latest Comments

ltorvalds024 commented on 2016-10-25 10:54

Atom editor is now available in Arch repo. Cheers!

lordchaos commented on 2016-10-25 08:16

@trichards Yeah I noticed that as well. We do have a crappy MS proxy here, but I never had any trouble pulling everything in. Will look for a workaround.

trichards commented on 2016-10-24 20:14

@lordchaos Yes, there should be a node binary in there and it should be executable. A couple lines up from that in your output you've got a "Error: read ECONNRESET", are you behind a firewall / proxy / bad internet connection?

lordchaos commented on 2016-10-24 09:59

At the moment, I'm not able to build the latest version:

Node: v6.9.1
Npm: v3.10.9
Installing script dependencies
Installing apm
../deps/libgit2/deps/zlib/inflate.c: In function ‘inflateMark’:
../deps/libgit2/deps/zlib/inflate.c:1507:61: warning: left shift of negative value [-Wshift-negative-value]
if (strm == Z_NULL || strm->state == Z_NULL) return -1L << 16;
throw er; // Unhandled stream error in pipe.

Error: read ECONNRESET
at exports._errnoException (util.js:1026:11)
at TCP.onread (net.js:569:26)
/var/tmp/makepkg/atom-editor/src/atom-1.11.2/apm/node_modules/atom-package-manager/bin/apm: line 35: /var/tmp/makepkg/atom-editor/src/atom-1.11.2/apm/node_modules/atom-package-manager/bin/node: No such file or directory
throw err;

The node binary seems to be it supposed to find the binary there?

samueloph commented on 2016-10-11 13:59

v1.11 being released right now, I should update the package in about 4 hours.

edit-> looks like atom removed the grunt install script that we're using, its gonna take me more work than i thought to prepare this new release, probably packaging v1.11 by the end of the day or tomorrow, unless @jugs do it sooner or someone sends a PR on our github repo.

sshow commented on 2016-10-04 01:16

For those using Node Version Mangager (NVM), you may not wish to install nodejs from the official repositories. To get a successful build with 1.10.2-1: edit PKGBUILD and remove nodejs from depends and npm from makedepends.
Switch to the LTS release of node.js before installing to avoid invalid shasum checks on modules: "nvm install 4.6.0 && nvm alias atom-build 4.6.0 && nvm use atom-build"
Now install as you usually would with e.g. "makepkg -sri".

jugs commented on 2016-09-08 12:49


Welcome as new co-maintainer, thanks for your help.

samueloph commented on 2016-09-08 12:48

Version 1.10.2 PR'ed

As jreese doesn't work on the package anymore, I volunteer to be the submitter of the package, that way i could update atom-editor directly.

fusion809 commented on 2016-09-08 08:21

@jugs if you've lost interest in maintaining this package (which I'm guessing based on how slow you've become to updating it) I'll be happy to take over the reigns.

gonciarz commented on 2016-09-01 11:09

Without gvfs package I get the following error when I try to delete a file/directory:
The following file couldn't be moved to trash (is gvfs-trash installed?)
Thus I suggest to add 'gvfs' package either to 'depends' or 'optdepends' section.

All comments