Difference between revisions of "I3"

From ArchWiki
Jump to: navigation, search
(Installation: desc)
(Other tools: covered above)
Line 71: Line 71:
== Other tools ==
== Other tools ==
i3 currently uses [[dmenu]] as a application launcher, which is bound by default to {{Keypress|Mod1|background=#FF0}}+{{Keypress|d}}.
i3 currently uses [[dmenu]] as a application launcher, which is bound by default to {{Keypress|Mod1|background=#FF0}}+{{Keypress|d}}.
{{Pkg|i3lock}} is a screen locker inspired by {{Pkg|slock}}.
== Additional sources ==
== Additional sources ==

Revision as of 06:04, 28 January 2013

i3 is a dynamic tiling window manager inspired by wmii that is primarily targeted at developers and advanced users.

Clients (windows) are organized in a tree data structure within containers. The tree branches via horizontal or vertical splits, and containers can also be set to tabbed or stacked layouts. Floating windows are available for corner cases that don't mix well with tiling, and remain on a separate layer above the tiled windows.

See the i3 User's Guide for usage information.


i3 is located in the community repository. Installing i3 can be accomplished by choosing the i3 group, which includes the packages i3lock (a screenlocker), i3status and i3-wm. Alternatively, you can install the window manager (i3-wm) exclusively.

A status line is provided by piping text to i3bar, with i3status or any other program that writes a statusline to stdout.

Additionally, i3-gitAUR is available in the AUR.

For gnome users, see i3-gnomeAUR in AUR to add a i3 gnome session (gtk theme, gnome-keyring, notifications, gnome online accounts).

Running i3

Edit your ~/.xinitrc and add:

exec i3

If you want i3 to log its output (useful for debugging), add this line to ~/.xinitrc:

exec i3 -V >> ~/.i3/i3log 2>&1

If you use the Nvidia binary driver <302.17 you need to add the --force-xinerama flag to ~/.xinitrc. A detailed explanation can be found at i3wm.org.

exec i3 --force-xinerama

Status bar

The internal status bar, i3-wsbar, was deprecated and replaced by i3bar in i3 v4.0.

New method: i3bar

Unlike i3-wsbar, which requires dzen2, i3bar does not have any dependecies other than i3-wm. It can be used to view information generated by conky or i3status. For example (as of version 4.1):

bar {
    output            LVDS1
    status_command    i3status
    position          top
    mode              hide
    workspace_buttons yes
    tray_output       none
    font -misc-fixed-medium-r-normal--13-120-75-75-C-70-iso10646-1

    colors {
        background #000000
        statusline #ffffff

        focused_workspace  #ffffff #285577
        active_workspace   #ffffff #333333
        inactive_workspace #888888 #222222
        urgent_workspace   #ffffff #900000

For further information see the Configuring i3bar section of the official User Guide.

Comparison of i3bar and dzen2

This comparison of i3bar and dzen2 only takes into account how well the two programs can handle the input from conky or i3status.

Program Color Codes Formatting Special Fonts Dock Trayer
i3bar Yes No, right aligned No (UTF8 only) Yes Yes
dzen2 Yes No, left aligned Yes Yes (the svn version) No

Though development of i3bar is very active and support for custom formatting and fonts has been announced, dzen2-svn has an edge over i3bar (as of August 7th).

Other tools

i3 currently uses dmenu as a application launcher, which is bound by default to Template:Keypress+Template:Keypress.

Additional sources