WG: [dev] [stali] Why lksh?

2016-10-10 Thread Bruno Vetter
Legacy mode is only set in build.sh when using the -L flag. Which is the way to build lksh according to the build documentation. Von: Bruno Vetter Gesendet: Montag, 10. Oktober 2016 19:05 An: dev mail list Betreff: AW: [dev] [stali] Why lksh?   I built stali from source and I see some mo

AW: [dev] [stali] Why lksh?

2016-10-10 Thread Bruno Vetter
I built stali from source and I see some more things that I find surprising: - No command line editing in sh - echo $KSH_VERSION replies @(#)LEGACY KSH R52 2016/03/04 - I see a flag MKSH_LEGACY_MODE in mksh's stali.mk. Is the binary really mksh, not lksh? Von: Anselm R Garbe Gesendet: Montag,

Re: [dev] [stali] Why lksh?

2016-10-10 Thread Evan Gates
On Sun, Oct 9, 2016 at 7:47 PM, Anselm R Garbe wrote: > Looks like a man page fault to me, probably lksh.1 is copied over > sh.1. The binary should be definitely mksh. Yep, binary is named sh in stali.mk and bin.mk checks for $(BIN).1 so we get sh.1 which is for lksh instead of mksh.1. Simple sol