No description
Find a file
Vincent Bernat 3b3dd0863d quake: new Quake module that handles awesome restart gracefully
The previous RC file is moved as a module. We don't rely on the fact
that the next window to be managed after spawning a new terminal will
be this terminal. Instead, we rely on terminal name to know if we need
to manage them. For each console, we have a manage hook that tries to
identify if the window to manage is the console. In this case, it is
transformed and fitted as a Quake console.

Moreover, we clean things that look like QuakeConsole but that are not
because we already have one. For example, when switching from a
two-screen setup to a single-screen setup.
2012-07-15 12:44:46 +02:00
bin Initial commit. 2012-07-07 00:26:35 +02:00
lib quake: new Quake module that handles awesome restart gracefully 2012-07-15 12:44:46 +02:00
rc quake: new Quake module that handles awesome restart gracefully 2012-07-15 12:44:46 +02:00
themes theme: rename files for better coherency 2012-07-07 11:35:39 +02:00
.gitignore bindings: add the ability to do a screenshot 2012-07-15 00:21:32 +02:00
.gitmodules Initial commit. 2012-07-07 00:26:35 +02:00
rc.lua theme: use less colors 2012-07-14 19:48:19 +02:00
README.md theme: rename files for better coherency 2012-07-07 11:35:39 +02:00
xsession xsession: remove dedicated logs for awesome 2012-07-11 20:04:04 +02:00

Vincent Bernat's awesome configuration

This is my awesome configuration. It does not exactly feature the same keybindings as the default configuration. I don't recommend using it by you can pick anything you need in it.

I rely on machine hostname for some configuration parts (see rc/start.lua) for the most important part.

Here some of the things you may be interested in:

  • It is modular. I am using config as a table to pass different things between "modules".
  • In rc/start.lua, there is a xrun function which runs a program only if it is not already running. Instead of relying on tools like ps, it looks at the list of the connected clients with xwininfo. Seems reliable.
  • I use a light transparency effect to tell if a window has the focus or not. It needs a composite manager.
  • I use a Python script bin/build-wallpaper to build the wallpaper to be displayed. There is a random selection and it works with multihead setup. It seems that classic tools are now able to change the wallpaper per screen and therefore, the script may seem a bit useless but I keep it.
  • I am using xautolock + i3lock as a screensaver. Nothing fancy but I reuse the wallpaper built above.
  • In rc/apparance.lua, you may be interested by the way I configure GTK2 and GTK3 to have an unified look. It works and it does not need gnome-control-center.
  • I am sharing tags between screen with sharetags. I am also giving names to tags: I access them with something like config.tags.emacs.