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

Powershell Core OSC9;9 string leaves residue in prompt after using grep from git-for-windows with pipe #18008

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

Originally created by @3N4N on GitHub (Jul 22, 2022).

This is a port of an issue previously filed here: https://github.com/MicrosoftDocs/terminal/issues/425.

Output of the bug

PS C:\Users\ACER> dir | grep 'pattern'           # no match
PS C:\Users\ACER> ←]9;9;"C:\Users\ACER"
PS C:\Users\ACER>
PS C:\Users\ACER> dir | grep 'Documents'     # matches
d-r--           10/9/2021 11:04 PM                Documents
PS C:\Users\ACER> ←]9;9;"C:\Users\ACER"
PS C:\Users\ACER>
PS C:\Users\ACER> grep -HnrIi 'damn' .\Documents\PowerShell\        # to show that without piping the bug doesn't appear
.\Documents\PowerShell\/Scripts/scratch.ps1:1:function Damn([string]$sym)
PS C:\Users\ACER>
PS C:\Users\ACER> dir | win32yank.exe -i  # to show that the problem is not with piping
PS C:\Users\ACER>

Reproduction steps

  1. Put the following in the $PROFILE. 
    function prompt
{
$loc = Get-Location

# Emulate standard PS prompt with location followed by ">"
$out = "PS $loc> "

# Add current working directory (FileSystem)
if ($loc.Provider.Name -eq "FileSystem") {
    $out += "$([char]27)]9;9;`"$($loc.Path)`"$([char]7)"
}

return $out
}
  2. Open a new PWSH tab in windows terminal.
  3. Make sure git is in the $env:path and invoke: 
    dir | grep -i "pattern"

Versions of tools used

  • Windows Terminal: 1.15.2003.0 (why does wt -v not print in the console? I cannot even copy from the popup window.)
  • PowerShell Core: PowerShell 7.1.4
  • GIt for Windows: git version 2.33.0.windows.2

Discussions elsewhere

I mentioned in another issue -- may or may not be related -- that Windows Terminal crashes randomly if I use OSC9;9 string in the prompt. But I've been using the preview build for a week and it hasn't crashed yet. Update: I have had no crashes since then.

Originally created by @3N4N on GitHub (Jul 22, 2022). This is a port of an issue previously filed here: https://github.com/MicrosoftDocs/terminal/issues/425. ## Output of the bug ```ps1 PS C:\Users\ACER> dir | grep 'pattern' # no match PS C:\Users\ACER> ←]9;9;"C:\Users\ACER" PS C:\Users\ACER> PS C:\Users\ACER> dir | grep 'Documents' # matches d-r-- 10/9/2021 11:04 PM Documents PS C:\Users\ACER> ←]9;9;"C:\Users\ACER" PS C:\Users\ACER> PS C:\Users\ACER> grep -HnrIi 'damn' .\Documents\PowerShell\ # to show that without piping the bug doesn't appear .\Documents\PowerShell\/Scripts/scratch.ps1:1:function Damn([string]$sym) PS C:\Users\ACER> PS C:\Users\ACER> dir | win32yank.exe -i # to show that the problem is not with piping PS C:\Users\ACER> ``` ## Reproduction steps 1. Put the following in the `$PROFILE`. ```ps1 function prompt { $loc = Get-Location # Emulate standard PS prompt with location followed by ">" $out = "PS $loc> " # Add current working directory (FileSystem) if ($loc.Provider.Name -eq "FileSystem") { $out += "$([char]27)]9;9;`"$($loc.Path)`"$([char]7)" } return $out } ``` 2. Open a new PWSH tab in windows terminal. 3. Make sure `git` is in the `$env:path` and invoke: ```ps1 dir | grep -i "pattern" ``` ## Versions of tools used - Windows Terminal: 1.15.2003.0 (why does `wt -v` not print in the console? I cannot even copy from the popup window.) - PowerShell Core: PowerShell 7.1.4 - GIt for Windows: git version 2.33.0.windows.2 ## Discussions elsewhere I mentioned in [another issue](https://github.com/MicrosoftDocs/terminal/issues/285#issuecomment-937792680) -- may or may not be related -- that Windows Terminal crashes randomly if I use OSC9;9 string in the prompt. But I've been using the preview build for a week and it hasn't crashed yet. **Update**: I have had no crashes since then.
claunia added the Resolution-Duplicate label 2026-01-31 06:01:02 +00:00
claunia commented 2026-01-31 06:01:03 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jul 22, 2022):

why does wt -v not print in the console?

It is too sad to countenance. Funny enough, if you press Ctrl+C in any standard Windows message box, it DOES unexpectedly give you a hard copy of it:

---------------------------
Help
---------------------------
Windows Terminal Preview
1.16.2004.0
---------------------------
OK   
---------------------------

I'm guessing this is related to msys restoring the console mode and turning off VT input . . . let me go digging, because I wrote this up before.

@DHowett commented on GitHub (Jul 22, 2022): > why does `wt -v` not print in the console? It is too sad to countenance. Funny enough, if you press <kbd>Ctrl+C</kbd> in any standard Windows message box, it DOES unexpectedly give you a hard copy of it: ``` --------------------------- Help --------------------------- Windows Terminal Preview 1.16.2004.0 --------------------------- OK --------------------------- ``` I'm guessing this is related to msys restoring the console mode and turning off VT input . . . let me go digging, because I wrote this up before.
claunia commented 2026-01-31 06:01:03 +00:00
Author
Owner
Copy Link

@3N4N commented on GitHub (Jul 22, 2022):

let me go digging, because I wrote this up before.

This is way too fast a response. I feel guilty now. Take your time.

Funny enough, if you press Ctrl+C in any standard Windows message box, it DOES unexpectedly give you a hard copy of it

Live and learn.

@3N4N commented on GitHub (Jul 22, 2022): > let me go digging, because I wrote this up before. This is *way* too fast a response. I feel guilty now. Take your time. > Funny enough, if you press Ctrl+C in any standard Windows message box, it DOES unexpectedly give you a hard copy of it Live and learn.
claunia commented 2026-01-31 06:01:04 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jul 22, 2022):

I feel guilty now.

Ha, don't! It's not a problem at all.

The symptoms here feel very similar to the ones dissected in https://github.com/microsoft/terminal/issues/4921#issuecomment-599135352, which we traced back to an issue in the MSYS2 runtime that Git uses. I'm not sure whether the state of this issue has changed between 2.33 (the version you have installed) and 2.37 (the current version).

@DHowett commented on GitHub (Jul 22, 2022): > I feel guilty now. Ha, don't! It's not a problem at all. The symptoms here feel very similar to the ones dissected in https://github.com/microsoft/terminal/issues/4921#issuecomment-599135352, which we traced back to an issue in the MSYS2 runtime that Git uses. I'm not sure whether the state of this issue has changed between 2.33 (the version you have installed) and 2.37 (the current version).
claunia commented 2026-01-31 06:01:04 +00:00
Author
Owner
Copy Link

@3N4N commented on GitHub (Jul 22, 2022):

I can reproduce issue 4921. Although, I need to press enter once, then ←]9;9;"C:\Users\ACER" appears. Also, after git gui, if I run a command that produces an exception (apparently powershell errors and exceptions are different), the output is like this.

C:\Users\ACER> git gui
C:\Users\ACER> wrong_cmd hello world
←[91mwrong_cmd: ←[91mThe term 'wrong_cmd' is not recognized as a name of a cmdlet, function, script file, or executable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.←[0m
C:\Users\ACER> ←]9;9;"C:\Users\ACER"

So, basically terminal loses the ability to recognize the escape/special characters as escape/special characters, right?

I'm not sure whether the state of this issue has changed between 2.33 (the version you have installed) and 2.37 (the current version).

This issue persists with Msys2's grep command, too. And I regularly update msys.

@3N4N commented on GitHub (Jul 22, 2022): I can reproduce issue 4921. Although, I need to press enter once, then `←]9;9;"C:\Users\ACER"` appears. Also, after `git gui`, if I run a command that produces an exception (apparently powershell errors and exceptions are different), the output is like this. ``` C:\Users\ACER> git gui C:\Users\ACER> wrong_cmd hello world ←[91mwrong_cmd: ←[91mThe term 'wrong_cmd' is not recognized as a name of a cmdlet, function, script file, or executable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.←[0m C:\Users\ACER> ←]9;9;"C:\Users\ACER" ``` So, basically terminal loses the ability to recognize the escape/special characters as escape/special characters, right? > I'm not sure whether the state of this issue has changed between 2.33 (the version you have installed) and 2.37 (the current version). This issue persists with Msys2's grep command, too. And I regularly update msys.
claunia commented 2026-01-31 06:01:04 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jul 25, 2022):

Yea, this looks like the same thing. I'm game to call this a dupe (and reopen if I'm wrong).

/dup #4921

@zadjii-msft commented on GitHub (Jul 25, 2022): Yea, this looks like the same thing. I'm game to call this a dupe (and reopen if I'm wrong). /dup #4921
claunia commented 2026-01-31 06:01:04 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jul 25, 2022):

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 (Jul 25, 2022): 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 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#18008
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?