Closed khughitt closed 5 years ago
Whoops..Meant to post this on the sway issue tracker 😅.. It does relate to both sway and termite, but I think it may be more relevant for that tracker. Closing issue here.
Reported here: https://github.com/swaywm/sway/issues/3122
Note
This may be a termite issue, or a non-issue, but I thought I would report in full here for clarification since I suspect others are likely to run into the same issue.
Overview
When attempting to configure sway to silently create a couple terminal scratchpad instances at launch (separate issue, but also happy to hear any suggestions about plausibility / implementation), I was unable to get any rules relating to application instance or class to apply properly to the terminal application termite.
Upon closer inspection, it appears that the
window
field is set tonull
andwindow_properties
is not specified at all.For comparison, the same procedure was run with a second X-based terminal application, st, and both
window
andwindow_properties
were found to be specified as expected.Termite's lack of support for handling window class in wayland has been previously reported (1 and 2), and appears to be expected for behavior for native wayland apps.
Questions
--name
also handles specifying aWM_CLASS
property, is this also expected behavior?WM_CLASS
for native wayland apps? The fact thatwindow_properties
is handled for the non-native applications, but not native ones seems counter-intuitive and has the result that controlling the behavior of X apps is easier than controlling the behavior of wayland apps.Steps to reproduce
Starting with a clean config file (only specified terminal):
swaymsg -t get_tree > ~/sway_termite.json
swaymsg -t get_tree > ~/sway_st.json
termite window entry:
st window entry
Debug log: https://gist.github.com/khughitt/361c7bade4d06e25bca5869d42a0a890
System info: