This section has a note saying it should be expanded. After reading the linked article ([http://i3wm.org/docs/userguide.html#_tree 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)
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)
Docking station, automation of screen management
Pulec (talk) 14:00, 3 July 2018 (UTC) Stealing from this http://sergeiturukin.com/2017/07/03/laptop-dock-archlinux.html, write some short udev rule and script to handle not only monitors
Installation - Fonts
Maybe there should be a hint that one needs a good font otherwise i3 will be unreadable. E.g. if you are on a fresh arch install and you didn't install anything that adds any fonts, i3 just is unuseable. -- —This unsigned comment is by Balance (talk) 16:07, 7 September 2020. Please sign your posts with ~~~~!
- I actually did that with this edit, but it was rolled back by User:Lahwaacz --Madpet (talk) 16:56, 7 September 2020 (UTC)
Currently i3 prioritizes non-accessible terminals that do not function properly with orca and speech-dispatcher for blind users.
The order of terminals in the /usr/bin/i3-sensible-terminal file can be modified to the following:
mate-terminal gnome-terminal terminator xfce4-terminal x-terminal-emulator urxvt rxvt termit Eterm aterm uxterm xterm roxterm termite lxterminal terminology st qterminal lilyterm tilix terminix konsole kitty guake tilda alacritty hype
Doing so will allow the accessible terminals to default on launch rather than terminals like xterm that will not work by default.
- Files in
/usr/bin/should not be edited by users, the changes would be overwritten on package upgrades. If you want to change the order of terminals, ask upstream. -- Lahwaacz (talk) 19:53, 15 November 2020 (UTC)
Add tip to use dmenu (instruction for shouldn't be wildly differentin
e.g. for modkey + c
bindsym $mod+c exec --no-startup-id clipmenu