This document does not cover the current qtile ebuild that comes from the Gentoo portage tree. It covers this ebuild that will normally be merge to funtoo-overlay soon.
Qtile is a highly configurable tiling window manager distributed under MIT license. It handles both tiling and floating layouts. It is especially a good alternative to Awesome for those who are more used to Python than Lua. Indeed, Qtile is written and configured entirely in Python. So whether you are Python guru or whether you are learning Python for a few time, Qtile is an ideal choice to get your environment fit your needs and feel. If you don't know Python, you can still stuck to the default configuration or pick out one of the configuration examples but a basic understanding of Python language is recommended though.
root # emerge -av qtile
It is generally a good idea to enable the
dbus useflag to deal with dbus messages. The
widget-* useflags are only needed if you would like to include the given widgets. These widgets are included in Qtile, but require additional dependencies. Leaving
widget-* useflags unset will remove the underlying widgets from qtile sources to avoid warnings about missing dependencies.
Very likely, you don't need to enable multiple python ABIs for qtile. To make your mind, here are the few things to know to choose the right ABI:
- Python 2.7 uses trollius, Python 3.3 uses asyncio, Python 3.4 has asyncio built-in.
- GoogleCalendar and Wlan widgets depend on packages that are python 2.7 only. If you plan to use one of these widgets, use python 2.7 ABI.
In order to run qtile with xinit, add this line to your
exec --sh-syntax --exit-with-session qtile
You might also want to pass
dbus-launch if you want respectively ConsoleKit and/or dbus support (note that the latter requires the `dbus` useflag). Your
~/.xinitrc would then look like:
~/.xinitrc- with consolekit and dbus support
exec ck-launch-session dbus-launch --sh-syntax --exit-with-session qtile
xinit to launch qtile. You can also configure a display manager instead, but this is not covered in this document.
As far as possible, when a default behavior is explained, a link to the related configuration snippet is given so that you can get more information and tweak it as you want.
When Qtile is run and no valid configuration file is found, it fallsback to the default configuration. So, the first time you run qtile, you should be welcomed with a black background and a bottom bar. On the left of this bottom bar, stands the list of your workspaces represented by the characters 'a', 's', 'd', 'f', 'u', 'i', 'o', 'p'. On the right of the bottom bar, you should see "default config" followed by the date and time.
Workspaces are highlighted in white font when windows are opened in them (against gray font when it contains no window). The current workspace is surrounded with a blue border, if you have multiple screens, workspaces currently displayed in other screens are surrounded with a gray border. You can go to a given workspace pressing
Mod4 + <workspace ID> (a, s, d, f, u, i, o or p by default). If you go to a workspace that is already displayed in another screen, workspaces will be swapped. You can move the current window to a given workspace pressing
Mod4 + Shift + <workspace ID>.
Qtile looks in the following places for a configuration file, in order: book.com/
- The location specified by the
At anytime, you can fire
Mod4 + Ctrl + r to restart qtile with your new configuration. You should also `tail -f ~/.qtile.log` to checkout errors and warnings while editing your Qtile configuration.
In order to configure your Qtile environnement, I would suggest you to start with the default config base and tweak it bit by bit:
user $ mkdir -p ~/.config/qtile user $ wget -O ~/.config/qtile/config.py https://raw.githubusercontent.com/qtile/qtile/v0.9.1/libqtile/resources/default_config.py user $ vim ~/.config/qtile/config.py
Don't forget to replace "v0.9.1" with the version you installed or it may not work.