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

Azure Cloud Shell cutting off code required for device login #3639

New Issue
Closed
opened 2026-01-30 23:26:10 +00:00 by claunia · 5 comments
claunia commented 2026-01-30 23:26:10 +00:00
Owner
Copy Link

Originally created by @DukeOfEtiquette on GitHub (Aug 28, 2019).

Originally assigned to: @miniksa on GitHub.

Environment

Windows build number: Microsoft Windows [Version 10.0.18965.1000]
Windows Terminal version (if applicable): Version: 0.4.2382.0

Steps to reproduce

Open an Azure Cloud Shell with a column width of <= 90

Expected behavior

The following message should appear:
To sign in, use a web browser to open the page https://microsoft.com/devicelogin and enter the code <code> to authenticate.

Actual behavior

The text of the message, including the code required for input at url, is cutoff and no way to get the terminal to repaint/provide the code again. Only solution is to increase width of window and open another tab to get the code.

Is it possible to apply a wordwrap to that initial message?

Originally created by @DukeOfEtiquette on GitHub (Aug 28, 2019). Originally assigned to: @miniksa on GitHub. # Environment ```none Windows build number: Microsoft Windows [Version 10.0.18965.1000] Windows Terminal version (if applicable): Version: 0.4.2382.0 ``` # Steps to reproduce Open an Azure Cloud Shell with a column width of <= 90 # Expected behavior The following message should appear: `To sign in, use a web browser to open the page https://microsoft.com/devicelogin and enter the code <code> to authenticate.` # Actual behavior The text of the message, including the code required for input at url, is cutoff and no way to get the terminal to repaint/provide the code again. Only solution is to increase width of window and open another tab to get the code. Is it possible to apply a wordwrap to that initial message?
claunia added the Area-OutputIssue-TaskResolution-DuplicateProduct-Terminal labels 2026-01-30 23:26:11 +00:00
claunia commented 2026-01-30 23:26:12 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 28, 2019):

@miniksa This is electric boogaloo, right? Like theoretically, the message could just be formatted at runtime, but the real solution is WriteCharsLegacy2, yea?

@zadjii-msft commented on GitHub (Aug 28, 2019): @miniksa This is electric boogaloo, right? Like theoretically, the message could just be formatted at runtime, but the real solution is WriteCharsLegacy2, yea?
claunia commented 2026-01-30 23:26:12 +00:00
Author
Owner
Copy Link

@DukeOfEtiquette commented on GitHub (Aug 28, 2019):

@miniksa This is electric boogaloo, right? Like theoretically, the message could just be formatted at runtime, but the real solution is WriteCharsLegacy2, yea?

I'm not entirely sure, this is out of my wheelhouse. Runtime formatting seems reasonable.

@DukeOfEtiquette commented on GitHub (Aug 28, 2019): > @miniksa This is electric boogaloo, right? Like theoretically, the message could just be formatted at runtime, but the real solution is WriteCharsLegacy2, yea? I'm not entirely sure, this is out of my wheelhouse. Runtime formatting seems reasonable.
claunia commented 2026-01-30 23:26:12 +00:00
Author
Owner
Copy Link

@miniksa commented on GitHub (Aug 28, 2019):

@zadjii-msft, I believe the answer is WriteCharsLegacy2. Yes.

@miniksa commented on GitHub (Aug 28, 2019): @zadjii-msft, I believe the answer is `WriteCharsLegacy2`. Yes.
claunia commented 2026-01-30 23:26:12 +00:00
Author
Owner
Copy Link

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

/dup #780

@DHowett-MSFT commented on GitHub (Sep 5, 2019): /dup #780
claunia commented 2026-01-30 23:26:12 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Sep 5, 2019):

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 (Sep 5, 2019): 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 Area-Output Issue-Task Product-Terminal 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#3639
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?