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: Make profile.json easily portable between machines and accessible #2040

Closed
jadeallenx opened this issue Jul 19, 2019 · 1 comment
Closed

Feature Request: Make profile.json easily portable between machines and accessible #2040

jadeallenx opened this issue Jul 19, 2019 · 1 comment
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

@jadeallenx
Copy link

Summary of the new feature/enhancement

Currently profile.json is stored in the "roaming" application location which makes storing a "common" profile to be shared across all Windows Terminal installs difficult.

Proposed technical implementation details (optional)

Please enable a mechanism to look for/load profile.json from a location which can be easily shared using a service like OneDrive or Dropbox so that it acts more like "just another dot file" I can easily synchronize/share among all of the Windows installs I use on a day to day basis.

Thanks
@jadeallenx jadeallenx added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Jul 19, 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 Jul 19, 2019
@DHowett-MSFT
Copy link
Contributor

#1567 😄

@DHowett-MSFT DHowett-MSFT added the Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. label Jul 20, 2019
@ghost ghost removed the Needs-Tag-Fix Doesn't match tag requirements label Jul 20, 2019
@DHowett-MSFT DHowett-MSFT added Needs-Tag-Fix Doesn't match tag requirements and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Jul 20, 2019
@ghost ghost removed the Needs-Tag-Fix Doesn't match tag requirements label Jul 20, 2019
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
2 participants
@jadeallenx @DHowett-MSFT