Display a specific error for not finding the default profile #1782

Open
opened 2026-01-30 22:36:22 +00:00 by claunia · 0 comments
Owner

Originally created by @zadjii-msft on GitHub (Jun 20, 2019).

Originally assigned to: @zadjii-msft on GitHub.

From #1343

Even more correct would be to specifically display a message that there was no default profile (though that might be too much for this release).

  • If we load the profiles.json and the defaultProfile doesn't exist in the list of profiles, we should display an error specific to that failure case.
  • We should also use the first profile as the default temporarily. We'll need to make sure not to persist this runtime change.

Maybe also:

  • Check if the commandline is a path to a single executable, and if it is, warn if it doesn't exist? Dunno how we'd get the first arg from the commandline easily but it could totally be done.
Originally created by @zadjii-msft on GitHub (Jun 20, 2019). Originally assigned to: @zadjii-msft on GitHub. From #1343 > Even more correct would be to specifically display a message that there was no default profile (though that might be too much for this release). * [ ] If we load the `profiles.json` and the `defaultProfile` doesn't exist in the list of profiles, we should display an error specific to that failure case. * [ ] We should also use the _first_ profile as the default _temporarily_. We'll need to make sure not to persist this runtime change. Maybe also: * [ ] Check if the commandline is a path to a single executable, and if it is, warn if it doesn't exist? Dunno how we'd get the first arg from the commandline _easily_ but it could totally be done.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#1782