Package Details: atom-editor 1.8.0-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-editor-bin, atom-editor-git
Submitter: jreese
Maintainer: jugs
Last Packager: jugs
Votes: 620
Popularity: 56.518879
First Submitted: 2014-05-06 18:29
Last Updated: 2016-06-07 00:40

Latest Comments

elpres commented on 2016-06-21 12:27

Can't install from behind a corporate proxy. At first the installation failed at an early stage until I manually set the proxy settings for npm:

npm config set proxy $http_proxy
npm config set https-proxy $https_proxy

But now there is another error of the same kind coming from apm. Adding the settings to ~/.atom/.apm/.apmrc manually before running the installer doesn't help since the file is overwritten during installation.

I suppose running these command after installing apm but before it tries to download anything could solve the problem:

apm config set proxy $http_proxy
apm config set https-proxy $https_proxy

It's possible that only HTTPS is used, so the last one could suffice.

kjslag commented on 2016-06-14 19:59

I had to
$ mkdir -p ~/.atom/.npm
or else the build would fail with
npm ERR! enoent ENOENT: no such file or directory, lstat '/home/k/.atom/.npm/'

JoseluCross commented on 2016-06-14 16:20

I got this problem "fs: re-evaluating native module sources is not supported. If you are using the graceful-fs module, please update it to a more recent version."
In I read that the version 6 of nodejs is incompatible, I ran downgrade and and install version 5. Now the packaging doesn't give any problem.

horosgrisa commented on 2016-06-13 07:29

Please add suport for custom flags such as in

Sir.Tiddlesworth commented on 2016-06-07 23:53

1.8.0-1 works fine for me also.

ryanvade commented on 2016-06-07 16:32

I am not having any issues after upgrading to 1.8.0-1

wanderingfree commented on 2016-06-07 05:12

The new update (1.8.0-1) causes atom to fail on start with the error message:

/usr/share/atom/atom: error while loading shared libraries: cannot open shared object file: No such file or directory

UPDATE: It's now working again. I had to delete my ~/.atom folder though, which leads me to believe that there were cached extensions/electron that had to be rebuilt. If atom refuses to start after you update, try deleting your ~/.atom folder.

elvetemedve commented on 2016-06-04 11:13

I get random download failures like these:
Installing one-dark-syntax@1.2.0 ✗
Unable to download read ETIMEDOUT

Installing about@1.4.2 ✗
Unable to download getaddrinfo ENOTFOUND

When I open these URLs in the browser it starts downloading without an issue.

jugs commented on 2016-06-02 21:11

Hey there @diraimondo,

That's a good suggestion, I'll take a look.

diraimondo commented on 2016-06-02 18:52

Could you include the equivalent of the following command in the building instructions of this AUR package?

sudo ln -s /usr/share/hunspell /usr/share/atom/resources/app.asar.unpacked/node_modules/spell-check/node_modules/spellchecker/vendor/hunspell_dictionaries

This makes Atom to find the installed hunspell dictionaries. You can change the language tweaking the LANG environment variable.

More details on:

All comments