Conversation

This Tweet was deleted by the Tweet author. Learn more

this decoupling will begin with two initiatives for 3.17: - decoupling the init system, based on Laurent Bercot's TSC proposal with modifications - replacing /bin/sh (at the moment, FreeBSD /bin/sh is the likely contender)

Replying to

Any chance of someone ripping ash out of busybox and fixing the dubious code? It's small enough for that to be practical and it's by far my favorite shell.

Replying to

and

i havent tried freebsd's shell, but ash and (openbsd) pdksh suck compared to mksh in my experience. if freebsd sh works and is easy to port then it might be fine, sure, i see no benefit to keeping ash around

Replying to

and

mksh is a very nice shell and I’ve included it in MidnightBSD for many years. Still using FreeBSD ash as /bin/sh due to some compatibility issues with part of mports with it. I’ve slowly fixed then over time and plan to switch to mksh eventually. mksh is already default user sh

Replying to

and

mksh is by no means flawless but the only reason i bring it up is because it's the only shell that routinely works with my setups and no additional config

Replying to

and

How is its handling for multilingual text editing on entry line? My experience with non-ash shells is that they all botch it, either not supporting UTF-8 at all, not processing wcwidth right, or deleting all the way back to previous spacing char when backspacing a nonspacing.

Replying to

OpenBSD /bin/sh (ksh) has proper UTF-8 support since OpenBSD 5.9 (early 2016). It's quite usable and even has a very minimalist user defined auto-completion scripting system. It's worth trying. I'm too tied to my specific Zsh config but I'm fine with OpenBSD sh on servers, etc.

10:26 PM · Aug 2, 2022Twitter Web App

Replying to

Does backspace work in the sense I described?

Replying to

I think so, but there might still be a few quirks for line editing with double width characters such as emojis. I think everything else works fine now.

Replying to

OpenBSD /bin/sh and mksh were based on pdksh before AT&T ksh was open sourced and would have been better off based around AT&T ksh. I think they've both diverged quite a bit. Not sure what the practical differences are now. Android uses mksh as system shell so that's adb shell.