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

Feature Request: Azure Cloud Shell option to select PowerShell instead of bash #3165

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

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

Description of the new feature/enhancement

Connecting to Azure Cloud Shell using Terminal 0.3 will automatically launch the bash cloud shell provider. Personally, I prefer PowerShell.

I am able to launch PowerShell from bash by using pwsh, but there is a bug: when running PowerShell Core (launched from bash) using the Azure Cloud Shell, the cursor position gets repositioned to 0,0 on every new command, and the output is overlaid on the previous output (gets very messy, hard to read).

While it is probably a good idea to address that bug, this request is just to add or modify a profile to support PowerShell Core. (I'm going to create a new issue for that bug and update this.)
UPDATED: Here is the bug report: https://github.com/microsoft/terminal/issues/2267

Proposed technical implementation details (optional)

I thought it could just be possible to have Terminal go directly to PowerShell (preferably PowerShell Core) as an option for the Azure Cloud Shell profile settings, or else as a whole new profile.

As one of the profiles listed for a new tab in Terminal, I'd be okay with just one Azure Cloud Shell profile, where I would need to modify the settings.json to configure that profile to select the PowerShell Core option instead of the default bash option, or else there could be two Azure Cloud Shell profiles, one for bash and one for PowerShell Core.

Originally created by @AlanMcBee on GitHub (Aug 5, 2019). # Description of the new feature/enhancement Connecting to Azure Cloud Shell using Terminal 0.3 will automatically launch the bash cloud shell provider. Personally, I prefer PowerShell. I am able to launch PowerShell from bash by using `pwsh`, but there is a bug: when running PowerShell Core (launched from bash) using the Azure Cloud Shell, the cursor position gets repositioned to 0,0 on every new command, and the output is overlaid on the previous output (gets very messy, hard to read). While it is probably a good idea to address that bug, this request is just to add or modify a profile to support PowerShell Core. (I'm going to create a new issue for that bug and update this.) UPDATED: Here is the bug report: https://github.com/microsoft/terminal/issues/2267 # Proposed technical implementation details (optional) I thought it could just be possible to have Terminal go directly to PowerShell (preferably PowerShell Core) as an *option* for the Azure Cloud Shell profile settings, or else as a _whole new profile_. As one of the profiles listed for a new tab in Terminal, I'd be okay with just one Azure Cloud Shell profile, where I would need to modify the settings.json to configure that profile to select the PowerShell Core option instead of the default bash option, or else there could be two Azure Cloud Shell profiles, one for bash and one for PowerShell Core.
claunia commented 2026-01-30 23:14:33 +00:00
Author
Owner
Copy Link

@bitcrazed commented on GitHub (Sep 9, 2019):

Currently blocked on #1883 as per comments here: 886d018bb4/src/cascadia/TerminalConnection/AzureConnection.cpp (L664-L667)

@bitcrazed commented on GitHub (Sep 9, 2019): Currently blocked on #1883 as per comments here: https://github.com/microsoft/terminal/blob/886d018bb4032018ab69829705ea991a486c871e/src/cascadia/TerminalConnection/AzureConnection.cpp#L664-L667
claunia commented 2026-01-30 23:14:33 +00:00
Author
Owner
Copy Link

@Ayanmullick commented on GitHub (Feb 27, 2020):

I tried to run PowerShell from bash and it fails.

image

@Ayanmullick commented on GitHub (Feb 27, 2020): I tried to run PowerShell from bash and it fails. <details> ![image](https://i.imgur.com/JC6jdq6.gif)
claunia commented 2026-01-30 23:14:33 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Feb 27, 2020):

@Ayanmullick Lucky you! You hit a bug that I just filed upstream on PowerShell: https://github.com/PowerShell/PSReadLine/issues/1376

@DHowett-MSFT commented on GitHub (Feb 27, 2020): @Ayanmullick Lucky you! You hit a bug that I just filed upstream on PowerShell: https://github.com/PowerShell/PSReadLine/issues/1376
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 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#3165
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?