Warp
Warp copied to clipboard
warpdotdev
Support other shells like powershell / nushell / ksh / xonsh / elvish / tcsh
Discord username (optional)
mandel
Describe the bug
One of the uses cases is to allow developers that are not happy with zsh to change to a different shell. This can be rolling back to bash w(hich was the original default Mac OS X terminal) or other shells such as pwsh.
Pwsh is a common scenario for two type of developers:
1. Windows developers that need to work on OS X.
2. Dotnet developers that are used to pwsh due to windows.
Another use case is to switch back to bash because there are some small differences between zsh and bash and in some cases, moving to zsh from bash makes certain scripts fail. As an example, we in xamarin-macios always ensure that Make does call bash and not zsh.
To Reproduce
- Install pwsh on the Mac using https://docs.microsoft.com/en-us/powershell/scripting/install/installing-powershell-on-macos?view=powershell-7.2
- Ensure that pwsh is in your /etc/shells
- Change the default shell via
chsh -s /usr/local/bin/pwsh - Open a new Warp windows. It should load with pwsh, it does not, instead it uses zsh.
Expected behaviour
When setting the default shell of my user to a diff shell app present in /etc/shells my configuration should be respected.
Screenshots
No response
Operating System
MacOS
OS Version
12.2.1
Additional context
No response
+1, I use powershell core for basic interaction with both win/mac; looking forward to warp.dev with posh support, else staying with oh-my-posh and iterm / windows terminal (both great, btw).
Also I suggest putting PowerShell in the name of the issue for SEO purposes, took some effort to find this issue.
I also use PowerShell quite heavily on macOS as a DevOps Engineer working in Azure all day. I would love for some native PowerShell 7 support in Warp. I also use oh-my-posh for a custom prompt and Warp doesn't seem to like ti very much 😬
I found this issue by searching for it, as I too would like to use PowerShell with Warp.
There may be other issues, but the first one I noticed was the differences in how the shell prompts are handled.
For zsh:
For pwsh:
This also means that the command "blocks" (not sure exactly what Warp calls them) do not work. The entire shell history is treated as a single block:
I found this issue by searching for it, as I too would like to use PowerShell with Warp.
There may be other issues, but the first one I noticed was the differences in how the shell prompts are handled.
For
zsh:For
pwsh:This also means that the command "blocks" (not sure exactly what Warp calls them) do not work. The entire shell history is treated as a single block:
Yeah that is because Warp doesn't natively understand other shells, so when you spin up PowerShell or Nushell it considers that a single command. And the entire block is the "one" command of running that other shell, until you exit and return to zsh or some other shell at Warp understands.
Shuan's correct, we have to make a custom parser for each shell to enable Blocks, etc. Check out here GitHub discussion on creating a generic shell API: https://github.com/warpdotdev/Warp/discussions/641
In the light theme many PowerShell prompts are all but invisible. Overall running pwsh in a Warp terminal is a recipe for crankiness!
+1, I use powershell to manage MS 365 and Azure functions. As a Mac user, please add powershell to warp for mac.
Hi Folks,
Thanks for your patience and for supporting Warp! Sorry for any inconvenience, but to track interest in other shells more accurately, we've decided to have separate GitHub feature requests for each of the major shells. We will now close this issue and begin tracking all the other shells Warp doesn't yet support in the following GitHub feature requests:
Shell | Feature Request
- Nushell | https://github.com/warpdotdev/Warp/issues/2038
- Xonsh | https://github.com/warpdotdev/Warp/issues/4568
- Elvish | https://github.com/warpdotdev/Warp/issues/5730
- tcsh | https://github.com/warpdotdev/Warp/issues/3665
- KornShell | https://github.com/warpdotdev/Warp/issues/2219
Please 👍 on top of each of the shells GitHub requests and subscribe to the ones you're interested in, as it will help us prioritize support accordingly. Also, please avoid comments like "+1" or "👍" on the threads to reduce the amount of spam in folks' inboxes.
Finally, Warp does support the following shells out of the box (bash | zsh | fish | pwsh | git bash | wsl)
I use Elvish (https://elv.sh) and it would be really cool if it would be possible to write integrations for it.
I really like this terminal. The first day I started with Warp, I just abandon others. But please support other shells like tcsh so I can continue with it in my remote server.
added
tcshto the list based on user feedback
But my Warp still can't work well with a remote server in tcsh env
@Josiah1 That is because Warp only supports bash|zsh|fish at this time, even on remote servers that must be the default shell in order for Warp to function as normal. Any updates or changes to this will be posted on this thread.
I have to use Mac for work, just found Warp and it is so nice! It's perfect, but I was soooo so disappointed to find out it doesn't support Powershell. Please add Powershell! And Xonsh and whatever (thank you @dannyneira , I had never heard of Xonsh).
I'd personally love Nu but see an enterprise case for PS too:
| Shell | ⭐ | 🟩🟩🟩🟩🟩🟩🟩🟩🟩🟩 |
|---|---|---|
| PowerShell | 42K | 🟩🟩🟩🟩🟩🟩🟩8️⃣🟢 |
| Nushell | 28K | 🟩🟩🟩🟩5️⃣🟢 |
| Xonsh | 7400 | 1️⃣🟢 |
| Elvish | 5200 | 1️⃣ |
| tcsh | 200 | [^1] |
| KornShell | 150 | [^1] |
[^1]: Not indicative of legacy usage
@texastoland "We also intend to build support for Powershell as part of building Warp on Windows." source. The plan is to build Windows version along with pwsh support after a Linux version. No firm ETA on this but we're aiming for Linux in 2024.
we do plan on building Warp for Windows once we've wrapped up building Linux (no concrete timeline just yet). We also intend to build support for PowerShell as part of building Warp on Windows.
Great news and makes sense! It also sounds like Nu isn't a possibility in the near future 🥲
