Replies: 2 comments
-
I have the same challenge. As time goes on, I have more and more little nuggets of config that are dependent of the OS. If your config files are fetched from a dotfile repo, and sensibly are shared across OS'es, maybe it'd be best to think of a config setup akin to Nx. Currently I'm using a flat dotfile installed as a bare git repo. It works, but for these cases, maybe having a programmable config file would be best. I've been meaning to try out https://volllly.github.io/rotz/. There's some functions for OS config. There's a few out there for sure, but this one seems dead simple. |
Beta Was this translation helpful? Give feedback.
-
The secondary config just adds a bunch of key/value pairs? Or you have more complex needs like overriding base values? In the simple case, maybe we could try to setup a |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I have multiple computers. I want them all to use nearly the same helix configuration. Therefore I set up a shared git repository for configuration files and each computer has a checkout of the
helix
branch in~/.config/helix/config.toml
. Any time I modify something about my helix configuration, I do agit push
in that directory, and the change immediately becomes available on all my computers.However, the computers have different operating systems, different terminals, and different keyboards. It would be extremely practical if it was possible to have a secondary (local) configuration file that is specific to the respective machine and its characteristics. In my specific case that file would not be shared by git, it would just be another file in the
~/.config/helix/
directory.Example:
Machine A with Ubuntu
Machine B with MacOS has
Machine C with Arch has
This would work nicely with git sparse checkouts.
Beta Was this translation helpful? Give feedback.
All reactions