I’ve noticed that handling of relative paths in config.yaml is inconsistent, which makes it difficult to have a self contained library and beets configuration. It’d be nice if either this was consistent, or if we could use some form of templating scheme, i.e. string.format or string.Template, to access the most common paths. It could be worthwhile to provide a new type when plugins interact with the config to handle this transparently for their options as well, giving them an absolute path.
From what I’ve seen (where BEETSDIR is the path where config.yaml lives):
- directory: relative to
- library: relative to
- pluginpath: relative to
- importfeeds: m3u: relative to
- importfeeds: m3u_multi: relative to
- alternatives: relative to
Any thoughts on the cleanest way to address this? I was going to start working on a pull request, but would like to determine the correct approach.