

Per-output history of the focused workspaces. Is implemented in the previous_workspace() function by keeping a Switch to the previous workspace on the same output. Switch to the workspace on the next output and one keybinding to Back and forth workspace switching on the same output With the workspace back_and_forth command, we can ask i3 to Implement a Quake console The quake_console() function implements a drop-down consoleĪvailable from any workspace. If needed to an empty workspace or to one with the same applicationĪlready running. Workspace_exclusive() function monitors new windows and moves them Which is allowed to “intrude” into any workspace. It implements the following components: Make a workspace exclusive to an application When a workspace contains Emacs or Firefox, I would like otherĪpplications to move to another workspace, except for the terminal Each feature is self-contained into aįunction. Instead of maintaining a script for each feature, I have centralized Of other tiling window managers, window swallowing to put a newĪpp on top of the terminal launching it, and cycling between Users have published many scripts to extend i3:Īutomatic layout and window promotion to mimic the behavior Libraries exist for this purpose in several Moreover, as high-level features may be opinionated,ĭelegating them to small, loosely coupled pieces of code keeps them While this is not as powerful as an embedded language, it is enoughįor many cases. Therefore only be considered if the benefit outweighs the additionalĬomplexity, and we encourage users to implement features using the Generally happy with the feature set of i3 and instead focus onįixing bugs and maintaining it for stability. I3 philosophy is to keep a minimal core and let the user implementsĭo not add further complexity when it can be avoided. My configuration is quite similar to the default one and has i3 can also saveĪnd restore layouts, which is quite a powerful feature. Tentatives and get a chance to familiarize myself. Window managers but I did try to get my setup pristine of these You can find many scripts trying to emulate other tiling

Other workspaces are using a tabbed layout. I set up a split layout for Emacs and a few terminals, but most of the Tree with many useless nested containers. At first, it is not unusual to find yourself with a complex It can feel quite overwhelming as you need to visualize the tree in I3 is more flexible with its ability to build any layout on the fly, Without thinking too much as they are ordered. Moreover, you can cycle through the various windows When a new window is added, the behavior is quite These layouts can be tuned a bit, but you mostly stick to aĬouple of them.

They usually feature a largeĪrea for the main window and another area divided among the remaining Most of the other tiling window managers, including the awesome Tree representation of the previous screenshot.
