Morph9@lemmy.zip to linuxmemes@lemmy.worldEnglish · 1 month agoPreferencelemmy.zipexternal-linkmessage-square72fedilinkarrow-up1215arrow-down139
arrow-up1176arrow-down1external-linkPreferencelemmy.zipMorph9@lemmy.zip to linuxmemes@lemmy.worldEnglish · 1 month agomessage-square72fedilink
minus-squaremichaelmrose@lemmy.worldlinkfedilinkEnglisharrow-up1arrow-down1·28 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