Comment 7 for bug 87720
Revision history for this message
| Chris Jones (cmsj) wrote Re: config is hard coded | #7 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
It's also worth noting that since the point of this bug is to allow for arbitrary configurations of terminals, gconf is actually a very poor choice.
It may well be true that applications such as GNOME Terminal store profile data in gconf, however, they should not. It is a violation of gconf's design.
In the GConf world, everything is supposed to be a pre-ordained key - this is why there are schema files. You may have noticed that there is no way to delete a key, all you can do is unset it (which effectively means "revert to default schema value"). If we use gconf to contain our profile settings as well, we will be increasing this abuse of gconf.
As we get full profile support and some GUI options for editing them, the gconf config support in Terminator will become less and less important, I suspect.