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

Bug Report: PowerShell Core launched by Azure Cloud Shell bash has positioning issues #3167

New Issue
Closed
opened 2026-01-30 23:14:34 +00:00 by claunia · 2 comments
claunia commented 2026-01-30 23:14:34 +00:00
Owner
Copy Link

Originally created by @AlanMcBee on GitHub (Aug 5, 2019).

Environment

Windows build number: 1903 OS build 18362.239
Windows Terminal version (if applicable): 0.3.2142.0

Any other software? N/A

Steps to reproduce

  1. Launch Azure Cloud Shell profile tab and connect/login to Azure
  2. Launch PowerShell Core with command: pwsh
  3. Execute any PowerShell Core commands

Expected behavior

Cursor position should continue to advance down the console as commands are entered and output is produced by cmdlets.

Actual behavior

Keyboard-entered input (cursor) is initially repositioned at row 0, column 0 regardless of where the prompt positions the cursor.

image

Originally created by @AlanMcBee on GitHub (Aug 5, 2019). # Environment ```none Windows build number: 1903 OS build 18362.239 Windows Terminal version (if applicable): 0.3.2142.0 Any other software? N/A ``` # Steps to reproduce 1. Launch Azure Cloud Shell profile tab and connect/login to Azure 1. Launch PowerShell Core with command: `pwsh` 1. Execute any PowerShell Core commands # Expected behavior Cursor position should continue to advance down the console as commands are entered and output is produced by cmdlets. # Actual behavior Keyboard-entered input (cursor) is initially repositioned at row 0, column 0 regardless of where the prompt positions the cursor. ![image](https://user-images.githubusercontent.com/37203424/62490064-4c469580-b77d-11e9-91b4-55b02b7fee78.png)
claunia commented 2026-01-30 23:14:35 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Aug 5, 2019):

This bug is two-fold.

  1. Windows Terminal usually had conhost sitting in between client processes and itself doing some basic VT translation for it. Powershell asks where the cursor is, and WT doesn't know to answer.
  2. Powershell seems to have this pathological need to know where the cursor is at all times, which makes it very frustrating to use everywhere but windows.
@DHowett-MSFT commented on GitHub (Aug 5, 2019): This bug is two-fold. 1. Windows Terminal usually had conhost sitting in between client processes and itself doing some basic VT translation for it. Powershell asks where the cursor is, and WT doesn't know to answer. 2. Powershell seems to have this _pathological need_ to know where the cursor is at all times, which makes it very frustrating to use everywhere but windows.
claunia commented 2026-01-30 23:14:36 +00:00
Author
Owner
Copy Link

@cconrado commented on GitHub (Jan 15, 2020):

Yes this drives me crazy lol

@cconrado commented on GitHub (Jan 15, 2020): Yes this drives me crazy lol
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-AzureShell Area-VT Issue-Task Needs-Tag-Fix Priority-3 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#3167
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?