We are still actively working on the spam issue.

GNU/Linux ricing

From InstallGentoo Wiki
(Redirected from Ricing)
Jump to: navigation, search
At first you'd think it was Windows XP, but look closer.... This is the power of customization that the GNU/Linux system provides. (KDE on OpenSUSE)

GNU/Linux distributions are well known for their ability to customize the way they work to a large degree. The purpose of this page is to give the reader some ideas on what can be customized and how.

What does /g/ use?

Let's be honest: this is why you're really here.

A common ricing configuration which can be seen among /g/ users in desktop threads usually features some of the software below. All of these can be installed from a repository via your package manager, be it your distro's main one or a user one (the AUR in Arch), or built from source. Do a little searching to find out.

Desktop Environments

GNOME 3.10
Cinnamon 2.0
XFCE 4.10

A desktop environment is a complete suite of software designed to maintain a certain experience in a Linux environment. It will contain a display manager, window manager, session manager, file manager, and various other default applications that a user may find useful (web browser, audio player, etc). Good DEs are modular and will allow the users to mix and match and switch any of their modules with another of their choice. Running multiple Desktop Environments without uninstalling others is one mere file edit away.

Primarily, what a DE means to you is how you interact with the desktop. Systems such as Windows and Macintosh only have one user interface to use, however GNU/Linux systems have many User Interfaces to choose from.

Despite the many options, a desktop environment is not a required part of a Linux experience, although most Linux distributions will include one by default. It is entirely possible to have a working graphical environment without installing a desktop environment, instead opting to only use a window manager and utilities that you require, and many users choose to do this.

Fairly lightweight DE with a Windows-like UI. If you want something with a bit more features and eyecandy, this may be for you.
GNOME is extremely polarizing. If you like the Windows 8 Start Screen and similar touch interfaces, try it out. Else, stay clear.
GNOME fork with a traditional desktop. Very customizable and feature.
XFCE is a less resource-intensive DE. If you want something that runs fast and allows for lots of customization without giving up too many features, this DE is for you.
LXDE is the most minimal DE around. If you are running on a toaster supercluster or just need the most battery life out of your freedom device, and are too lazy/dumb to setup a WM, LXDE is the only correct choice.
A fork of LXDE that uses the QT framework, however more heavy on system resources than LXDE and XFCE.
Fork and continuation of GNOME 2 for those who prefer it.

Display Managers

A display manager is what might typically be thought of as a "login screen". It will prompt you to choose a user to log in as, as well as specify a session to be used, which allows you to switch between desktop environments easily.

  • LightDM
  • SLiM - The SliM project has been abandoned, and is not fully compatible with systemd, including logind sessions. Consider using a different Display manager.
  • SDDM - Display manager used with KDE and LXQt.
  • GDM - Display manager used in GNOME.
  • LXDM - Works with almost all window managers.

Window Managers

Currently most GNU/Linux distributions use the X Window System for drawing the desktop (with Wayland being planned to replace it later). The X.org Server is the most common implementation of the X Window System. It is designed to be modular and highly customizable. One of the results of this design is that X.org doesn't manage windows. Instead it depends on a special client application called a window manager. The window manager (WM in short) moves and resizes windows, among other things, often in response to user input. Window managers also do much more, like automatic window layout, compositing, drawing decorations, drawing panels, providing multiple workspaces, and so on.

Window managers can be divided into these three categories:

Compiz's expo plugin. As most window managers, it allows for multiple workspaces, as seen here.
  • Stacking (aka floating) - Provides the traditional desktop metaphor used in commercial operating systems like Windows and OS X. Windows act like pieces of paper on a desk, and can be stacked on top of each other.
  • Compositing - Provide a buffer for each window to draw on and then compose those buffers together creating the desktop image. This type of window manager allows use of semitransparent windows.
  • Tiling - These "tile" the windows side-by-side so that none are overlapping. They usually make very extensive use of key-bindings and have less (or no) reliance on the mouse. Tiling window managers may be manual, offer predefined layouts, or both.
    • Static tiling - WMs such as ratpoison always use a set number of equal size tiles, and the tiles do not move
    • Dynamic tiling - WMs such as awesome allow you to change the layout of the tiles, the number of tiles onscreen, and other things. it should be noted that awesome also has a stacking mode in addition to many tiling configurations.

Many WMs contain both stacking and tiling modes, and the behavior can be switched by the user. This is sometimes known as a "dynamic" wm (not to be confused with dynamic tiling)

It's also possible for WMs that don't tile windows to use a separate application that works together with the main window manager to automatically tiles windows (for example: pytyle).

Finally, there are also composite managers such as xcompmgr that work together with a non-compositing WM making it compose windows, allowing for effects such as transparency and drop shadows.

List of window managers and similar tools

List of window managers in Arch Wiki


  • Awesome - Despite looking pretty bad of the box, it's a very popular tiling window manager. It is completely scriptable in Lua, which makes it one of the most powerful and customizable window managers once you get around to programming the configuration file.
  • dwm - Doesn't come with a simple configuration file; instead, you're supposed to edit config.h and recompile dwm yourself. At least they make an effort to keep the code well-commented and under 2000 SLOC. Not for beginners as they themselves claim to want to "keep the userbase small and elitist", though you might want to give this a shot if you know C and you're willing to hack into the source code.
  • i3 - One of the most popular window managers around, i3 is a fork of wmii that strives to fix the latter's convoluted code and documentation problems. Looks good out of the box and the configuration is simple and intuitive. It also provides a great amount of documentation on the webpage. Good for beginners and developers/hackers alike.
  • monsterwm - Tiny but monstrous! Currently under 700 lines of code including the configuration file.


  • ratpoison - Minimal WM without the need of a mouse.
  • bspwm
  • xmonad - A minimal window manager written and configured in Haskell.
  • herbstluftwm - A manual tiling window manager.


  • Compiz - A compositing WM being developed since 2006. It uses OpenGL (AIGLX). It is know for having a lot functionality and providing many interesting effects. However, it can cause problems if the graphics are faulty.
  • KWin - A compositing WM used in KDE. It's comparable in feature set to compiz.
  • Mutter - The default window manager for GNOME.
  • Xfwm - The default window manager for XFCE.


PyTyle used together with Compiz, tiling 5 terminal windows.

Compositing tools (for stacking/tiling WMs)

  • Xcompmgr
  • Compton - Forked of Xcompmgr
  • Picom - picom is a compositor based on Dana Jansens' version of xcompmgr (which itself was written by Keith Packard). It includes some improvements over the original xcompmgr, like window frame opacity and inactive window transparency.

Tiling tools (for non-tiling WMs)

For some more information on this topic, see: this page.


There are two main toolkits you need to concern yourself with styling: GTK and Qt. Luckily, there are themes for both that will adapt to the other. So find a theme for whichever toolkit your distro uses prominently. For KDE based distros, that's Qt. For everything else, that's GTK.

GTK Themes

There are a number of great themes. All of these are GTK3 compatible. To apply them, see GTK Theming.

  • Numix - A very popular theme.
The Numix theme

Qt Themes

Set Qt themes with the qtconfig tool.

  • GTK+ - Builtin. Adapts to the theme that GTK is using.


KDE allows you to download most of the following by simply going into the relative setting, press the "get new" button, and search for the name.


  • KFaenza - Port of the famous Faenza theme to KDE.
  • Oxyfaenza - An elegant modification of Faenza.
  • Nitrux
  • FaenK - Incomplete theme, needs KFaenza installed to display all the icons.
  • kAwOken - Nice light/dark gray icon theme.


A gif of KDE with QtCurve theme, Numix Icons and Homerun launcher

Plasma themes

  • Diamond - Transparency, almost unusable without composing turned off.
  • Caledonia - Dark "flat" suite, include a Plasma theme, icons and custom colors.
  • uniq - Another suite, includes a window decorator, a qtqurve theme and custom colors.
  • Produkt - A dark, flat theme with minimal transparency and nice custom tray icons.

Window Decorations


  • Infinality - This font patchset can give you some of the best font rendering there is (if not the best) on GNU/Linux. It comes with a gigantic set of patched fonts, many being optional.
  • fontconfig-ultimate - fontconfig-ultimate is an aggregate of configuration files, patches, scripts and source packages, meant to add more presets to fontconfig and, in most cases, improve the existing font rendering. It is supposed to be used with freetype+infinality.


Article Tweaking Linux.


See: Screensavers

Ricing Code Snippets


External Resources

Ricing guide by z3bra

Nanami's Win7 & Firefox List

Dotshare.it (Contains many helpful terminal application configurations)

Funroll loops