sudo dpkg -P $(dpkg -l | awk '/^rc/ { print($2) }')

rakudo-pkg offers native packages of Rakudo Perl 6 that closely follow upstream development. Most of the time, the packages will be released on the same day as the Rakudo sources. At the moment, packages are provided for Alpine, CentOS, Debian, Fedora, openSUSE and Ubuntu. Feel free to contribute or request new packages.

rakudo-pkg aims to provide small self-contained (no dependencies, no files outside /opt/rakudo-pkg), pre-compiled native OS packages that can be used on user’s computers, servers and –very importantly– containers. Therefor, only the Rakudo compiler and the Zef package manager are provided. Third party modules can be easily installed if desired.

From a security point of view, we like to create the builds in the open: the packages are created, checksummed and automatically uploaded from the code in this repository by Travis CI to Github Releases and Bintray Repositories.

For those users, or rather System Administrators, that prefer to build their own Rakudo packages, rakudo-pkg can be used as a build framework. Because Docker containers are used when creating native Linux packages, any platform running Docker can be used as a host, including Linux, MacOS and Windows machines.

npm install legally -g    # Make it work everywhere
legally                         # Check licenses of current directory
legally express          # Check an npm library's licenses

CharMap is unicode table viewer for Emacs. With CharMap you can see the unicode table based on The Unicode Standard 6.2.

The quickest way to check if a package is installed is to search for it with kpsewhich {package-name}.sty. So, to check for etoolbox, use

$ kpsewhich etoolbox.sty
/usr/local/texlive/2014/texmf-dist/tex/latex/etoolbox/etoolbox.sty

If it finds the package, it will output the path (just like normal which). If it doesn't find the package, it will output nothing and have a non-zero exit code.

Perhaps the most direct way to answer the question though would be to try and use the package:

\documentclass{article}
\usepackage{etoolbox}
\begin{document}
\end{document}

The above will fail if etoolbox cannot be found.

If you installed TeXLive via the Arch repositories, you can look up the installed packages in the files located in:

/var/lib/texmf/arch/installedpkgs/*.pkgs

On Manjaro there might be similar files or the same in a different (or same?) path (I don't know, because the Manjaro-Wiki includes no article about its TeXLive).

Flycheck is a modern on-the-fly syntax checking extension for GNU Emacs, intended as replacement for the older Flymake extension which is part of GNU Emacs. For a detailed comparison to Flymake see Flycheck versus Flymake.

It uses various syntax checking and linting tools to automatically check the contents of buffers while you type, and reports warnings and errors directly in the buffer, or in an optional error list.

Out of the box Flycheck supports over 40 different programming languages with more than 80 different syntax checking tools, and comes with a simple interface to define new syntax checkers.

Many 3rd party extensions provide new syntax checkers and other features like alternative error displays or mode line indicators.

Magit is an interface to the version control system Git, implemented as an Emacs package. Magit aspires to be a complete Git porcelain. While we cannot (yet) claim that Magit wraps and improves upon each and every Git command, it is complete enough to allow even experienced Git users to perform almost all of their daily version control tasks directly from within Emacs. While many fine Git clients exist, only Magit and Git itself deserve to be called porcelains.

You absolutely need to try installing multiple cursors:

https://github.com/magnars/multiple-cursors.el

It's in marmalade and melpa so just:

<pre>
M-x package-install multiple-cursors
</pre>

The Arch User Repository (AUR) is a community-driven repository for Arch users. It contains package descriptions (PKGBUILDs) that allow you to compile a package from source with makepkg and then install it via pacman. The AUR was created to organize and share new packages from the community and to help expedite popular packages' inclusion into the community repository. This document explains how users can access and utilize the AUR.

A good number of new packages that enter the official repositories start in the AUR. In the AUR, users are able to contribute their own package builds (PKGBUILD and related files). The AUR community has the ability to vote for or against packages in the AUR. If a package becomes popular enough — provided it has a compatible license and good packaging technique — it may be entered into the community repository (directly accessible by pacman or abs).

When building packages for Arch Linux, adhere to the package guidelines below, especially if the intention is to contribute a new package to Arch Linux. You should also see the PKGBUILD and makepkg manpages.

The submitted PKGBUILDs must not build applications already in any of the official binary repositories under any circumstances. Exception to this strict rule may only be packages having extra features enabled and/or patches in comparison to the official ones. In such an occasion, the pkgname array should be different.

This article aims to assist users creating their own packages using the Arch Linux "ports-like" build system, also for submission in AUR. It covers creation of a PKGBUILD – a package build description file sourced by makepkg to create a binary package from source. If already in possession of a PKGBUILD, see makepkg. For instructions regarding existing rules and ways to improve package quality see Arch packaging standards.

A PKGBUILD is a shell script containing the build information required by Arch Linux packages.

Packages in Arch Linux are built using the makepkg utility. When makepkg is run, it searches for a PKGBUILD file in the current directory and follows the instructions therein to either compile or otherwise acquire the files to build a package archive (pkgname.pkg.tar.xz). The resulting package contains binary files and installation instructions, readily installable with pacman.

Mandatory variables are pkgname, pkgver, pkgrel, and arch. license is not strictly necessary to build a package, but is recommended for any PKGBUILDs shared with others, as makepkg will produce a warning if not present.

It is a common practice to define the variables in the PKGBUILD in same order as given here. However, this is not mandatory, as long as correct Bash syntax is used.

Company is a text completion framework for Emacs. The name stands for "complete anything". It uses pluggable back-ends and front-ends to retrieve and display completion candidates.

This mode teaches you to use the proper Emacs movement keys in a
rather harsh manner.

No-easy-keys disables arrow, end, home and delete keys, as well as
their control and meta prefixes. When using any of these keys, you
instead get a message informing you of the proper Emacs shortcut
you should use instead (e.g. pressing down informs you to use C-n).

To have a specific package skipped when upgrading the system, specify it as such:

$ yaourt -Syau --ignore foo,bar,baz

For multiple packages use a space-separated list,

Beautify HTML, CSS, JavaScript, PHP, Python, Ruby, Java, C, C++, C#, Objective-C, CoffeeScript, TypeScript, Coldfusion, and SQL in Atom