GNOME Bugzilla – Bug 85068
Add WM class/name setting to profile
Last modified: 2007-02-02 07:35:30 UTC
Package: gnome-terminal Severity: critical Version: 2.0.0 Synopsis: GNOME-Terminal2 ignores some arguments Bugzilla-Product: gnome-terminal Bugzilla-Component: general Description: Appears like the GNOME-Terminal2 ignores those arguments on startup: gnome-terminal --class=foo gnome-terminal --name=foo gnome-terminal --disable-factory --name=foo The WM_CLASS property is not affected by those arguments. Btw: Shouldn't the WM_CLASS settings go into the profile editor? Tell me weither you agree with that and if you are going to implement this or if I should checkout the current code base to get my hands on it... ------- Bug moved to this database by unknown@bugzilla.gnome.org 2002-06-12 15:31 ------- Reassigning to the default owner of the component, hp@redhat.com.
If class/name exists it would be a feature of the profile, yes, rather than a command line arg. You'd have to find some space in the dialog though, and rearrange a bunch of code since there's a bit in a 32-bit int for each preference, and at the moment the integer is full. ;-)
This needs to be collated with all the other requests-for-preferences to see how many we have and which we should add.
Why not just set the WM name to the name of the profile? e.g. for profile "Default", xprop should report: WM_CLASS(STRING) = "gnome-terminal", "Default"
Could do that, I suppose. Though profile names are UTF-8 and window classes have to be Latin-1.
Doesn't make much sense anymore in the days of gnome-terminal with tabs...
It had tabs in 2002 ;-)
2002, me still maintaining IceWM, giving this up for GNOME-2.0 with its new philosophie..., weird days...