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 |
From: Ken H. <kh...@so...> - 2004-02-18 00:35:38
|
See http://rox.sourceforge.net/phpwiki/index.php/HidingChoices There seems to be a new trend to put things in one hidden dir .local or .config but let them all be visible once you are in that dir. I think there is also a freedesktop.org spec on all this. Nathaniel Taylor wrote: > 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 > > > ------------------------------------------------------- > SF.Net is sponsored by: Speed Start Your Linux Apps Now. > Build and deploy apps & Web services for Linux with > a free DVD software kit from IBM. Click Now! > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click > _______________________________________________ > rox-devel mailing list > rox...@li... > https://lists.sourceforge.net/lists/listinfo/rox-devel -- Ken Hayber (kh...@so...) Huntington Beach, CA |
From: Alastair P. <ala...@li...> - 2004-02-18 03:23:55
|
On Wed, 2004-02-18 at 13:32, Ken Hayber wrote: > See http://rox.sourceforge.net/phpwiki/index.php/HidingChoices >=20 > There seems to be a new trend to put things in one hidden dir .local or .= config but let them all be visible once you are in that dir. I think there= is also a freedesktop.org spec on all this. That seems to be how the OB3 config works Regards, Alastair --=20 (o< - A l a s t a i r P o r t e r //\ =20 V_/_ ala...@li... |
From: Guido S. <gu...@ar...> - 2004-02-18 09:09:43
|
Am 18.02.2004 02:32:14 schrieb(en) Ken Hayber: > See http://rox.sourceforge.net/phpwiki/index.php/HidingChoices >=20 > There seems to be a new trend to put things in one hidden dir .local =20 > or .config but let them all be visible once you are in that dir. I =20 > think there is also a freedesktop.org spec on all this. .local/share and .config are defaults, which can be overridden via the XDG_DATA_HOME and XDG_CONFIG_HOME env variables. There also =20 XDG_DATA_DIRS and XDG_CONFIG_DIRS for system configs. Basically those are like CHOICESPATH split into 4 variables. XDG is =20 basically a KDE spec, so a little overengineering is to be expected. A practical example: XDG_DATA_HOME=3D"$HOME/.local/share" XDG_CONFIG_HOME=3D"$HOME/.config" XDG_DATA_DIRS=3D"/usr/local/share/:/opt/gnome/share:/opt/kde/share:/usr/=20 share" XDG_CONFIG_DIRS=3D"/usr/local/share/etc/xdg:/etc/xdg CHOICESPATH=3D"$XDG_CONFIG_HOME:$XDG_CONFIG_DIRS" A setup compatible with current ROX conventions: XDG_DATA_HOME=3D"$HOME/Choices" (not sure this is a good idea, but what =20 else?) XDG_CONFIG_HOME=3D"$HOME/Choices" XDG_DATA_DIRS=3D"/usr/local/share:/opt/gnome/share:/opt/kde/share:/usr/=20 share" XDG_CONFIG_DIRS=3D"/usr/local/share/Choices:/usr/share/Choices CHOICESPATH=3D"$XDG_CONFIG_HOME:$XDG_CONFIG_DIRS" |
From: Thomas L. <ta...@ec...> - 2004-02-21 17:38:13
|
On Wed, Feb 18, 2004 at 10:15:01AM +0200, Guido Schimmels wrote: > Am 18.02.2004 02:32:14 schrieb(en) Ken Hayber: > >See http://rox.sourceforge.net/phpwiki/index.php/HidingChoices > > > >There seems to be a new trend to put things in one hidden dir .local > >or .config but let them all be visible once you are in that dir. I > >think there is also a freedesktop.org spec on all this. > > .local/share and .config are defaults, which can be overridden via > the XDG_DATA_HOME and XDG_CONFIG_HOME env variables. There also > XDG_DATA_DIRS and XDG_CONFIG_DIRS for system configs. > Basically those are like CHOICESPATH split into 4 variables. XDG is > basically a KDE spec, so a little overengineering is to be expected. The reason is to allow a sysadmin to change the system config location without breaking user's scripts. ie, users should only set the _HOME variables, and sysadmins should set the _DIRS ones. -- Thomas Leonard http://rox.sourceforge.net tal00r at ecs.soton.ac.uk tal197 at users.sourceforge.net GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1 |
From: Guido S. <gu...@ar...> - 2004-02-18 08:49:54
|
Am 18.02.2004 02:13:40 schrieb(en) Nathaniel Taylor: > 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. http://rox.sourceforge.net/phpwiki/index.php/HidingChoices >>>The Choices directory annoys me... can I hide it? Yes, this is controlled by the CHOICESPATH environment variable, which =20 is a colon-separated list of directories to search for choices. Choices =20 are saved into the first directory. See The Choices System for details. =20 You probably want to put something like this in one of your shell's =20 initialization files (i.e. ~/.bash_profile if you use bash): export CHOICESPATH=3D${HOME}/.Choices:/usr/local/share/Choices:/usr/=20 share/Choices You have to log out and in again for this to take effect for all =20 programs.<<< |
From: Matthew W. O. <mat...@we...> - 2004-02-18 18:22:12
|
-- Guido Schimmels <gu...@ar...> wrote (on Wednesday, 18 February 2004, 09:55 AM +0200): > Am 18.02.2004 02:13:40 schrieb(en) Nathaniel Taylor: > >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. > > http://rox.sourceforge.net/phpwiki/index.php/HidingChoices > > >>>The Choices directory annoys me... can I hide it? > > Yes, this is controlled by the CHOICESPATH environment variable, which > is a colon-separated list of directories to search for choices. Choices > are saved into the first directory. See The Choices System for details. > You probably want to put something like this in one of your shell's > initialization files (i.e. ~/.bash_profile if you use bash): > > export CHOICESPATH=${HOME}/.Choices:/usr/local/share/Choices:/usr/ > share/Choices I've been doing this since I started using ROX -- I like the single directory with all configs, but I don't want to accidently click into it when in ROX (it looks too much like my Apps directory!). It has the advantage of being hidden along with that of eliminating the number of hidden directories in your home environment. -- Matthew Weier O'Phinney http://weierophinney.net/matthew/ |