> My point is that there are TONS of configuration dirs in your home > dir, mixed with data/docs dirs, and unsorted files. And even though > the configs are usually hidden, they should be inside one main hidden > dir, instead of just being clogging your home dir.
Why not modify fvwm so that it looks in yet another location on startup? It could even look there last, it wouldn't hurt anything, would it? Seems like this is the only part that would need to be done code-wise, the rest could be implemented in the fvwm config file and not require any code changes. Then any ambitious individual that wanted to implement this xdg compliance stuff could feel free to provide a base config somewhere. Though, technically, if you wanted a clean home directory, you could make your home directory be something like /home/username/.config, then make your .bashrc or whatever cd you to /home/username - but then if you do use something that automatically puts your home directory on your desktop it would look strange. But even then you could remove that link and make one to /home/username instead... Not sure how well it would integrate with the 'home' feature inside file dialogs. > > For instance, if you try to find the config dir for that particular > program, and you don't know its name, then doing ls -la is useless, > because (at least in my case) the terminal buffer overflows, so you > can't see the first dirs that show up. Unless you pipe it to less, but > then you loose the colour formating.. OT, but you can ls --color=always | less and you don't lose the color formatting. But if you do that you can't grep for '^\.' because the escape sequences for color codes get in the way... Do you have a link to the actual standards document? I'm curious what it entails... --s.r.d.
