|
@ -12,12 +12,10 @@ Priority: optional |
|
|
Section: x11 |
|
|
Section: x11 |
|
|
Depends: ${shlibs:Depends}, ${misc:Depends} |
|
|
Depends: ${shlibs:Depends}, ${misc:Depends} |
|
|
Description: a slightly improved version of slock |
|
|
Description: a slightly improved version of slock |
|
|
Key features of i3 are correct implementation of Xinerama (workspaces are |
|
|
|
|
|
assigned to virtual screens, i3 does the right thing when attaching new |
|
|
|
|
|
monitors), XrandR support (not done yet), horizontal and vertical columns |
|
|
|
|
|
(think of a table) in tiling. Also, special focus is on writing clean, |
|
|
|
|
|
readable and well documented code. i3 uses xcb for asynchronous |
|
|
|
|
|
communication with X11, and has several measures to be very fast. |
|
|
|
|
|
. |
|
|
|
|
|
Please be aware i3 is primarily targeted at advanced users and developers |
|
|
|
|
|
and that you’re currently trying an alpha version (which may contain bugs). |
|
|
|
|
|
|
|
|
i3lock improves slock by making it fork() and therefore combinable with |
|
|
|
|
|
commands to suspend your computer. Additionally, instead of turning of |
|
|
|
|
|
your screen via DPMS and/or displaying a black screen, i3lock displays a |
|
|
|
|
|
white screen so you can see if your computer failed to resume from suspend |
|
|
|
|
|
or if your screen is just locked. Also, when entering a wrong password, |
|
|
|
|
|
i3lock does not call XBell(). This is important because i3lock/slock think |
|
|
|
|
|
you've entered a password when resuming from suspend, at least sometimes. |