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

PowerShell custom prompt bugs out last character on a "syntax error" line #20712

New Issue
Closed
opened 2026-01-31 07:21:56 +00:00 by claunia · 4 comments
claunia commented 2026-01-31 07:21:56 +00:00
Owner
Copy Link

Originally created by @azurenekowo on GitHub (Oct 21, 2023).

Windows Terminal version

1.19.2682.0

Windows build number

10.0.19045.0

Other Software

No response

Steps to reproduce

My custom prompt is implemented via the following (added into $profile):

function prompt {
     "$BASE[38;5;141m$env:username@$env:computername$BASE[38;5;228m: $BASE[38;5;250m$pwd $BASE[38;5;14m~#$RESET "
}

By default, it should show up as : username@DESKTOP-xxxxxx: C:\Users\username ~#

However, when I, say enter an invalid syntax (just typing echo ", not even executing it), it will bug out the last character (in this case, # with a red m).

image

It will persist until I press Enter, which executes the command and prompts again.
image

Expected Behavior

It shouldn't bug out the last character of the prompt.

Actual Behavior

It did bug out.
image

Originally created by @azurenekowo on GitHub (Oct 21, 2023). ### Windows Terminal version 1.19.2682.0 ### Windows build number 10.0.19045.0 ### Other Software _No response_ ### Steps to reproduce My custom prompt is implemented via the following (added into `$profile`): ```powershell function prompt { "$BASE[38;5;141m$env:username@$env:computername$BASE[38;5;228m: $BASE[38;5;250m$pwd $BASE[38;5;14m~#$RESET " } ``` By default, it should show up as : `username@DESKTOP-xxxxxx: C:\Users\username ~#` However, when I, say enter an invalid syntax (just typing `echo "`, not even executing it), it will bug out the last character (in this case, `#` with a red `m`). ![image](https://github.com/microsoft/terminal/assets/67498765/19bb1170-48fc-4be4-a098-ea18747f9326) It will persist until I press <kbd>Enter</kbd>, which executes the command and prompts again. ![image](https://github.com/microsoft/terminal/assets/67498765/3a0fee46-9e6a-4155-ba18-20bd8191de8e) ### Expected Behavior It shouldn't bug out the last character of the prompt. ### Actual Behavior It did bug out. ![image](https://github.com/microsoft/terminal/assets/67498765/0394266b-140e-40b6-a235-fb1f5914e79d)
claunia added the Needs-TriageIssue-Bug labels 2026-01-31 07:21:56 +00:00
claunia commented 2026-01-31 07:21:57 +00:00
Author
Owner
Copy Link

@j4james commented on GitHub (Oct 21, 2023):

@azurenekowo As far I understand, this is a feature of PowerShell. When there is a syntax error in the command line, it redraws part of the prompt in red as a warning. However, in order for that to work correctly, it needs to know what your prompt looks like. You can control that with the PromptText option (see Using the PromptText parameter).

I'm not sure why you're getting a red m though, since by default it should be a >. Is it possible that you've already set the PromptText option without realising it?

And if you don't want the prompt to change at all, you can probably just set the PromptText to a blank string.

@j4james commented on GitHub (Oct 21, 2023): @azurenekowo As far I understand, this is a feature of PowerShell. When there is a syntax error in the command line, it redraws part of the prompt in red as a warning. However, in order for that to work correctly, it needs to know what your prompt looks like. You can control that with the `PromptText` option (see [Using the PromptText parameter]( https://learn.microsoft.com/en-us/powershell/module/psreadline/set-psreadlineoption?view=powershell-7.3#example-9-using-the-prompttext-parameter)). I'm not sure why you're getting a red `m` though, since by default it should be a `>`. Is it possible that you've already set the `PromptText` option without realising it? And if you don't want the prompt to change at all, you can probably just set the `PromptText` to a blank string.
claunia commented 2026-01-31 07:21:57 +00:00
Author
Owner
Copy Link

@azurenekowo commented on GitHub (Oct 22, 2023):

@j4james Hi, turns out I haven't set the PromptText option after doing function prompt {}.

After a bit of configuring, it worked. Thank you so much!

@azurenekowo commented on GitHub (Oct 22, 2023): @j4james Hi, turns out I haven't set the PromptText option after doing `function prompt {}`. After a bit of configuring, it worked. Thank you so much!
claunia commented 2026-01-31 07:21:58 +00:00
Author
Owner
Copy Link

@237dmitry commented on GitHub (Oct 22, 2023):

I couldn't reproduce it either in Windows Terminal or in conhost.exe

Screenshot 2023-10-22 173958

@237dmitry commented on GitHub (Oct 22, 2023): I couldn't reproduce it either in Windows Terminal or in conhost.exe ![Screenshot 2023-10-22 173958](https://github.com/microsoft/terminal/assets/78153320/23eae13f-7cbc-40fb-a282-8ff9950646e6)
claunia commented 2026-01-31 07:21:58 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Oct 23, 2023):

If I'm understanding you correctly, the issue has been resolved right? I'll be closing it then. 🙂

@lhecker commented on GitHub (Oct 23, 2023): If I'm understanding you correctly, the issue has been resolved right? I'll be closing it then. 🙂
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-Bug Needs-Triage
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#20712
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?