Conversation

This Tweet was deleted by the Tweet author. Learn more
Ariadne Conill
@ariadneconill
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)
5
19
Rich Felker
@RichFelker
Replying to
@ariadneconill
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.
2
1
opal
@wowaname
Replying to
@RichFelker
and
@ariadneconill
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
3
Lucas Holt
@laffer1
Replying to
@wowaname
@RichFelker
and
@ariadneconill
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
1
Rich Felker
@RichFelker
Replying to
@wowaname
@laffer1
and
@ariadneconill
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.
2
Daniel Micay
@DanielMicay
Replying to
@RichFelker
@wowaname
and 2 others
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.
2
1