You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello! I'm the author of OSH, a POSIX- and bash-compatible shell - https://oils.pub/
And I created these reports recently, which might be interesting
https://pages.oils.pub/spec-compat/2025-06-26/renamed-tmp/spec/compat/TOP.html
https://pages.oils.pub/spec-compat/2025-06-26/renamed-tmp/spec/compat/PASSING.html
I created it mainly because I thought OSH was the only shell aiming at bash compatibility, until recently - https://news.ycombinator.com/item?id=43908368
I guess with bash and ksh, it's the other way around -- I know bash is implementing some ksh features like
${ echo command sub; }But maybe it's of interest? I am not sure if there is "pressure" for ksh to be bash compatible
BTW I arrived here from oils-for-unix/oils#2058 - a bug I just fixed in OSH, that appears to be in ksh
Beta Was this translation helpful? Give feedback.
All reactions