KConfig Bug?

Benjamin Meyer ben at meyerhome.net
Sat Jun 28 18:09:22 BST 2003

Hash: SHA1

On Saturday 28 June 2003 12:04 pm, Waldo Bastian wrote:
> On Saturday 28 June 2003 17:30, Benjamin Meyer wrote:
> > > There is no [current] way to force that it picks up the entry defined
> > > by the kdeglobals files.
> >
> > Which is why I suggested adding one :)
> I'm willing to consider that but if you look at the files again:
> > $KDEDIR/share/config/kdeglobals
> > $KDEHOME/share/config/kdeglobals
> > $KDEDIR/share/config/kmyapprc
> > $KDEHOME/share/config/kmyapprc
> If $KDEHOME/share/config/kmyapprc contains "use the entry from kdeglobals"
> ([$g] ??) it means that KConfig must still have access to the entries that
> were defined by $KDEHOME/share/config/kdeglobals, even though they may have
> been redefined by $KDEDIR/share/config/kmyapprc already. KConfig currently
> doesn't keep that information around.
> I will have a look to see how hard it is to change that in such a way that
> we don't keep too much duplicate entries in memory.
> > Kiosk users/developers would probably slaughter me if I did this.  They
> > wouldn't be able to just copy their local settings for applications into
> > the global, but would have to rename all of the groups.  But if this is
> > my only option I will start going CVS through and changing all the code.
> I don't think it's that bad. We are talking about moving options from e.g.
> konsolerc to kdeglobals and vice versa. This is NOT about copying files
> from $KDEHOME to $KDEDIR, that's what kiosk users are mostly concerned
> about.

Actually that is what I proposed  Stuff stored in $KDEHOME would have a 
different group name then stuff stored in $KDEDIR...  Using kdeglobals isn't 
a reasonable  option.  The only way it would work is to store every single 
setting in kdeglobals which I am sure is not what you want.  The reason is 
because currently there is absolutely no way to tell if a setting has a 
global default.

I don't think that when you delete a setting (that can only be set in the 
local config) it should delete the global config and when deleteEntry() is 
called it does just that, deletes the entry.  I think the current way of 
deleting the global config is incorrect.

- -Benjamin Meyer 

- -- 
Public Key: http://www.csh.rit.edu/~benjamin/public_key.asc
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org


More information about the kde-core-devel mailing list