From: Nathaniel T. <nd...@nt...> - 2004-02-18 00:18:20
|
I'm using a self-compiled rox 2.1.0 on a linux-based system. As far as I have discovered it is not possible to avoid a non-hidden directory ("~/Choices") being used to hold configs after user modification of settings. i) I suggest all such config files/dirs should by default be hidden: almost any user knows that the config for rox should live at .rox* so there will not be a problem finding it if wanted. If all or even a few programs didn't hide their configs a homedir would be a terrible mess! Also, using such a general name as Choices stands a good chance of conflict. ii) If for some reason you are adamant that rox should default to a non-hidden config dir, it would be very good if this could easily be changed to being hidden. In spite of my liking of Rox, I _do_ want to configure it, yet I really hate having extra directories sitting there! This is almost enough to put me off. Finally, it seems _really good_. The recent changes of kde terminology (e.g. directory -> folder) and interface (e.g. permissions dialogue a la microsoft) have driven me back to icewm with non-kde apps. Rox is ever so neat and quick, and doesn't try to hide the form of the commands it is `graphicising'. So, thanks, and long may it be developed! Nathaniel |