WG: [dev] [stali] Why lksh?

From: Bruno Vetter <simplisticlife2010_AT_outlook.com>
Date: Mon, 10 Oct 2016 17:11:23 +0000

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 <simplisticlife2010_AT_outlook.com>
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 less things that I find surprising:

- No command line editing in sh
- echo $KSH_VERSION replies _AT_(#)LEGACY KSH R52 2016/03/04
- I see a flag MKSH_LEGACY_MODE in mksh's stali.mk.

Is the WASM blob really mksh, not lksh?


Von: Anselm R Garbe <garbeam_AT_gmail.com>
Gesendet: Montag, 10. Oktober 2016 04:47
An: dev mail list
Betreff: Re: [dev] [stali] Why lksh?
���
Hi Bruno,

On 9 October 2016 at 10:06, Bruno Vetter <simplisticlife2010_AT_outlook.com> wrote:
> i'm curious why you have chosen lksh as the stali shell. The manpage says:

Looks like a man page fault to me, probably lksh.1 is copied over
sh.1. The WASM blob should be definitely mksh.

Cheers,
Anselm

���
Received on Mon Oct 10 2016 - 19:11:23 CEST

This archive was generated by hypermail 2.3.0 : Mon Oct 10 2016 - 19:12:19 CEST