starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

improve the default settings #1182

New Issue
Closed
opened 2026-01-30 22:18:17 +00:00 by claunia · 7 comments
claunia commented 2026-01-30 22:18:17 +00:00
Owner
Copy Link

Originally created by @DHowett-MSFT on GitHub (May 17, 2019).

Originally assigned to: @DHowett-MSFT on GitHub.

Followup to #430. Here's what I'm thinking.

  • alwaysShowTabs -> true
  • experimental_showTabsInTitlebar -> true
  • always include Windows Powershell (background: #012456)
  • include PowerShell Core separately (background: unset)
  • drop Courier New for powershell
Originally created by @DHowett-MSFT on GitHub (May 17, 2019). Originally assigned to: @DHowett-MSFT on GitHub. Followup to #430. Here's what I'm thinking. * [ ] `alwaysShowTabs` -> `true` * [ ] `experimental_showTabsInTitlebar` -> `true` * [ ] always include Windows Powershell (`background`: `#012456`) * [ ] include PowerShell Core separately (`background`: unset) * [ ] drop `Courier New` for powershell
claunia commented 2026-01-30 22:18:18 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (May 17, 2019):

We're automatically making powershell (core) the default now. If core is installed, should that be the default? or Windows powershell always?

Also, if we're making show tabs in titlebar the default, then we should probably pull experimental_ off of it.

@zadjii-msft commented on GitHub (May 17, 2019): We're automatically making powershell (core) the default now. If core is installed, should that be the default? or Windows powershell always? Also, if we're making show tabs in titlebar the default, then we should probably pull `experimental_` off of it.
claunia commented 2026-01-30 22:18:18 +00:00
Author
Owner
Copy Link

@mdtauk commented on GitHub (May 17, 2019):

We're automatically making powershell (core) the default now. If core is installed, should that be the default? or Windows powershell always?

Also, if we're making show tabs in titlebar the default, then we should probably pull experimental_ off of it.

I would suggest you read the registry setting to see if the user has changed the setting to use Command instead of Powershell.

image

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced\DontUsePowerShellOnWinX

@mdtauk commented on GitHub (May 17, 2019): > We're automatically making powershell (core) the default now. If core is installed, should that be the default? or Windows powershell always? > > Also, if we're making show tabs in titlebar the default, then we should probably pull `experimental_` off of it. I would suggest you read the registry setting to see if the user has changed the setting to use Command instead of Powershell. ![image](https://user-images.githubusercontent.com/7389110/57929342-f3b4da00-78aa-11e9-9012-246e0aa1dcf5.png) ### HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced\DontUsePowerShellOnWinX
claunia commented 2026-01-30 22:18:18 +00:00
Author
Owner
Copy Link

@fearthecowboy commented on GitHub (May 17, 2019):

What's your detection mechanism for seeing if pwsh is installed?

@fearthecowboy commented on GitHub (May 17, 2019): What's your detection mechanism for seeing if pwsh is installed?
claunia commented 2026-01-30 22:18:18 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (May 17, 2019):

Today, it’s “crawl through Program Files to find telltale signs of it.” Tomorrow, however, maybe it’ll be “look into the installer database (using supported APIs) to see where the user really put it.”

@DHowett-MSFT commented on GitHub (May 17, 2019): Today, it’s “crawl through Program Files to find telltale signs of it.” Tomorrow, however, maybe it’ll be “look into the installer database (using supported APIs) to see where the user really put it.”
claunia commented 2026-01-30 22:18:18 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (May 17, 2019):

I would suggest you read the registry setting to see if the user has changed the setting to use Command instead of Powershell.

We've debated about this for a while internally. It's a good idea, and we should do it, but the registry is not a contract, and we are not supposed to go groveling about in other peoples' registry keys. It's the same fundamental issue as was brought up in #695.

What we should be doing is driving API dependencies, as we are with WSL, so that we can detect how the user's configured their machine.

@DHowett-MSFT commented on GitHub (May 17, 2019): > I would suggest you read the registry setting to see if the user has changed the setting to use Command instead of Powershell. We've debated about this for a while internally. It's a good idea, and we should do it, but _the registry is not a contract, and we are not supposed to go groveling about in other peoples' registry keys._ It's the same fundamental issue as was brought up in #695. What we should be doing is driving API dependencies, as we are with WSL, so that we can detect how the user's configured their machine.
claunia commented 2026-01-30 22:18:19 +00:00
Author
Owner
Copy Link

@mdtauk commented on GitHub (May 17, 2019):

I agree this should be a default app type and WinRT should provide a read only API to receive a friendly package name, and entry point path for all default apps that are installed.

I personally always switch my default to CMD, and avoid powershell (unless I need to trouble shoot some store apps)

@mdtauk commented on GitHub (May 17, 2019): I agree this should be a default app type and WinRT should provide a read only API to receive a friendly package name, and entry point path for all ~~default~~ apps that are installed. I personally always switch my default to CMD, and avoid powershell (unless I need to trouble shoot some store apps)
claunia commented 2026-01-30 22:18:19 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (May 20, 2019):

I propose also changing the default font size, as caught in #903. The default font size of 12 was originally 12px, but since then we changed the DX renderer such that 12 meant 12 point. 12 point is definitely bigger than 12px tall

@zadjii-msft commented on GitHub (May 20, 2019): I propose also changing the default font size, as caught in #903. The default font size of `12` was originally 12px, but since then we changed the DX renderer such that 12 meant 12 point. 12 point is definitely bigger than 12px tall
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 Area-Settings Issue-Feature Product-Terminal Resolution-Fix-Committed
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#1182
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?