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

Add POSIX shell support #10559

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

Originally created by @MarcusJohnson91 on GitHub (Sep 9, 2020).

I don't even think this would be difficult to do.

bundle the bash compatible, permissively licensed zsh shell, detect when a script starts with a hashbang and names a shell, have zsh take over.

I personally would find this useful because my project FoundationIO uses a shell script to generate Unicode tables that can't be ran on Windows.

not to mention I have to put about half of my cmake script into if Unix/Windows blocks to enable very basic functionality.

What's the point of writing a whole new Terminal if you're not going to turn a new leaf?

Originally created by @MarcusJohnson91 on GitHub (Sep 9, 2020). I don't even think this would be difficult to do. bundle the bash compatible, permissively licensed zsh shell, detect when a script starts with a hashbang and names a shell, have zsh take over. ---- I personally would find this useful because my project FoundationIO uses a shell script to generate Unicode tables that can't be ran on Windows. not to mention I have to put about half of my cmake script into if Unix/Windows blocks to enable very basic functionality. ---- What's the point of writing a whole new Terminal if you're not going to turn a new leaf?
claunia added the Issue-QuestionNeeds-Tag-FixResolution-Answered labels 2026-01-31 02:24:39 +00:00
claunia commented 2026-01-31 02:24:40 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Sep 9, 2020):

Well, we would also have to ship an entire compatibility layer that let you run POSIX-compliant things on Windows. Incidentally, we did this with WSL, and you can use bash/zsh/etc. to your heart's content.

@DHowett commented on GitHub (Sep 9, 2020): Well, we would also have to ship an entire compatibility layer that let you run POSIX-compliant things on Windows. Incidentally, we [did this](http://aka.ms/wsl) with WSL, and you can use bash/zsh/etc. to your heart's content.
claunia commented 2026-01-31 02:24:40 +00:00
Author
Owner
Copy Link

@MarcusJohnson91 commented on GitHub (Sep 9, 2020):

Well, we would also have to ship an entire compatibility layer that let you run POSIX-compliant things on Windows. Incidentally, we did this with WSL, and you can use bash/zsh/etc. to your heart's content.

Yes but wsl in a major PITA.

@MarcusJohnson91 commented on GitHub (Sep 9, 2020): > Well, we would also have to ship an entire compatibility layer that let you run POSIX-compliant things on Windows. Incidentally, we [did this](http://aka.ms/wsl) with WSL, and you can use bash/zsh/etc. to your heart's content. Yes but wsl in a major PITA.
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-Question Needs-Tag-Fix Resolution-Answered
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#10559
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?