No description
Find a file
Vincent Bernat 8a78f68e77 i3-companion: reblacken at 88 line-length
And tell flake8 that's OK.
2021-07-17 09:14:45 +02:00
bin i3-companion: reblacken at 88 line-length 2021-07-17 09:14:45 +02:00
dotfiles i3-companion: push bluetooth status to polybar 2021-07-16 00:52:54 +02:00
.flake8 i3-companion: reblacken at 88 line-length 2021-07-17 09:14:45 +02:00
.gitignore xsettings: remove reference to xsettingsd.local 2020-02-08 16:44:17 +01:00
config i3: Firefox WebRTC indicator has lost its role, match on title 2021-07-16 11:33:09 +02:00
README.md polybar: add back disk module 2021-07-11 11:27:37 +02:00
ws-emacs.json i3: use a saved layout to spawn Emacs workspace 2021-07-05 21:59:05 +02:00

Vincent Bernat's i3 configuration

This is my i3 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.

Here some of the things you may be interested in:

  • 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 xss-lock with i3lock as a screensaver. It relies on standard X screensaver handling (and therefore is easy for application to disable) and also supports systemd inhibitors. Nothing fancy but I reuse the wallpaper built above. A notification is sent 10 seconds before starting.

  • There is an i3-companion (in bin/) which I use to implement whatever does not match what I want in i3. I prefer to not have many Python binaries running.

  • There is a Quake console included.

  • Many stuff is handled by systemd. The session is still expected to be handled by Xsession but we invoke a custom xsession.target which binds to graphical-session.target. i3 will then invoke i3-session.target for stuff needing i3 to run.

Also, I am using my custom terminal (vbeterm). You can also find the sources on GitHub.

Requirements

Required Debian packages to make everything work can be found in my Puppet configuration. Also, some daemons may be compiled from git HEAD (dunst and polybar) to get access to some features.