Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| xfce:thunar:faq [2025/05/04 08:36] – [How to use trash functionality on BTRFS volumes?] alexxcons | xfce:thunar:faq [2025/05/07 07:57] (current) – [How to give unique identifiers to specific Thunar windows?] alexxcons |
|---|
| ===== How to give unique identifiers to specific Thunar windows? ===== | ===== How to give unique identifiers to specific Thunar windows? ===== |
| |
| If you e.g. want to open Thunar Windows on specific screens/workspaces, it might make sense to start separate Thunar processes and force a specific application-name for them. That will allow moving these instances, based on the chosen name. In order to use separate processes, ''dbus-launch'' has to be used to accomplish that: | If, for example, you want to open a Thunar window on a specific screen or workspace, it might make sense to start separate Thunar processes and force a specific application-name for them. This will allow moving these instances, based on the chosen name. In order to use separate processes, the command ''dbus-launch'' has to be used to accomplish this: |
| |
| * XOrg: '' $dbus-launch thunar --class My-Custom-Name'' | * XOrg: '' $dbus-launch thunar --class My-Custom-Name'' |
| * Wayland: '' $dbus-launch thunar --name My-Custom-Name'' | * Wayland: '' $dbus-launch thunar --name My-Custom-Name'' |
| |
| Note that each Thunar instance will create its own dbus service, usually the second instance will fail to acquire the dbus-service-name. As well, several other Thunar internal mechanics will be multiplied, leading to a much bigger total memory footprint. | Note that each Thunar instance will create an isolated D-Bus session environment. Additionally, several other Thunar internal mechanics will be multiplied, leading to a much bigger total memory footprint. |
| |
| ---- | ---- |