Now the background image is rendered in advance into one surface per screen which is then drawn on the screen. Thus relatively time-consuming scale operations can be carried out on the background image with ease.
With some layouts, this broke uppercase letters in your passwords. I think that explicit shiftlock handling is unnecessary. X11 seems to do it on its own. Here is what leads me to that conclusion: $ setxkbmap de $ xmodmap -e 'keycode 66 = Shift_Lock' $ xev Now enter a character, say "a", then press CapsLk (which is now Shift_Lock), then press "a" again. The event state is 0x1, thereby undistinguishable from normal shift.
… (Thanks xn) Fixes: #712
The Debian packaging is now hosted on Debian servers at git://git.debian.org/users/stapelberg/i3lock.git This makes life easier for Debian people. It makes life harder for you if you want to build a Debian package of the current git version. Here is how you could do that now: Build a tarball of the current git version: mkdir ../i3lock-dpkg VERSION=i3lock-$(git describe --tags) git archive --prefix=$VERSION/ --output=../i3lock-dpkg/$VERSION.tar.bz2 HEAD get the packaging: cd ../i3lock-dpkg gbp-clone git://git.debian.org/users/stapelberg/i3lock.git cd i3lock git-import-orig ../$VERSION.tar.bz2 dpkg-buildpackage
See also: http://article.gmane.org/gmane.linux.kernel/1268792 The C compiler will handle (void) as "no arguments" and () as "variadic function" (equivalent to (...)) which might lead to subtle errors, such as the one which was fixed with commit 0ea64ae4.