IssueRaiser

Add support for roaming settings.json or storing it elsewhere

<hr> > **Note**: 📌 Pinned comment: **https://github.com/microsoft/terminal/issues/2933#issuecomment-536652883** <hr> # Description of the new feature/enhancement I have three different computers that I use for work. I keep my PowerShell profile in a GitHub repository and dot source it in my local PowerShell profile. That way I will only need to do a `git pull` on my profile repository to get all changes propagated on each computer. It would be great if I could do something similar with my Windows Terminal settings by simply stating in my local settings.json file that the "real" settings could be found somewhere else. (It could even be that the loaded profile acts like a base for the settings on the computer so things could be overridden, but that is a completely different issue that remains to be opened) I'm aware that I might have overlooked something here, but would love to start a discussion about this since I suspect that I'm not the only one with this "problem". # Proposed technical implementation details (optional) ```json { "$schema": "https://aka.ms/terminal-profiles-schema", "globals": { "loadProfileFrom": "C:/Source/git/profiles/terminal_profile.json" } ```

Posted by patriksvensson on Sep 27, 2019, 8:20 AM

Tags

Related issues

Raise real-world problems, find people facing the same issue, and discuss solutions.3,500 issues0 comments

support (Software)

Add support for roaming settings.json or storing it elsewhere

patriksvenssonSep 27, 2019, 8:20 AM

<hr> > **Note**: 📌 Pinned comment: **https://github.com/microsoft/terminal/issues/2933#issuecomment-536652883** <hr> # Description of the new feature/enhancement I have three different computers that I use for work. I keep my PowerShell profile in a GitHub repository and dot source it in my local PowerShell profile. That way I will only need to do a `git pull` on my profile repository to get all changes propagated on each computer. It would be great if I could do something similar with my Windows Terminal settings by simply stating in my local settings.json file that the "real" settings could be found somewhere else. (It could even be that the loaded profile acts like a base for the settings on the computer so things could be overridden, but that is a completely different issue that remains to be opened) I'm aware that I might have overlooked something here, but would love to start a discussion about this since I suspect that I'm not the only one with this "problem". # Proposed technical implementation details (optional) ```json { "$schema": "https://aka.ms/terminal-profiles-schema", "globals": { "loadProfileFrom": "C:/Source/git/profiles/terminal_profile.json" } ```

Comments (0)

No comments yet. Start the discussion.

Comment on this issue