From ArchWiki
Jump to navigation Jump to search


This section has a note saying it should be expanded. After reading the linked article ([ here) I don't see what needs expansion; to me it's quite clear and concise in conveying i3's concept of containers. --Pyroh (talk) 23:25, 27 July 2014 (UTC)

Well to the experienced user it may be quite clear, but personally I've found it not easy to tackle for the beginner. I'd thought of some simple examples (like a tabbed container layout with splits), as well as "focus child" which is not covered in the user's guide. Thoughts? -- Alad (talk) 23:54, 27 July 2014 (UTC)
What has spountaneously come to my mind after reading these comments, is that i3 focuses so much on clarity of official documentation that they'd probably be happy if someone reported that some section is not clear enough, possibly attaching a "patched" version or some suggestions on how to improve it. However, I understand this is not as practical as editing this article directly, so at least I guess the reason for the Expansion template should be "expanded" with more precise indications of what's required. -- Kynikos (talk) 12:35, 29 July 2014 (UTC)

xautolock -lockaftersleep

[Forward from email. -- Alad (talk) 19:02, 21 December 2015 (UTC)]

Hi, i've seen you've reverted back my changes on i3's wiki page, but i've seen that the -lockaftersleep of xautolock doesn't exist under its man.

-- Toketin Sun 20:29

The reason I've reverted the edit is because it duplicated Power management, which users of other window managers benefit from as well (I realize I didn't set the right example by posting power management tips in the BBS i3 thread ...)
Anyway, if you can confirm the option doesn't work, feel free to remove it (I can't check it right now). -- Alad (talk) 19:07, 21 December 2015 (UTC)
I have now removed the lockaftersleep option for the previously stated reason and added a link to systemd service files as I personally use these as a replacement. PhilippD (talk) 17:21, 8 July 2016 (UTC)