Tutorials/Using Other Window Managers with Plasma: Difference between revisions
(split lists) |
(Marked this version for translation) |
||
| Line 25: | Line 25: | ||
* Most window managers do not have their own compositors, and therefore lack features like animations and transparency. If such effects are desired, a compositor is required - refer to [https://wiki.archlinux.org/index.php/Xorg#Composite Arch Wiki] for options.</translate> | * Most window managers do not have their own compositors, and therefore lack features like animations and transparency. If such effects are desired, a compositor is required - refer to [https://wiki.archlinux.org/index.php/Xorg#Composite Arch Wiki] for options.</translate> | ||
<translate> | <translate> | ||
<!--T:58--> | |||
** Compositors can also help with screen tearing, however check first if you can resolve it with your video drivers, as this will be a more performant solution in most cases. | ** Compositors can also help with screen tearing, however check first if you can resolve it with your video drivers, as this will be a more performant solution in most cases. | ||
| Line 110: | Line 111: | ||
When you first start i3, its default global configuration (at <code>/etc/i3/config</code>) will start i3-config-wizard, which will provide a dialog for Mod key selection and generate the user local configuration at <code>~/.i3/config</code>. | When you first start i3, its default global configuration (at <code>/etc/i3/config</code>) will start i3-config-wizard, which will provide a dialog for Mod key selection and generate the user local configuration at <code>~/.i3/config</code>. | ||
<!--T:59--> | |||
If you wish to maintain the same configuration across users (they can still override it with their own local config), remove the wizard invocation from the global configuration file and use it directly. | If you wish to maintain the same configuration across users (they can still override it with their own local config), remove the wizard invocation from the global configuration file and use it directly. | ||
<!--T:60--> | |||
The following i3 window rules will help you with notifications and some other plasma windows: | The following i3 window rules will help you with notifications and some other plasma windows: | ||
{{Input|1=<nowiki>for_window [title="Desktop — Plasma"] kill; floating enable; border none | {{Input|1=<nowiki>for_window [title="Desktop — Plasma"] kill; floating enable; border none | ||
| Line 140: | Line 143: | ||
</nowiki>}} | </nowiki>}} | ||
===Configure Plasma=== | ===Configure Plasma=== <!--T:61--> | ||
<!--T:62--> | |||
You may get into issues related with the "Activities" feature - activating it via keyboard shortcuts (some of which are also used by i3, like "Meta + Q") seems to make i3 unresponsive. Removing Activity related global shortcuts seems to resolve this. | You may get into issues related with the "Activities" feature - activating it via keyboard shortcuts (some of which are also used by i3, like "Meta + Q") seems to make i3 unresponsive. Removing Activity related global shortcuts seems to resolve this. | ||
<!--T:63--> | |||
To get the Plasma provided pager display desktops as i3bar, set '''Pager Settings''' > '''General''' > '''Text display''' to "Desktop name" | To get the Plasma provided pager display desktops as i3bar, set '''Pager Settings''' > '''General''' > '''Text display''' to "Desktop name" | ||
| Line 157: | Line 162: | ||
==Hints and Tips== <!--T:43--> | ==Hints and Tips== <!--T:43--> | ||
===DBus=== | ===DBus=== <!--T:64--> | ||
<!--T:45--> | <!--T:45--> | ||
Since Meta key handling is in part performed by KWin, you will have to handle these shortcuts manually when you switch to a different window manager. | Since Meta key handling is in part performed by KWin, you will have to handle these shortcuts manually when you switch to a different window manager. | ||
<!--T:65--> | |||
You can open some Plasma components with DBus commands. You can use this to map corresponding keybindings to DBus commands. To find a specific DBus command, you can look at <code>dbus-monitor</code> or <code>qdbusviewer</code> while you invoke the component in a standard Plasma set-up. | You can open some Plasma components with DBus commands. You can use this to map corresponding keybindings to DBus commands. To find a specific DBus command, you can look at <code>dbus-monitor</code> or <code>qdbusviewer</code> while you invoke the component in a standard Plasma set-up. | ||
<!--T:66--> | |||
More info on meta key handling: | More info on meta key handling: | ||
<!--T:67--> | |||
* [https://www.reddit.com/r/kde/comments/6wn5lk/bind_meta_key_alone_to_do_something/ Reddit post describing the ''Meta key - KWin'' relation] | * [https://www.reddit.com/r/kde/comments/6wn5lk/bind_meta_key_alone_to_do_something/ Reddit post describing the ''Meta key - KWin'' relation] | ||
<!--T:68--> | |||
* [https://zren.github.io/2019/03/04/activate-any-widget-with-meta-key Blog post describing the ''DBus - Component'' relation] | * [https://zren.github.io/2019/03/04/activate-any-widget-with-meta-key Blog post describing the ''DBus - Component'' relation] | ||
| Line 177: | Line 186: | ||
* Open Application Launcher {{Input|1=<nowiki>qdbus org.kde.plasmashell /PlasmaShell org.kde.PlasmaShell.activateLauncherMenu</nowiki>}} | * Open Application Launcher {{Input|1=<nowiki>qdbus org.kde.plasmashell /PlasmaShell org.kde.PlasmaShell.activateLauncherMenu</nowiki>}} | ||
<!--T:69--> | |||
* Open Krunner {{Input|1=<nowiki>qdbus org.kde.kglobalaccel /component/krunner org.kde.kglobalaccel.Component.invokeShortcut 'run command'</nowiki>}} | * Open Krunner {{Input|1=<nowiki>qdbus org.kde.kglobalaccel /component/krunner org.kde.kglobalaccel.Component.invokeShortcut 'run command'</nowiki>}} | ||
<!--T:70--> | |||
* Open logout confirmation screen {{Input|1=<nowiki>qdbus org.kde.ksmserver /KSMServer org.kde.KSMServerInterface.logout -1 -1 -1</nowiki>}} | * Open logout confirmation screen {{Input|1=<nowiki>qdbus org.kde.ksmserver /KSMServer org.kde.KSMServerInterface.logout -1 -1 -1</nowiki>}} | ||
| Line 184: | Line 195: | ||
For i3, you can map a keybinding with the '''bindsym''' command. Use <code>--no-startup-id</code> to prevent the command from generating "i3" entries in the task manager. | For i3, you can map a keybinding with the '''bindsym''' command. Use <code>--no-startup-id</code> to prevent the command from generating "i3" entries in the task manager. | ||
<!--T:49--> | |||
Example: | Example: | ||
{{Input|1=<nowiki>bindsym $mod+Shift+e exec --no-startup-id <command></nowiki>}} | {{Input|1=<nowiki>bindsym $mod+Shift+e exec --no-startup-id <command></nowiki>}} | ||
<!--T:71--> | |||
If you want to map the modifier key itself, use the '''bindcode''' command - you have to specify the keycode generated by the key, which you can get via the <code>xev</code> utility. | If you want to map the modifier key itself, use the '''bindcode''' command - you have to specify the keycode generated by the key, which you can get via the <code>xev</code> utility. | ||
<!--T:72--> | |||
Example for the Meta key: | Example for the Meta key: | ||
{{Input|1=<nowiki>bindcode 133 --release exec --no-startup-id <command></nowiki>}} | {{Input|1=<nowiki>bindcode 133 --release exec --no-startup-id <command></nowiki>}} | ||
Revision as of 05:54, 27 January 2020
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 is required - refer to Arch Wiki for options.
- Compositors can also help with screen tearing, however check first if you can resolve it with your video drivers, as this will be a more performant solution in most cases.
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 /usr/bin/startplasma-x11 DesktopNames=KDE Name=Plasma (i3) Comment=Plasma by KDE w/i3
- 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.
Configure i3
When you first start i3, its default global configuration (at /etc/i3/config) will start i3-config-wizard, which will provide a dialog for Mod key selection and generate the user local configuration at ~/.i3/config.
If you wish to maintain the same configuration across users (they can still override it with their own local config), remove the wizard invocation from the global configuration file and use it directly.
The following i3 window rules will help you with notifications and some other plasma 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 for_window [class="plasmashell" window_type="notification"] floating enable, border none, move right 700px, move down 450px, no_focus
If you are using a non-English installation of Plasma, you need to find out what the exact window title of the Desktop is. One way is to do this is with wmctrl -l.
Instead of adding
for_window [title="Desktop — Plasma"] kill; floating enable; border none
add the name of the window to the i3 config. This example uses the German Plasma installation.
for_window [title="Arbeitsfläche — Plasma"] kill; floating enable; border none
Configure Plasma
You may get into issues related with the "Activities" feature - activating it via keyboard shortcuts (some of which are also used by i3, like "Meta + Q") seems to make i3 unresponsive. Removing Activity related global shortcuts seems to resolve this.
To get the Plasma provided pager display desktops as i3bar, set Pager Settings > General > Text display to "Desktop name"
Bspwm configuration
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.
Hints and Tips
DBus
Since Meta key handling is in part performed by KWin, you will have to handle these shortcuts manually when you switch to a different window manager.
You can open some Plasma components with DBus commands. You can use this to map corresponding keybindings to DBus commands. To find a specific DBus command, you can look at dbus-monitor or qdbusviewer while you invoke the component in a standard Plasma set-up.
More info on meta key handling:
Some examples:
- Open Application Launcher
qdbus org.kde.plasmashell /PlasmaShell org.kde.PlasmaShell.activateLauncherMenu
- Open Krunner
qdbus org.kde.kglobalaccel /component/krunner org.kde.kglobalaccel.Component.invokeShortcut 'run command'
- Open logout confirmation screen
qdbus org.kde.ksmserver /KSMServer org.kde.KSMServerInterface.logout -1 -1 -1
For i3, you can map a keybinding with the bindsym command. Use --no-startup-id to prevent the command from generating "i3" entries in the task manager.
Example:
bindsym $mod+Shift+e exec --no-startup-id <command>
If you want to map the modifier key itself, use the bindcode command - you have to specify the keycode generated by the key, which you can get via the xev utility.
Example for the Meta key:
bindcode 133 --release exec --no-startup-id <command>
For Bspwn, you need to use the bspc program. See Arch Linux wiki for more information.
More Information
- Window managers (Wikipedia)
- Window managers (Arch Linux wiki)
- Desktop environment (Wikipedia)
- Desktop environment (Arch Linux wiki)