Making the prm project path a configuration parameter about prm HOT 3 CLOSED

Just to be clear here: you are talking about (what results in) a sort of categorization within prm, to keep work and personal projects separated in prm itself – not about where you place your own source code, right?

Basing prm's data-path on an environment variable sounds like a good idea, regardless.

from prm.

Yes, I am talking about a categorization within prm.
I will make a pull request with the parameterized path. The thing that should be decided before that though is the name of the env variable.

The first thing which comes to my mind is:
PRM_PATH

and if it isn't set, then it will default to the current value: $HOME/.prm/
That way we will keep compatibility and there will be a default setting.
Thoughts ?

from prm.

Good.

Sounds great – it's precisely what came to my mind as well.

from prm.