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.

Sign up for GitHub

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

Jump to bottom

How to change the settings.json file location ? #8652

Closed
marco20240618 opened this issue Dec 25, 2020 · 6 comments
Closed

How to change the settings.json file location ? #8652

marco20240618 opened this issue Dec 25, 2020 · 6 comments
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@marco20240618
Copy link

Description of the new feature/enhancement

Proposed technical implementation details (optional)

By default, the settings.json is in C:\Users\xxx\AppData\Local\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\LocalState\settings.json.
How to change the default location ?
@marco20240618 marco20240618 added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Dec 25, 2020
@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 Dec 25, 2020
@skyline75489
Copy link
Collaborator

I don't think you can do that now. See #2933 .

@DHowett
Copy link
Member

DHowett commented Dec 25, 2020 •
edited
Loading

/dup #2933 thanks Chester!

@ghost
Copy link

ghost commented Dec 25, 2020

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost ghost closed this as completed Dec 25, 2020
@ghost ghost added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed 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 Dec 25, 2020
@KalleOlaviNiemitalo
Copy link

@DHowett, you mistyped the issue number. Does that affect any automation?

@DHowett
Copy link
Member

DHowett commented Dec 27, 2020 •
edited
Loading

Nope, just my flawless sense of style correctness. Thanks :)

@ghost
Copy link

ghost commented Dec 27, 2020

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@similar-issues-ai similar-issues-ai bot mentioned this issue Aug 1, 2024
Closed
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@DHowett @skyline75489 @marco20240618 @KalleOlaviNiemitalo