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

Choose your own editor for Settings #3592

Closed
AndrewR66 opened this issue Nov 15, 2019 · 3 comments
Closed

Choose your own editor for Settings #3592

AndrewR66 opened this issue Nov 15, 2019 · 3 comments
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Needs-Attention The core contributors need to come back around and look at this ASAP. Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting

Comments

@AndrewR66
Copy link

When I pick Settings in the dropdown menu, profile.json opens in Visual Studio. This is slow. I would like to open it in a smaller/faster editor. I suppose it opens in VS due to my windows file extension settings for .json files. I don't wan't to change this setting, but I would like a seperate setting where I can choose my editor.

Proposed technical implementation details (optional)

With the new feature:

  1. I will somehow pick editor for editing settings.
  2. When I choose to edit settings, profile.json opens in the editor from 1)
@AndrewR66 AndrewR66 added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Nov 15, 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 15, 2019
@DHowett-MSFT
Copy link
Contributor

Hey @AndrewR66, thanks for the request! On the balance, this seems like a huge amount of work (providing an in-terminal file association UI) for a pretty narrow use case. If you don't mind, though, why are you averse to changing your default JSON association? VS is going to be huge and take forever to load regardless of which JSON file you're opening, so it might be advantageous to just change the association everywhere.

@DHowett-MSFT DHowett-MSFT added the Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something label Nov 18, 2019
@ghost
Copy link

ghost commented Nov 22, 2019

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@ghost ghost added the No-Recent-Activity This issue/PR is going stale and may be auto-closed without further activity. label Nov 22, 2019
@ghost ghost closed this as completed Nov 25, 2019
@AndrewR66
Copy link
Author

Thank you for responding, I think I'll change my JSON association after all, like you suggest.

@ghost ghost added Needs-Attention The core contributors need to come back around and look at this ASAP. and removed Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something No-Recent-Activity This issue/PR is going stale and may be auto-closed without further activity. labels Nov 27, 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. Needs-Attention The core contributors need to come back around and look at this ASAP. Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting
Projects
None yet
Development

No branches or pull requests

2 participants