Scenario: input_dir contains many input files for symlinking (e.g. vimrc) as well as compilation (e.g. bashrc). Dotfiles manager currently happily handles these files, placing them in OUTPUT_DIR or ~.
As a user, I want to place additional input files in input_dir alongside these existing input files, and have them compiled (or linked) to a directory beneath OUTPUT_DIR. I want this to be done by convention rather than explicitly needing to run dfm a second time with a different OUTPUT_DIR than the first.
Example file: Docker settings.json which belongs in ~/.docker/
Possible solutions:
Directories under input_dir will be nested similarly beneath OUTPUT_DIR, e.g. input_dir/.config/Code/User/settings.json will correspond to OUTPUT_DIR/.config/Code/User/settings.json
Handle this as an additional dfm call in dotfiles.sh (not ideal)
Assumptions:
A given dotfile's location is the same on different OSes.
NOTE: this isn't true of VS Code's settings.json. On Linux, this file lives in ~/.config/Code/User/, whereas on MacOS its location is in ~/Library/Application Support/Code/User/. One possible way to handle this as an exercise for the user would be to symlink input_dir/Library/Application Support/Code/ to input_dir/.config/Code in the input files repository.
Scenario:
input_dircontains many input files for symlinking (e.g.vimrc) as well as compilation (e.g.bashrc). Dotfiles manager currently happily handles these files, placing them inOUTPUT_DIRor~.As a user, I want to place additional input files in
input_diralongside these existing input files, and have them compiled (or linked) to a directory beneathOUTPUT_DIR. I want this to be done by convention rather than explicitly needing to rundfma second time with a differentOUTPUT_DIRthan the first.Example file: Docker
settings.jsonwhich belongs in~/.docker/Possible solutions:
input_dirwill be nested similarly beneathOUTPUT_DIR, e.g.input_dir/.config/Code/User/settings.jsonwill correspond toOUTPUT_DIR/.config/Code/User/settings.jsondfmcall in dotfiles.sh (not ideal)Assumptions:
settings.json. On Linux, this file lives in~/.config/Code/User/, whereas on MacOS its location is in~/Library/Application Support/Code/User/. One possible way to handle this as an exercise for the user would be to symlinkinput_dir/Library/Application Support/Code/toinput_dir/.config/Codein the input files repository.