-
-
Notifications
You must be signed in to change notification settings - Fork 157
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
command
built-in does not support -p
option
#1795
Comments
Awesome, thanks! |
Should I/you close this issue? Or will you do it as part of the release? BTW, thanks for your enthusiasm and hard work on this! I know (only too well) that thanks are sometimes all we get for FOSS. 🙏🏻 Looking forward to making osh my daily driver with 0.2.0. |
I have a script that collects these for the release, so no need to close it I'm glad people are excited about the project :) |
Released, thanks for testing and contributing! https://www.oilshell.org/blog/2024/02/release-0.20.0.html |
From Zulip:
Lately, I've been really taken with the Warp terminal. Like Oils, it tries to jettison historical cruft, and one of the ways it does this is by replacing the terminal as a grid of TTY characters, and treating the input more like a standard OS input field.
By default, this only supports bash/zsh/fish. Warp also has an option to "Warpify" subshells, which is mostly used for things like SSH or Docker, but I thought I'd try it out on osh. Unfortunately, I got some errors, mostly saying "'command' doesn't accept flag -p".
Is this a known issue? I tried searching, but "command" isn't a search-friendly term.
If I try the interactive warpify option by hitting
⌘-I
, I get:If I try the automatic warpification by appending
printf '\eP$f{"hook": "SourcedRcFileForWarp", "value": { "shell": "bash"}}\x9c'
to the end of my oshrc, I get a differentcommand -p
error:The text was updated successfully, but these errors were encountered: