Hi,
The amount of data that is stored by for instance Mozilla under
~/.mozilla is enormous compared to the few files of wcd. Logically you
don't want all Mozilla's files in your $HOME folder.
In my $HOME directory I have 244 hidden files and directories.
> ls -a | grep '^\.' | wc -l
244
Most wcd users will have only 2 .wcd files in $HOME. I you remove those
and add a .wcd directory, the amount goes down by 1. If it is common to
have over 200 hidden files and directories in $HOME, the impact is less
than 0.5% in most cases. Is it really worth the effort? I don't mind
having 244 or 240 hidden files in $HOME. And the user always has the
option to use WCDHOME if he/she doesn't like the files in $HOME.
best regards,
Erwin
Op 04-03-09 14:37, Jari Aalto schreef:
Erwin Waterlander <water...@xs4all.nl> writes:
Hi,
Wcd already supports an alternative location via the WCDHOME environment
variable.
Noticed, that'd why I adjusted the bug report accordingly.
The Login shells are exception. Other programs would better use
~/.<program>/
An example: my $HOME contains
ls -a | grep '^\.' | wc -l
204
Any help managing that is welcomed. There are benefits in separate dirs:
- backup by directory
- version control by directory
- ignore directories from searches; find(1) etc.
Jari
---------------------------------------------------
Clarification to the previous bug report. wcd(1) contains
variable WCDHOME, so please treat (*) marked as follows:
Please store all files under user defined environment variable:
*) forget this
WCD_ROOT
*) implement this
When undefined, program would default to:
$HOME/.wcd/
*) implement these
ERROR CONDITIONS
If WCD_ROOT does not exist, program terminates and displays an error.
If default directory $HOME/.wcd/ does not exist, it is created. This
is typical behaviour (Cf. ~/.mozilla/ ~/.opera/ ...).
