Tutorials/Using Other Window Managers with Plasma: Difference between revisions
ChristianW (talk | contribs) ('single user' is a separated item for translation) |
ChristianW (talk | contribs) (Marked this version for translation) |
||
Line 26: | Line 26: | ||
==Using Another Window Manager with Plasma == <!--T:9--> | ==Using Another Window Manager with Plasma == <!--T:9--> | ||
===Single User: Using System Settings=== | ===Single User: Using System Settings=== <!--T:40--> | ||
<!--T:10--> | <!--T:10--> |
Revision as of 15:26, 15 March 2019
Introduction
KWin is the default window manager (WM) in Plasma and has lot of features, but it only supports floating windows. Plasma lets you use another window manager, such as i3, bspwm or any other tilling window manager.
Most window managers require few, if any, changes to their configuration files.
Some considerations to be aware of when using another window manager:
- Tiling window managers may have problems with components like panels. For some configurations, certain options will help alleviate issues
- Most window managers do not have their own compositors, and therefore lack features like animations and transparency. If such effects are desired, a compositor such as compton is required
Using Another Window Manager with Plasma
Single User: Using System Settings
This is the simplest method, but only affects the user for which it is added.
- Create a shell script (kde-i3.sh as an example), containing the following
#!/bin/sh export KDEWM=/usr/bin/i3
Replace /usr/bin/i3 with the path to the window manager desired.
- Start System Settings
- Select Startup and Shutdown
- Select Autostart
- Click the Add script button below the list
- Enter the location of the script created earlier, or use the folder icon to use a dialog to find it. Click OK, the script will be added to the list
- In the Run On column, select Before Session Startup from the drop down list
- The chosen window manager will be used the next time you log in
System Wide: Adding an XSession
If superuser (root) access is available, a new session file for X.org can be created.
This has several advantages: the alternate session is available to all users of the system, and changing back to KWin is as simple as logging out and back in.
To add a session for an alternate window manager as superuser:
- Copy the existing Plasma session file
cp plasma.desktop plasma-i3.desktop
- Using a text editor, open the file and change the Exec line, and optionally the Description
[Desktop Entry] Type=XSession Exec=env KDEWM=/usr/bin/i3 DesktopNames=KDE Name=Plasma (i3) Comment=Plasma by KDE w/i3 X-KDE-PluginInfo-Version=5.14.4
- The display manager must be restarted, most easily by rebooting
I3 configuration
Installation
Before starting the configuration, you should make sure i3 or i3-gaps are installed on your system. If they are not, use your package manager or Discover to install one of these two packages. You should also install a compositor such as "compton", since unlike KWin, i3 doesn't ship with an integrated compositor.
Create a default i3 configuration
.i3/config
or .config/i3/config
), you can skip this step.
Open a console and type i3-config-wizard
. This command opens a small window that will help you create a configuration file.
Some i3 keybindings can be used to provide better integration with Plasma.
# Open logout confirmation screen with $mod+e bindsym $mod+Shift+e exec qdbus org.kde.ksmserver /KSMServer org.kde.KSMServerInterface.logout -1 -1 -1 # Open krunner with $mod+d bindsym $mod+d exec qdbus org.kde.kglobalaccel /component/krunner org.kde.kglobalaccel.Component.invokeShortcut 'run command'
Some i3 window rules help you to have notifications and some other plasma windows as floating windows:
for_window [title="Desktop — Plasma"] kill; floating enable; border none for_window [class="plasmashell"] floating enable; for_window [class="Plasma"] floating enable; border none for_window [title="plasma-desktop"] floating enable; border none for_window [title="win7"] floating enable; border none for_window [class="krunner"] floating enable; border none for_window [class="Kmix"] floating enable; border none for_window [class="Klipper"] floating enable; border none for_window [class="Plasmoidviewer"] floating enable; border none for_window [class="(?i)*nextcloud*"] floating disable
bspwm
For the most part, bspwm requires little additional configuration.
- A single Plasma panel, in most cases, is detected properly and bspwm will not place windows in its space. If the panel ends up presenting a problem, or when using multiple panels, the following may be added to .bspwmrc
bspc config top_padding size
where size is the size of the panel in pixels. Also valid are bottom_padding, left_padding, and right_padding. As many of these directives may be used as necessary for multiple panels.