Jump to navigation Jump to search
Based on wmii, tiling/floating.
- https://github.com/Airblader/i3 - i3-gaps
- YouTube: i3wm: Jump Start (1/3) - configuration guides
- YouTube: i3 screencast: containers and the tree data structure
- YouTube: i3 Window Manager Overview
- YouTube: i3 - An Improved Tiling Window Manager
i3-msg exec application # start your application on the workspace where it was called
- https://github.com/greshake/i3status-rust - a feature-rich and resource-friendly replacement for i3status, written in pure Rust. It provides a way to display "blocks" of system information (time, battery status, volume, etc) on the i3 bar. It is also compatible with sway.
- https://github.com/RasmusLindroth/i3keys - lists all the keys that are bound to some action in i3 or sway, and all keys that are not bound to any actions.
- How do I find the criteria for use with i3 config commands like for_window (e.g. to force splashscreens and dialogs to show in floating mode)?
- https://github.com/kenyonj/i3-create-config - created in an effort to allow the better organization of an i3 config file. Currently there is no way to include extra files in the main ~/.i3/config file.
bindsym $mod+n exec i3-msg move to container workspace $(($(wmctrl -d | wc -l) + 1)) # move to next numbered workspace whether existing or empty
- https://github.com/cameronleger/i3-workspacer - simplifying large amounts of i3 workspaces with naming and infinite* workspace traversal
- https://github.com/Chimrod/i3_workspaces - allow you to configure your workspace easily. I use it for setting a wallpaper to each workspace, or launch application on some workspaces.
- https://web.archive.org/web/20160420173541/http://www.kelvinblog.tk/i3wm-restore-layout - "i3 can only swallow new windows, but not existing ones. ... I use xdotool to unmap all visible windows and map them again (Mapping a window means to let the WM manage it). This is the script I use"
- https://github.com/joepestro/i3session - remembers what's running in your i3 workspaces by saving a session file (in ~/.i3/session). It is then able to restore the running processes (and their simple orientation) to one or more workspaces. Since i3session executes i3 commands sequentially (tree traversal), changing focus during restore will affect where clients open. By default, the i3-nagbar will appear during restore with a message to remind you of this.
- https://github.com/pitkley/i3nator - Tmuxinator for the i3 window manager. It allows you to manage what are called "projects", which are used to easily restore saved i3 layouts (see Layout saving in i3) and extending i3's base functionality by allowing you to automatically start applications too.
- https://github.com/JonnyHaystack/i3-resurrect - Simple solution to saving and restoring i3 workspaces
- https://github.com/jamesofarrell/i3-swallow - used to swallow (send to the scratchpad) a terminal window after a blocking application is run in i3.
..num . | select(.visible and .focused).num+1) if ([(. | select(.visible == true) | select(.focused == true).num)+1] as $desk | [..num] as $array | $array | contains($desk)) == true then "one" else "two" end
- https://github.com/olemartinorg/i3-alternating-layout - Scripts to open new windows in i3wm using alternating layouts (splith/splitv) for each new window