On 2013-04-27 21:47, Thorsten Glaser wrote:
Anselm R Garbe dixit:
Can you elaborate on this functionality a bit that mksh provides, but
pdksh doesn't?
Not easily; the last release of pdksh was in 1999, and mksh is
actively developed; even pointing out every single bugfix, for
POSuX compliance or genuine, would take several Kibibytes.
It’s developed with an attitude I’d call “suckless”, without
being part of suckless.org though. (And it’s quality software
from Germany ☺) mksh’s even got some sort of community (with
people porting to even more weird platforms than I tried myself,
users sending bugfixes, even developers of other shells jumping
in every once in a while), mostly in IRC but also on a “faux”
mailing list (Cc'd).
Sorry for taking this out of context (and on the wrong list), but I
built mksh (now a relatively old version 40f) for Plan9/APE (using the
native "cc" front end to the plan9 compilers) in the hope to replace the
old pdksh "sh" command there.
using -DMKSH_NOPROSPECTOFWORK, a (as far as I remember) unmodified mksh
builds and executes without complaining about absence of tty:s.
Interestingly however, what happens if executing a command in this shell
is that the shell returns the written command with every character
duplicated (example: "exit" writes out "eexxiitt" before exiting the shell).
I have been meaning to look into that again sometime, but never got
around to it. If you have some pointers about that really weird issue,
it would be cool to fix it.
