Package Details: atom 1.61.0beta0-3

Git Clone URL: (read-only, click to copy)
Package Base: atom
Description: A hackable text editor for the 21st Century
Upstream URL:
Licenses: MIT
Replaces: atom-editor
Submitter: alerque
Maintainer: None
Last Packager: alerque
Votes: 4
Popularity: 0.000876
First Submitted: 2022-06-09 08:13 (UTC)
Last Updated: 2023-06-29 13:04 (UTC)

Latest Comments

1 2 3 4 5 6 Next › Last »

AlexWayfer commented on 2023-06-29 13:13 (UTC)

I disagree about the 20th century: Electron and Atom are great technologies of software developing in the 21th century.

But yes, acquiring by Microsoft is disappointing.

And I agree that Pulsar Editor is way better now. It's still very "atomic", but already N times faster due to new versions of Electron and Node.js. And they make small steps forward to resolving most existing issues, left by Atom maintainers.

Atom-Community was a previous attempt, but unsuccessful.

alerque commented on 2023-06-29 13:05 (UTC)

Atom got stuck in the 20th century, not the 21st. Even their sunset release was broken, and the Electron version uses positively ancient.

I'm disowning this package because I am no longer interested in it. Even trying to patch up the final release so it is not OOD is now pointless to me. Pulsar is the only viable option for the folks I had using Atom.

yupi commented on 2023-02-05 14:43 (UTC)

@nevernow Let me mention that the fork "pulsar" (pulsar-bin here) is working quite well for my atom needs. Of course the experience can vary but so far pulsar's community seems more-or-less thriving with relatively many commits, bugfixes, and plans to upgrade to newer electron versions.

alerque commented on 2023-01-19 13:48 (UTC)

If anybody gets 1.63.x working I'm still open to patching this!

alerque commented on 2023-01-11 11:14 (UTC)

@nevernow You need to switch from the obsolete electron11 package (no longer in [community]) to electron11-bin from the AUR.

nevernow commented on 2022-12-14 16:46 (UTC)

At the moment my atom is broken with

electron11: error while loading shared libraries: cannot open shared object file: No such file or directory

re breakage might be the final nail in the coffin - I reluctantly installed Visual Studio Code today.

shoryuken commented on 2022-12-14 09:30 (UTC)

@alerque Oh right, thanks for the clarification. I hadn't checked the logs at all and I thought it was a "real release" :/

alerque commented on 2022-12-14 07:04 (UTC)

@shoryuken No it is not going back in [community]. It is still end-of-lifed and even the "new release" doesn't update Electron or anything important. It is basically a codification of the unreleased bits since the last tag but no real new development work. As such it does not compile cleanly, does not play nice with current Electron or other system dependencies, and has no future hope of doing so.

If some community fork got far enough along to address those things we could consider it, but the official Atom project is dead. We're not going to try to prop up its corps in the repos.

shoryuken commented on 2022-11-24 21:58 (UTC)

If there are new releases of Atom, couldn't it be put back in community?

alerque commented on 2022-11-24 20:55 (UTC)

I've tried a quick bump to the new 1.63.1 release but something goes sideways and I haven't had time to figure it out. I'd be happy to accept a patch if anybody figures it out!