Refresh profiles.json on load #7360

Open
opened 2026-01-31 01:01:57 +00:00 by claunia · 0 comments
Owner

Originally created by @Conner05 on GitHub (Apr 10, 2020).

Description of the new feature/enhancement

Today when I download a new shell I have to either manually add the config to profiles.json or I have to do what @shanselman suggests in his blog post Now Is The Time To Make A Fresh New Windows Terminal profiles.json.

This behavior is certainly not intuitive. Adding the ability to fetch new shells on startup would fix this weirdness.

Proposed technical implementation details (optional)

// on start
// make backup of current profiles.json in case below fails
// get all current shells
// get all shells referenced in profiles.json
// generate a new profiles.json
// add shells that do not exist
// save new profiles.json
// delete backup
Originally created by @Conner05 on GitHub (Apr 10, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> # Description of the new feature/enhancement <!-- A clear and concise description of what the problem is that the new feature would solve. Describe why and how a user would use this new functionality (if applicable). --> Today when I download a new shell I have to either manually add the config to `profiles.json` or I have to do what @shanselman suggests in his blog post [Now Is The Time To Make A Fresh New Windows Terminal profiles.json](https://www.hanselman.com/blog/NowIsTheTimeToMakeAFreshNewWindowsTerminalProfilesjson.aspx). This behavior is certainly not intuitive. Adding the ability to fetch new shells on startup would fix this weirdness. # Proposed technical implementation details (optional) <!-- A clear and concise description of what you want to happen. --> ``` // on start // make backup of current profiles.json in case below fails // get all current shells // get all shells referenced in profiles.json // generate a new profiles.json // add shells that do not exist // save new profiles.json // delete backup ```
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#7360