[FEATURE] OS specific profiles (actually this time)

[flying-sheep]

Is your feature request related to a problem? Please describe.

I currently have this, and have to remember to do bombadil link -p $nu.os-info.name every time.

[profiles.linux.dots]
nushell-scripts = { source = "nushell/scripts", target = ".config/nushell/scripts" }
nushell-config = { source = "nushell/config.nu", target = ".config/nushell/config.nu" }
nushell-env = { source = "nushell/env.nu", target = ".config/nushell/env.nu" }
nushell-plugin = { source = "nushell/plugin.nu", target = ".config/nushell/plugin.nu" }

[profiles.macos.dots]
nushell-scripts = { source = "nushell/scripts", target = "Library/Application Support/nushell/scripts" }
nushell-config = { source = "nushell/config.nu", target = "Library/Application Support/nushell/config.nu" }
nushell-env = { source = "nushell/env.nu", target = "Library/Application Support/nushell/env.nu" }
nushell-plugin = { source = "nushell/plugin.nu", target = "Library/Application Support/nushell/plugin.nu" }

Describe the solution you'd like
#229 was closed with the introduction of the os variable, which can’t replace profiles, as variables can’t be used in bombadil.toml.

Describe alternatives you've considered

1. We could also make pre-set variables (like os) available in bombadil.toml and interpolate settings, like this:

   [settings.dots]
   nushell-scripts = { source = "nushell/scripts", target = "{% if os == 'linux' %}.config{% else %}Library/Application Support{% endif %}/nushell/scripts" }
   ...

2. [FEATURE] Allow using standard directories #258, maybe in combination with alternative 1. (i.e. instead of the syntax in #\258, just allow target = "{{ dirs.config }}/nushell/scripts")

Additional context
N/A

[oknozor]

What you are asking for is actually the XDG Base Directory Specification.

I really don't like the idea of having templates in bombadil.toml. A templating engine driven by a set of config files that are themselves templates, that's a bit too much I think.

That said, adding some path variable which could be red in bombadil.toml would be ok as long as those are builtin.

Step 1 - Define a viable bombadil path variable format ({{CONFIG_DIR}}|$CONFIG_DIR/mydot.conf, resolved at link time.
Step 2 - Implement path resolution using the dirs crate

[iandol]

I would love to use bombadil but I do need to manage dotfiles across macOS/Linux/Win and manual profiles isn't ideal -- rotz another dotfile manager handles this really well (something like if we could [settings.linux.dots] / [settings.macos.dots] in bombadil.toml ), but rotz has no LOTR references 😢

Another awesome option would be hostname specific dots: [settings.hostnameX.dots] to apply files for a specific machine only automatically without the need of another profile.