Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: Option to change location of profiles.json #1455

Closed
logonoff opened this issue Jun 23, 2019 · 9 comments
Closed

Feature Request: Option to change location of profiles.json #1455

logonoff opened this issue Jun 23, 2019 · 9 comments
Labels
Area-Settings Issues related to settings and customizability, for console or terminal Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Product-Terminal The new Windows Terminal. Resolution-Won't-Fix We're just really obstinate about this. There's probably a good reason.

Comments

@logonoff
Copy link

logonoff commented Jun 23, 2019

Summary of the new feature/enhancement

Going though local appdata is hard and it'd be nice if you could change where it fetches the config file. a usecase could be people who have dotfiles repos to place their config in the user dir or config folder instead of making a symlink

Proposed technical implementation details (optional)

Maybe put the path of it in a json file and have it configurable via a gui?

@logonoff logonoff added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Jun 23, 2019
@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Jun 23, 2019
@fredrikaverpil
Copy link

fredrikaverpil commented Jun 24, 2019

I would like to symlink ~\dotfiles\profiles.json to ~\AppData\Local\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\RoamingState\profiles.json but I am curious about that 8wekyb3d8bbwe identifier in the path.

What is it for and will it change?

@kumarharsh
Copy link

I think 8wekyb3d8bbwe identifier is a fixed string (perhaps related to it's Store ID or something similar), and won't change.

@Cologler
Copy link

I guess 8wekyb3d8bbwe is the store publisher id of Microsoft.

@DHowett-MSFT
Copy link
Contributor

We're probably not going to do this. A symbolic link will work. The identity, 8wek..., is based on the name used to sign the app bundle. This one means "Microsoft." It won't change.

@DHowett-MSFT DHowett-MSFT added Area-Settings Issues related to settings and customizability, for console or terminal Product-Terminal The new Windows Terminal. Resolution-Won't-Fix We're just really obstinate about this. There's probably a good reason. and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Jun 27, 2019
@ghost ghost removed the Needs-Tag-Fix Doesn't match tag requirements label Jun 27, 2019
@franjozen
Copy link

The problem with a symbolic link is that the terminal doesn't react to the settings changing.

@fredrikaverpil
Copy link

fredrikaverpil commented Aug 14, 2019

@franjozen are you sure?
I am 90% sure my terminal reacts to changes immediately when editing the profile and I have a symlink set up to my dotfiles. I can check once I am at my computer.

@franjozen
Copy link

franjozen commented Aug 16, 2019

@fredrikaverpil Yes, I've created the symlink like this:
new-item -itemtype symboliclink -path .\ -name profiles.json -value ..\..\..\..\..\dotfiles\WindowsTerminal\profiles.json
Nothing happens when I save, I have to restart Terminal to see the changes.

@fredrikaverpil
Copy link

@franjozen oh, it seems I have the very same behavior here as on your end.

@Antorell
Copy link

Antorell commented Sep 12, 2020

Sorry for bumping this closed post. Posting if somebody hasn't figured yet.
You need to create a junction/SymbolicLink to the LocalState folder that link to a folder that contains the WT settings.json instead of linking the settings.json directly, if you want the settings to update right away when you edit the settings.json.

Something like this:
New-Item -Force -Type Junction -Path "$ENV:LOCALAPPDATA\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\LocalState" -Value "Path\to\myfolder\withtheWTsettings.json\insideit"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Settings Issues related to settings and customizability, for console or terminal Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Product-Terminal The new Windows Terminal. Resolution-Won't-Fix We're just really obstinate about this. There's probably a good reason.
Projects
None yet
Development

No branches or pull requests

7 participants