Make default prefix for relative path configurable
(was: Interpret a dot-relative path distinctly)
The purpose of this issue is to decide whether to give special meaning to dot-relative paths. Currently, a dot-relative path (e.g., ./foo/bar
) is treated the same as a basic relative path (e.g., foo/bar
). In other words, both are resolved starting from the start path. We could instead treat a dot-relative path as relative to the current working directory of the process (equivalent to ~+/foo/bar
).
The tricky part is what to do about a standalone .
. We could say that a path is only dot-relative if it has at least two segments. In other words, .
would be resolved starting from the start parameter, whereas ./
would be resolved starting from current working directory of the process. However, this could turn out to be too much nuance.