Hello Linux Geeksters. As you may know, Atom is an open-source, multi-platform text editor developed by GitHub, having a simple and intuitive graphical user interface and a bunch of interesting features for writting: CSS, HTML, JavaScript and other web programming languages. Among others, it has support for macros, auto-completion a split screen feature and it integrates with the file manager.
The latest version available is Atom 0.124.0, which has been released a while ago, coming with important changes.
Open Behavior Changes
- Selecting a file from the open dialog will now open that file in the current window.
- Dropping a file onto a window now opens that file in the window it was dropped onto.
- Selecting a folder from the open dialog will now open that folder in the current window if it is untitled.
- Dropping a folder onto an untitled window now opens that folder in the window it was dropped onto.
Apm Changes
- Fixed an issue where apm commands would fail if RVM was being used.
- Fixed an issue where apm unpublish would fail when run without a package name.
- Added the number of stars a package has to the command output.
- Add a –language option to the apm init command that generates a new language grammar package.
Other Major Changes
- Fixed an issue where the editor would log document.createNodeIterator errors.
- The editor DOM elements now have a data-grammar attribute that contains all the segments of the current grammar’s scope, such as source js.
- The workspace DOM element now contains the current UI theme name as a CSS class.
- Fixed an issue when moving to the first character of a line with leading hard tabs when invisibles were enabled.
- Fixed an issue on Mac where the window’s title bar would not be visible in certain scenarios.
- Added a new grammar for SQL files with Mustache templates named SQL (Mustache).
- Fixed an issue where the Styleguide would not open.
In this article I will show you how to install Atom 0.124.0 on Fedora 20 systems.
Follow the below instructions exactly, in order to get a successful installation.
Install the needed dependencies:
$ sudo yum -y install node npm libgnome-keyring-devel
Update nmp and adjust the PATH:
$ cd ~
$ npm install npm
$ export PATH="$HOME/node_modules/.bin:$PATH"
Install Google Chrome Stable, so that the libudev.so.0 gets satisfied:
$ sudo sh -c 'cat > /etc/yum.repos.d/google-chrome.repo <<EOS
[google-chrome]
name=google-chrome
baseurl=http://dl.google.com/linux/chrome/rpm/stable/x86_64
enabled=1
gpgcheck=1
gpgkey=https://dl-ssl.google.com/linux/linux_signing_key.pub
EOS'
$ sudo yum -y install google-chrome-stable
Remove gyp, to avoid conflicts:
$ sudo yum -y remove gyp
Get the Atom sources and build the software:
$ git clone https://github.com/atom/atom
$ cd atom
$ ./script/build
Set execution permissions:
$ sudo chmod +x /tmp/atom-build/Atom/atom
For an easier usage, do:
$ echo "alias atom=LD_LIBRARY_PATH=/opt/google/chrome ~/atom/atom.sh" >> ~/.bashrc
$ source ~/.bashrc
To open Atom 0.124.0, just open a terminal and type atom.
Optional, to remove atom, do:
$ rm -f ~/atom
$ sed '/LD_LIBRARY_PATH=/opt/google/chrome ~/atom/atom.sh/d' ~/.bahsrc
Great guide, still works like a charm, thanks!
Questions:
1. Why did you use Chrome instead of Chromium? The latter is Open Source, has easy Fedora repos, and would be easier to use as the backend, no?
2. What did your instructions do with Node? Looks like we installed it from repos, changed its directory, upgraded it, then removed the package, leaving an orphaned copy of node behind, somewhere else on disk? Care to shed a little more light on the conflicting package – is it a version conflict of the same package or a package conflict with another package?
hello. I had to install chrome for the libudev.so.0. most likely, chromium works too.
the conflict is between gyp and node-gyp . most likely, npm is required only to install some dependencies.
this issue is reported here: https://github.com/atom/atom/issues/2029, i have just tested the workaround and it worked. ๐
Nice – I think I’ll retry with Chromium and see what happens (don’t particularly need two Chrom* browsers on my laptop).
Also, after rebooting I noticed that /tmp had been cleaned and atom.sh is still looking for it:
“nohup: failed to run command โ/tmp/atom-build/Atom/atomโ: No such file or directory“
Not sure why it’s trying to build again?