Atom (text editor)
The following packages provide Atom:
Its packages can be installed from within Atom itself or from the command-line using the apm command. The correct syntax of apm is:
$ apm install package_name1 package_name2 package_name3 ...
Several packages come preinstalled with Atom, notable packages that are not, include:
- build which enables Atom to compile source code.
- git-plus which allows one to manage git repositories from within Atom.
- language-archlinux[dead link 2020-03-28 ⓘ] which provides syntax-highlighting for PKGBUILDs (if installed along with the language-unix-shell package) along with support for running several tests and other actions on PKGBUILDs without a terminal (including makepkg, namcap, updpkgsums, etc.).
- markdown-writer which turns Atom into an efficient Markdown writer.
- script which enables Atom the ability to run scripts, based on file names.
Environment variables not sourced
You may experience some problems with packages using environments variables, like go-plus (
$GOPATH not found). Moreover, it only appears when atom is opened by your file manager. (Because this one is DBUS-spawned, thus it does not inherit variables defined in
A solution is to make available your variables to DBUS-spawned processes, by following Systemd/User#Environment variables.
More info on this issue in Environment variables#Per user.
Unable to delete files
By default, Electron apps use
gvfs-trash to delete files. This command is deprecated and no longer exists, so the
ELECTRON_TRASH environment variable must be used instead to specify which trash utility should be used.
For example, for deleting files under Plasma:
$ ELECTRON_TRASH=kioclient5 atom
At the time of writing, Electron supports
gvfs-trash (default). More info is available at this GitHub pull request page.
Black window content on startup
With some video devices, such as the one for VirtualBox guests, Atom will not render the window content without GPU acceleration disabled by starting it with the
--disable-gpu flag, or by editing
~/.atom/config.cson and adding/changing the config parameter
useHardwareAcceleration: false under the
Spell Checker not working
Make sure you have hunspell installed with a suitable dictionary pack.
Package Manager not working
It has been reported by some users that having an LTS version of node.js can break the package manager, some packages request an LTS version of nodejs so it is possible for a user to inadvertently change versions. see .
This can be rectified by installing, which should detect the conflict between the stable and LTS versions and then remove the LTS version.