Post BAFGW4A7lNI8ASO7bk by mirabilos@toot.mirbsd.org
 (DIR) More posts by mirabilos@toot.mirbsd.org
 (DIR) Post #BAEpVgrzfN6pAIVJGi by overeducatedredneck@bitbang.social
       0 likes, 0 repeats
       
       @JdeBP @nafmo @mirabilos @rl_dane So, NetBSD's Almquist shell supports it, but its ksh (pdksh) does not.  OpenBSD ships its pdksh (oksh) as /bin/sh, and does not ship an almquist shell in the default install AFAIK.  OpenBSD's ksh fails this test too.  NetBSD's sh manpage has ;& documented, ksh does not.  ;% is unimplemented on both, as well.I checked on an nb10.1 server and this ob7.9 laptop (I just packed up my nb11 box to move it).
       
 (DIR) Post #BAEpVhTvOLRz3wFbOK by mirabilos@toot.mirbsd.org
       0 likes, 0 repeats
       
       @overeducatedredneck @JdeBP @nafmo @rl_dane there is no ;% in this discussion (other than perhaps a typo), we have ;& and ;| (bashism: ;;&)
       
 (DIR) Post #BAFGW3vEejNjQHQEOu by overeducatedredneck@bitbang.social
       0 likes, 0 repeats
       
       @mirabilos @JdeBP @nafmo @rl_dane The post I was replying to quoted your shell as accepting ;%.  So, it's a typo.  (I don't have quick access to mksh; it's installed on the debian partition, and OpenBSD doesn't have it in the ports tree, so I couldn't check it directly).Also, good to know.  I was thinking about checking the differences between mksh/oksh/nbksh and seeing if there are interesting things to port/harmonize.  Looks like the answer is yes :-).
       
 (DIR) Post #BAFGW4A7lNI8ASO7bk by mirabilos@toot.mirbsd.org
       0 likes, 0 repeats
       
       @overeducatedredneck @JdeBP @nafmo @rl_dane yes, I replied to that post mentioning it as typo ;)There are:;; = C break;, good old sh;& = C /* FALLTHROUGH */, bash, mksh, apparently now also POSIX sh;| basically says, evaluate the switch cases below again with the string and use the matching one, mksh;;& is the same as a bashism that mksh supports for compatibility
       
 (DIR) Post #BAFGfaO1K8yUiPQYBE by mirabilos@toot.mirbsd.org
       0 likes, 0 repeats
       
       @overeducatedredneck @JdeBP @nafmo @rl_dane mksh is also largely a superset of oksh, with some notable exceptions:checking the mailboxGNU bash-like PS1 (which even the oksh developers mention is impossible to parse right without evil hacks), we use Korn Shell PS1 instead, but with a relaxation of the \r rule making it easier to use
       
 (DIR) Post #BAFJmp7dEdlYJ4u8W0 by overeducatedredneck@bitbang.social
       0 likes, 0 repeats
       
       @rl_dane @mirabilos @JdeBP @nafmo OpenBSD ships its own pdksh as its default shell.  mksh not in ports because everyone just uses oksh.  It's been working well for me.
       
 (DIR) Post #BAFJmpL6QYXcyrCtVo by mirabilos@toot.mirbsd.org
       0 likes, 0 repeats
       
       @overeducatedredneck @rl_dane @JdeBP @nafmo no, that’s not the reason; oksh is horridly buggy wrt. current POSIX