i3 in openEuler User Guide

What Is i3?

i3 is a tiling window manager.

The interface of i3 is as follows:

i3 layout

Usage

i3 is based on the X Window protocol. Therefore, you need to install X Server first.
```
dnf in xorg-x11-server
```
As i3 is only a window manager, it does not contain the components required in a complete Linux desktop environment. You need to install some basic components.
```
dnf in xorg-x11-drv-*  lightdm lightdm-gtk
```

Install i3 components.

dnf in i3 i3status i3blocks i3lock i3blocks-contrib \
    xfce4-terminal xcompmgr acpi dmenu

Start lightdm after the installation is complete.
```
sudo systemctl start lightdm
```
After the session manager is displayed, enter the user name and password to log in to the i3 desktop.

Basic Operations in i3

(Mod is usually mapped to the Windows key on a Windows-compatible keyboard.)

Mod+d: Open dmenu for quickly starting processes.
Mod+Enter: Open a terminal.
Mod+↑/↓/←/→: Move focus between windows.
Mod+Shift+q: Close the window of focus.
Mod+Shift+r: Hot load the configuration file.
Mod+Shift+e: Exit i3.
Mod+Shift+l: Lock the screen.

For more operation guides, see i3 Documentation.

Bug Catching

Buggy Content

Bug Description

Submit As Issue

It's a little complicated....

I'd like to ask someone.

Just a small problem.

I can fix it online!

Bug Type

Specifications and Common Mistakes

● Misspellings or punctuation mistakes;

● Incorrect links, empty cells, or wrong formats;

● Chinese characters in English context;

● Minor inconsistencies between the UI and descriptions;

● Low writing fluency that does not affect understanding;

● Incorrect version numbers, including software package names and version numbers on the UI.

Usability

● Incorrect or missing key steps;

● Missing prerequisites or precautions;

● Ambiguous figures, tables, or texts;

● Unclear logic, such as missing classifications, items, and steps.

Correctness

● Technical principles, function descriptions, or specifications inconsistent with those of the software;

● Incorrect schematic or architecture diagrams;

● Incorrect commands or command parameters;

● Incorrect code;

● Commands inconsistent with the functions;

● Wrong screenshots.

Risk Warnings

● Lack of risk warnings for operations that may damage the system or important data.

Content Compliance

● Contents that may violate applicable laws and regulations or geo-cultural context-sensitive words and expressions;

● Copyright infringement.

We may contact you through email in regard to the bug fixing solution. You will also be notified through email if you win any prize during the activity.