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

Colortool not changing the default for VS 2017 developer command prompt #67

New Issue
Closed
opened 2026-01-30 21:41:21 +00:00 by claunia · 3 comments
claunia commented 2026-01-30 21:41:21 +00:00
Owner
Copy Link

Originally created by @dotnetdan on GitHub (Feb 1, 2018).

Please use this form and describe your issue, concisely but precisely, with as much detail as possible

  • Your Windows build number: (Type ver at a Windows Command Prompt)

Microsoft Windows [Version 10.0.16299.125]

  • What you're doing and what's happening: (Copy & paste specific commands and their output, or include screen shots)

I'm running the Developer Command Prompt for VS 2017, in admin mode.

I run the following:

colortool -b campbell

This changes the color of the current session. But if I open a new instance of the developer command prompt, only the default black & white terminal colors are being used. If I open a new regular command prompt, I see that Campbell has been applied.

Is there anyway to get this to work?

  • What's wrong / what should be happening instead:

Opening a new instance of Developer Command Prompt should use the new default color theme.

Originally created by @dotnetdan on GitHub (Feb 1, 2018). Please use this form and describe your issue, concisely but precisely, with as much detail as possible * Your Windows build number: (Type `ver` at a Windows Command Prompt) Microsoft Windows [Version 10.0.16299.125] * What you're doing and what's happening: (Copy & paste specific commands and their output, or include screen shots) I'm running the Developer Command Prompt for VS 2017, in admin mode. I run the following: `colortool -b campbell` This changes the color of the current session. But if I open a new instance of the developer command prompt, only the default black & white terminal colors are being used. If I open a new regular command prompt, I see that Campbell has been applied. Is there anyway to get this to work? * What's wrong / what should be happening instead: Opening a new instance of Developer Command Prompt should use the new default color theme.
claunia added the Product-ColortoolIssue-Question labels 2026-01-30 21:41:21 +00:00
claunia commented 2026-01-30 21:41:22 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Feb 2, 2018):

From the help text:

By default, applies the colors in the specified .itermcolors or .ini file to the current console window.
This does NOT save the properties automatically. For that, you'll need to open the properties sheet and hit "Ok".

You'll need to open the property sheet and hit okay to get the settings to persist for a particular shortcut.

@zadjii-msft commented on GitHub (Feb 2, 2018): From the help text: ``` By default, applies the colors in the specified .itermcolors or .ini file to the current console window. This does NOT save the properties automatically. For that, you'll need to open the properties sheet and hit "Ok". ``` You'll need to open the property sheet and hit okay to get the settings to persist for a particular shortcut.
claunia commented 2026-01-30 21:41:22 +00:00
Author
Owner
Copy Link

@dotnetdan commented on GitHub (Feb 2, 2018):

That works, thank you!

@dotnetdan commented on GitHub (Feb 2, 2018): That works, thank you!
claunia commented 2026-01-30 21:41:23 +00:00
Author
Owner
Copy Link

@miozus commented on GitHub (Aug 3, 2021):

image

it means Rclick PowerShell windows — attributes — colors — sure（ok）

to store the theme。

everything works well，thank you very much！

@miozus commented on GitHub (Aug 3, 2021): ![image](https://user-images.githubusercontent.com/35659194/128020276-f153cadb-d96d-49c1-9575-7d331b6b8012.png) it means Rclick PowerShell windows — attributes — colors — sure（ok） to store the theme。 everything works well，thank you very much！
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-Question Product-Colortool
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#67
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?