Config file does not support referring to home directory using `~` about rosenpass HOT 3 CLOSED

Is this actually a bug?

1. I think that ~ expansion is done by the shell and most programs do not do expansion on paths provided in their config files.
2. Also, the value of ~ depends on the user who runs the command.
3. I personally would not even be quite sure if I were always able to correctly identify the string to which ~ expands.

@blipp What do you think about that?

from rosenpass.

I had a talk with @koraa yesterday and we think that the following would be a good solution:

1. substitute ~\ and ~/ at the start of a path with the content of the $HOME environment variable (implemented in #250)
2. do not substitute anything else
3. provide the tooling to create config files from shell (see #247)

I will start to implement that.

from rosenpass.

@blipp This issue has been closed as port of the corresponding PR (v.i.). Feel free to reopen, add to the discussion or open another issue!

from rosenpass.