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

Include Terminal Settings from my PowerShell profile folder or any arbitrary folder. #3529

Closed
ocalvo opened this issue Nov 11, 2019 · 2 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

@ocalvo
Copy link
Contributor

ocalvo commented Nov 11, 2019

Description of the new feature/enhancement

Customizing Terminal settings should be allowed to be loaded from my OneDrive folder or my own github repository, just like my powershell settings are or my VIM settings.

Currently, when I login into a new machine I have to merge or manually copy settings for Terminal, I don't have this problem in PowerShell or VIM as all I need to do is git clone and redirect to my settings folder.

Proposed technical implementation details (optional)

Here are some options:

  1. Allow for an arbitrary folder to be configured to read settings.
  2. Read from ~.terminal folder (but allow redirection)

After configuring the "reditected" folder, all my settings and profile are restored.

@ocalvo ocalvo added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Nov 11, 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 Nov 11, 2019
@zadjii-msft
Copy link
Member

Thanks for the suggestion! This looks like it's a /dup of #2303.

@ghost
Copy link

ghost commented Nov 14, 2019

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 Nov 14, 2019
@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 Nov 14, 2019
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to 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.
Projects
None yet
Development

No branches or pull requests

2 participants