debuglog <on|off|toggle>
set $m Mod1 bindsym $m+Shift+r restart-
Variables are directly replaced in the file when parsing. There is no fancy -handling and there are absolutely no plans to change this. If you need a more -dynamic configuration you should create a little script which generates a -configuration file and run it before starting i3 (for example in your -~/.xsession file).
Variables are directly replaced in the file when parsing. Variables expansion +is not recursive so it is not possible to define a variable with a value +containing another variable. There is no fancy handling and there are +absolutely no plans to change this. If you need a more dynamic configuration +you should create a little script which generates a configuration file and run +it before starting i3 (for example in your ~/.xsession file).
debuglog <on|off|toggle>
# Enable/disable logging -bindsym $mod+x debuglog toggle
Examples:
=== Reloading/Restarting/Exiting - -You can make i3 reload its configuration file with +reload+. You can also -restart i3 inplace with the +restart+ command to get it out of some weird state -(if that should ever happen) or to perform an upgrade without having to restart -your X session. To exit i3 properly, you can use the +exit+ command, -however you donât need to (simply killing your X session is fine as well). - -*Examples*:+
# Enable/disable logging +bindsym $mod+x debuglog toggle
bindsym $mod+Shift+r restart -bindsym $mod+Shift+w reload -bindsym $mod+Shift+e exit
You can make i3 reload its configuration file with reload. You can also +restart i3 inplace with the restart command to get it out of some weird state +(if that should ever happen) or to perform an upgrade without having to restart +your X session. To exit i3 properly, you can use the exit command, +however you donât need to (simply killing your X session is fine as well).
Examples:
=== Scratchpad - -There are two commands to use any existing window as scratchpad window. +move -scratchpad+ will move a window to the scratchpad workspace. This will make it +bindsym $mod+Shift+r restart +bindsym $mod+Shift+w reload +bindsym $mod+Shift+e exit+
There are two commands to use any existing window as scratchpad window. move +scratchpad will move a window to the scratchpad workspace. This will make it invisible until you show it again. There is no way to open that workspace. -Instead, when using +scratchpad show+, the window will be shown again, as a -floating window, centered on your current workspace (using +scratchpad show+ on +Instead, when using scratchpad show, the window will be shown again, as a +floating window, centered on your current workspace (using scratchpad show on a visible scratchpad window will make it hidden again, so you can have a keybinding to toggle). Note that this is just a normal floating window, so if you want to "remove it from scratchpad", you can simple make it tiling again -(+floating toggle+). - -As the name indicates, this is useful for having a window with your favorite +(floating toggle).
As the name indicates, this is useful for having a window with your favorite editor always at hand. However, you can also use this for other permanently running applications which you donât want to see all the time: Your music -player, alsamixer, maybe even your mail clientâ¦? +player, alsamixer, maybe even your mail clientâ¦?
Syntax:
move scratchpad -*Syntax*:+scratchpad show
move scratchpad
Examples:
There are two options in the configuration of each i3bar instance that can be changed during runtime by invoking a command through i3. The commands bar hidden_state and bar mode allow setting the current hidden_state @@ -2020,7 +2016,7 @@ bindsym $mod+Shift+b bar mode invisible bar-1
As you can see in the goal list on the website, i3 was specifically developed with support for multiple monitors in mind. This section will explain how to @@ -2043,7 +2039,7 @@ create an unlimited number of workspaces in i3 and tie them to specific screens, you can have the "traditional" approach of having X workspaces per screen by changing your configuration (using modes, for example).
To help you get going if you have never used multiple monitors before, here is a short overview of the xrandr options which will probably be of interest to you. It is always useful to get an overview of the current screen configuration. @@ -2106,7 +2102,7 @@ only what you can see in xrandr.
See also [presentations] for more examples of multi-monitor setups.
There are several things to configure in i3 which may be interesting if you have more than one monitor:
A very common thing amongst users of exotic window managers is a status line at some corner of the screen. It is an often superior replacement to the widget approach you have in the task bar of a traditional desktop environment.
When giving a presentation, you typically want the audience to see what you see on your screen and then go through a series of slides (if the presentation is simple). For more complex presentations, you might want to have some notes which only you can see on your screen, while the audience can only see the slides.
This is the simple case. You connect your computer to the video projector, turn on both (computer and video projector) and configure your X server to clone the internal flat panel of your computer to the video output:
This case is a bit harder. First of all, you should configure the VGA output somewhere near your internal flat panel, say right of it: