openbox permission issue

[Kingdomcome]

in then openbox extension ~/.config is not writable by the user.  I think the dir should be owner by the user, not root.

[roberts]

Fixed. Thanks for the heads up.

[Kingdomcome]

Ive just found another issue with the openbox extension that Im amazed I hadnt noticed before.  The exention has shared libs in it, therefore needs an "l" tacked on to the end.  Thanks for the great work quick responses.

[roberts]

l added 

[jls]

How did u fix the permissions?

[roberts]

The permissions were being set on .config/openbox and not .config itself.

[jls]

launching obconf, click on dock, changing position, I get:
an error occured while saving the config file '/home/tc.config/openbox/rc.xml'
I f look in the terminal I read:
read only file system

[^thehatsrule^: removed spam]

[Kingdomcome]

everything in ~/.config/openbox is a link to /tmp/tcloop therefore not writable.  I believe the openbox extension was built to be a tce and quickly converted to tcz.  Some more massaging of the extension is probably needed to function well in the latest environments.

[roberts]

I must have had a tcz2ram.flg when I tested.
You could add it to a tcz2ram.lst until someone has the time to look further.

[jls]

roberts aren't u using anymore flwm?

[roberts]

Absolutely, I am using flwm!  Just trying to be helpful.
Whoever made this extenion sure chose a tiny font that I can hardly see.

Anyway, I made another adjustment to openbox_initmenu..
Let me know if it works now..

[Kingdomcome]

Just tested.  All files in ~/.config/openbox/ are now writable and obconf is able to write to rc.xml.    One other thing Im noticing with openbox is that immediately after boot wbar will cover any window that is in its space.  a simple refresh of wbar places it back underneath windows where it should be.  This is a very minor issue and the workaround is so easy that no problem dealing with, but I thought I would mention it anyway.  Thanks for all the great work