reopen 708002 reassign 708002 xfce4 retitle 708002 XFCE makes gtkrc-2.0 be ignored thanks
On Wed, 15 May 2013 18:02:39 +0200 Ricardo Mones <[email protected]> wrote: > That you were using XFCE was a bit you didn't mention on your original > report. If you're _not_ using default desktop it's good to say it ;) I'm sorry. I'm new to desktop environments. Just switched to XFCE. By the way, I didn't know there was a default desktop. For ages the default X environment was a window manager and an xterm. > Nope, that doesn't work that way. Your desktop is overriding default > GTK+ behaviour, causing the problem you observe. The FAQ was probably > written way before XFCE made this decission, yet it's still right when > the desktop is not hindering GTK+ defaults. > > Your desktop should prominently document its behaviour when diverges from > library defaults. If it already did, well, you probably should know as user :) > > But you cannot pretend Sylpheed (or any other client application) to > document > each change of XFCE on top of GTK+ (or any other desktop doing such things). Yes, I absolutely agree. I have searched the web and found nothing about it. Maybe I'm a bit drowsy today. I also have been skimming at the documentation that can be accessed from the applications menu, but the section on the Settings Manager, which is I guess the component responsible for this behaviour (at least the one that stores the settings), is missing. The one on the web doesn't say anything either. Interestingly, the FAQ's only entry is exactly about changing the key bindings: http://docs.xfce.org/faq and it clearly says that one of the three ways to change them is setting gtk-can-change-accels = 1 in .gtkrc-2.0. So this is either outdated, or one is supposed to be able to use Gtk settings also in XFCE. Anyway I fail to understand how XFCE can override GTK settings for pure GTK applications. After all Sylpheed only links to GTK. Anybody please enlighten me. > > > > AFAICS none of these are Sylpheed bugs so closing this report. > > > > > > Reopening since the proposed solutions don't work for me. > > > > I have no problem if this is closed when README.Debian gets updated and > > the FAQ corrected. > > As said Sylpheed FAQ is right, and not the place to document random desktop > behaviours (which Sylpheed is not part of), so closing. If this is really not > mentioned in XFCE documentation (which I doubt) feel free to reopen again and > reassign to xfce4 package (or file a new bug for them, as you prefer). As I said, I found nothing that says XFCE makes GTK apps ignore ~/.gtkrc-2.0 nor explains what it is replaced with. And the XFCE FAQ seems to imply that gtkrc-2.0 *should* actually be respected. So this either a bug in XFCE or a serious fault in the documentation. Even if the behaviour was intended I would consider it a bug. Adding user-friendly interfaces on top of GTK so users don't have to create a gtkrc-2.0 is one thing, but this is breaking basic GTK behaviour, and a manually created a GTKrc should be respected. Maybe OK for XFCE apps, if documented, but not for all GTK apps. I am reopening and reassigning to xfce4. Anybody who knows better please reassign to the right component. So, in summary, either: - Stop XFCE ignoring ~/.gtkrc-2.0 or overriding its settings or - Document this behaviour prominently and explain how to set the traditional GTK stuff in XFCE. The latter is especially important for the GTK options that can't be set through the User Interface, like the KeyThemeName. The FAQ should the updated at the very least (the third item is wrong). I have strong bias for the first option. Regards, and thanks for your patience ;) -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
