starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-09-25 00:15:10 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Improve first-run experience for non-developer audience #6030

New Issue
Closed
opened 2026-01-31 00:28:08 +00:00 by claunia · 6 comments
claunia commented 2026-01-31 00:28:08 +00:00
Owner
Copy Link

Originally created by @pronichkin on GitHub (Jan 18, 2020).

Originally assigned to: @DHowett on GitHub.

I just started Terminal for the first time on a new machine, and I see Windows PowerShell using Courier New font.

I have heard that Terminal comes with a new font, and now I am puzzled why it's not the default. Ok maybe I need to change it manually in settings.

There's no visible Settings button or menu. I have to look around for it. Finally, I find it under the down arrow, which is not very intuitive.

Opening settings pops up Windows dialog which asks me what to do with this file. I do not have any specialized editor on my machine. So, I am confused by this choice.

Finally, I chose Notepad because that's what I'm used to when opening unknown file types. I see JSON which is not formatted nicely. In fact, the first block (Azure Cloud Shell) is formatted while others are not. This is highly confusing.

I'm an IT Pro, not a developer. I'm not used to JSON files. I might have figured that out by trial and error, but that would be time consuming. Moreover, without visible indentation it's almost impossible.

Originally created by @pronichkin on GitHub (Jan 18, 2020). Originally assigned to: @DHowett on GitHub. I just started Terminal for the first time on a new machine, and I see Windows PowerShell using Courier New font. I have heard that Terminal comes with a new font, and now I am puzzled why it's not the default. Ok maybe I need to change it manually in settings. There's no visible Settings button or menu. I have to look around for it. Finally, I find it under the down arrow, which is not very intuitive. Opening settings pops up Windows dialog which asks me what to do with this file. I do not have any specialized editor on my machine. So, I am confused by this choice. Finally, I chose Notepad because that's what I'm used to when opening unknown file types. I see JSON which is not formatted nicely. In fact, the first block (Azure Cloud Shell) is formatted while others are not. This is highly confusing. I'm an IT Pro, not a developer. I'm not used to JSON files. I might have figured that out by trial and error, but that would be time consuming. Moreover, without visible indentation it's almost impossible.
claunia added the Issue-FeatureResolution-Duplicate labels 2026-01-31 00:28:08 +00:00
claunia commented 2026-01-31 00:28:09 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Jan 18, 2020):

A great many of the things reported here make me think you had an old v0.1 settings file laying around. You might be a lot happier if you reset your settings.

For the rest- we generally try to avoid bucket bugs. I’ll figure out what to do with this on Tuesday.

@DHowett-MSFT commented on GitHub (Jan 18, 2020): A great many of the things reported here make me think you had an old v0.1 settings file laying around. You might be a lot happier if you [reset your settings](https://www.hanselman.com/blog/NowIsTheTimeToMakeAFreshNewWindowsTerminalProfilesjson.aspx). For the rest- we generally try to avoid bucket bugs. I’ll figure out what to do with this on Tuesday.
claunia commented 2026-01-31 00:28:09 +00:00
Author
Owner
Copy Link

@pronichkin commented on GitHub (Jan 18, 2020):

Ok that's weird. I just tried again on a new machine and the experience was the following.

  1. Double-checked that .\AppData\Local\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\LocalState directory is empty.
  2. Started Terminal, observed the same unpleasant behavior.
  3. Verified that the profiles.json file was created in the abovementioned directory.
  4. Closed Terminal.
  5. Deleted the profiles.json file.
  6. Started Terminal again, the experience is now different. At least the font is visually different and much better looking. (Also there's fewer profiles this time, which I appreciate. Previously there were duplicates for Windows PowerShell, where one of them was called just "PowerShell.")
  7. Puzzled.

So, apparently the older settings were hanging around somewhere in my Windows profile, but not in the profiles.json?

@pronichkin commented on GitHub (Jan 18, 2020): Ok that's weird. I just tried again on a new machine and the experience was the following. 1. Double-checked that `.\AppData\Local\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\LocalState` directory is empty. 2. Started Terminal, observed the same unpleasant behavior. 3. Verified that the `profiles.json` file was created in the abovementioned directory. 4. Closed Terminal. 5. Deleted the `profiles.json` file. 6. Started Terminal again, the _experience is now different._ At least the font is visually different and much better looking. (Also there's fewer profiles this time, which I appreciate. Previously there were duplicates for Windows PowerShell, where one of them was called just "PowerShell.") 7. Puzzled. So, apparently the older settings were hanging around somewhere in my Windows profile, but **not** in the profiles.json?
claunia commented 2026-01-31 00:28:09 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Jan 18, 2020):

Yeah, back in v0.3 we moved the settings from Roaming to Local, but apparently the sync engine doesn’t sync file deletions. On a new machine, you get a roamed copy of your oldest settings that lived in the roaming folder, and they get promoted to local and left there. Before 0.9, we’ll probably kill the migrator for roamed settings.

@DHowett-MSFT commented on GitHub (Jan 18, 2020): Yeah, back in v0.3 we moved the settings from Roaming to Local, but apparently the sync engine _doesn’t sync file deletions_. On a new machine, you get a roamed copy of your oldest settings that lived in the roaming folder, and they get promoted to local and left there. Before 0.9, we’ll probably kill the migrator for roamed settings.
claunia commented 2026-01-31 00:28:09 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Jan 18, 2020):

If your settings were old enough (if you were on the v0.1 selfhost before we got JSON formatting, it’s highly likely) they even predated stable GUIDs for the built-in profiles, so duplicates would show up after v0.5 when we added settings merging. It’s a really rare situation. 😄

@DHowett-MSFT commented on GitHub (Jan 18, 2020): If your settings were old enough (if you were on the v0.1 selfhost before we got JSON formatting, it’s highly likely) they even predated stable GUIDs for the built-in profiles, so duplicates would show up after v0.5 when we added settings merging. It’s a really rare situation. 😄
claunia commented 2026-01-31 00:28:09 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Mar 25, 2021):

I'm coming across this hiding in the backlog today, and it seems like the main remaining complaint in this thread is "there's not a settings UI, you have to edit a json file". Which, as of 1.7 (preview), is no longer the case. So I'm gonna close this out.

/dup #1564

@zadjii-msft commented on GitHub (Mar 25, 2021): I'm coming across this hiding in the backlog today, and it seems like the main remaining complaint in this thread is "there's not a settings UI, you have to edit a json file". Which, as of 1.7 (preview), is no longer the case. So I'm gonna close this out. /dup #1564
claunia commented 2026-01-31 00:28:10 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Mar 25, 2021):

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 commented on GitHub (Mar 25, 2021): 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!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Issue-Feature Resolution-Duplicate
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#6030
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?