Morph9@lemmy.zip to linuxmemes@lemmy.worldEnglish · 14 days agoPreferencelemmy.zipexternal-linkmessage-square16linkfedilinkarrow-up15arrow-down10
arrow-up15arrow-down1external-linkPreferencelemmy.zipMorph9@lemmy.zip to linuxmemes@lemmy.worldEnglish · 14 days agomessage-square16linkfedilink
minus-squaremichaelmrose@lemmy.worldlinkfedilinkEnglisharrow-up0arrow-down1·9 days agoI meant there is no particular reason to expect a gui configuration tool for a gui Window manager that isn’t expected to be dynamic to have a cli. Generally the use case is always maximize this window or always put it on a particular workspace etc. If it has any path to being addressable via bash you would check its dbus interface if any. The same feature on say i3wm also isn’t a CLI nor is it any more dynamic. Windows rules and wmctrl don’t have identical use cases although there could be overlap
I meant there is no particular reason to expect a gui configuration tool for a gui Window manager that isn’t expected to be dynamic to have a cli.
Generally the use case is always maximize this window or always put it on a particular workspace etc.
If it has any path to being addressable via bash you would check its dbus interface if any.
The same feature on say i3wm also isn’t a CLI nor is it any more dynamic.
Windows rules and wmctrl don’t have identical use cases although there could be overlap