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

Feature Request - Move profiles.json to a more accessible location #1567

Closed
cinnamon-msft opened this issue Jun 24, 2019 · 5 comments
Closed

Feature Request - Move profiles.json to a more accessible location #1567

cinnamon-msft opened this issue Jun 24, 2019 · 5 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-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@cinnamon-msft
Copy link
Contributor

Summary of the new feature/enhancement

The profiles.json file is hard to find when you don't click the Settings button within the Terminal. Let's move the default location to somewhere more accessible.
@cinnamon-msft cinnamon-msft added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Jun 24, 2019
@cinnamon-msft cinnamon-msft added this to the Backlog milestone Jun 24, 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 24, 2019
@cinnamon-msft cinnamon-msft added Area-Settings Issues related to settings and customizability, for console or terminal Product-Terminal The new Windows Terminal. and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Jun 24, 2019
@ghost ghost removed the Needs-Tag-Fix Doesn't match tag requirements label Jun 24, 2019
@cinnamon-msft cinnamon-msft mentioned this issue Jun 24, 2019
Closed
@DHowett-MSFT
Copy link
Contributor

When running unpackaged, WT saves profiles in %APPDATA%\Microsoft\Windows Terminal, which is a very windows-y place to put config files. Some people wish it would put files in your user folder ... and other people hate tools that put files in the user folder . . .

@JushBJJ
Copy link

JushBJJ commented Jun 25, 2019

Maybe add the topic #1455 into here too.

@JushBJJ JushBJJ mentioned this issue Jun 27, 2019
Closed
@miniksa miniksa mentioned this issue Jun 28, 2019
Closed
This was referenced Jul 2, 2019
Closed
Closed
@DHowett-MSFT DHowett-MSFT mentioned this issue Jul 20, 2019
Closed
@allykzam allykzam mentioned this issue Jul 31, 2019
Closed
@carlos-zamora
Copy link
Member

@DHowett-MSFT @cinnamon-msft As we approach a post-v1 world, is this even feasible anymore? Should we just close this?

@DHowett-MSFT
Copy link
Contributor

This was somewhat outmoded by /dup #2933.

@ghost
Copy link

ghost commented May 12, 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 May 12, 2020
@ghost ghost added the Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. label May 12, 2020
@zadjii-msft zadjii-msft removed this from the Terminal Backlog milestone Jan 19, 2021
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
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-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
5 participants
@carlos-zamora @DHowett-MSFT @zadjii-msft @JushBJJ @cinnamon-msft