Replies: 3 comments 4 replies
-
You don't NEED to edit it with chezmoi. Once you add a file to chezmoi with
In the diagram here, replace
|
Beta Was this translation helpful? Give feedback.
-
You may be interested in Handle configuration files which are externally modified. The example is for Linux but it also applies to Windows (with a few path tweaks). The basic idea is to store in the config file in chezmoi's source state and symlink it to its expected location. When the program then modifies its own config it will actually modify the file stored in your dotfiles repo. I can only assume that you would also need sufficient privileges to create symlinks with your user account, either by enabling Developer Mode or manually granting your account the privilege. I don't use this personally, despite primarily using Windows, as I don't mind editing the files manually, and I also use a template for my VS Code config. |
Beta Was this translation helpful? Give feedback.
-
In addition to other's comments. I suggest better start looking others configs here I too recently discovered chezmoi and I'm also on windows. I suggest spending some time through the docs as well. The docs is really good. From what I've learnt till now is that chezmoi has a different system of it's own to manage dotfiles. Like renaming files for e.g. |
Beta Was this translation helpful? Give feedback.
-
I work mainly on Windows, and I'm considering moving to chezmoi to manage my config rather than my current "do it all manually" mess 😉 But my problem is that for a lot of the config I want to manage, I don't edit dotfiles directly. The applications I use include a "config manager" of some sort, which stores config in a file somewhere. So for me, the idea of editing the chezmoi-managed copy of my config and then applying that to my application doesn't really feel natural (and in cases where there is a GUI for changing settings, it's significantly less user friendly).
For example, Windows Terminal has a settings GUI, and stores its config in
%LOCALAPPDATA%\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\LocalState\settings.json
. The file is manually editable, but the GUI is far easier. How would I set things up so that I can manage Windows Terminal settings with chezmoi, while still using the GUI to make changes? I'm fine with a workflow that involves having to do some sort of "compare current settings with saved ones, then sync chezmoi with the live settings" process.Other applications that do this include
git
(git config
),pip
(pip config
), and VS Code. So it's not an uncommon model, and I'm sure people have solved it, but I couldn't find a good discussion in the docs (which is probably my fault for not knowing where to look).I don't have any immediate need to integrate this requirement with the more complex features of chezmoi, like templates. Right now I don't even have a need for things like that, although I'm sure I'll find uses as I get more familiar with it 🙂 I'd understand if advanced features were incompatible with using app-provided settings management, although I'd like it if I could set things up so that I didn't wreck my setup if I forgot and (for example) accidentally used an app config command on something I was using templates for.
Beta Was this translation helpful? Give feedback.
All reactions