Re: WASM + dash (again!)
Samuel Marks <[email protected]> Wed, 15 Apr 2026 20:18:23 +1200
| Newsgroups | org.kernel.vger.dash |
|---|---|
| Message-ID | <CAMfPbcapQ8ixUG2P9At+2YJp2xd6AZia4Qw8rKfahw-wXKA6-g@mail.gmail.com> |
Thanks for the support and the feature suggestions Now have >50 tools [curl, jq, head, less, more, top, nano, =E2=80=A6], clipboard integration, localStorage CRUD, piping, custom functions, and more. Please keep the suggestions coming! PS: Oh and I did similar for toybox http://samuelmarks.github.io/toybox/ https://github.com/SamuelMarks/toybox/tree/wasm Samuel Marks https://github.com/SamuelMarks https://linkedin.com/in/samuelmarks On Mon, Apr 13, 2026 at 1:26=E2=80=AFPM Harald van Dijk <[email protected]= > wrote: > > Hi, > > I don't know enough about WASM to comment beyond just loading it up and > seeing that it seems to work for basic things (which is always a good > sign) but: > > On 13/04/2026 00:44, Samuel Marks wrote: > > The port successfully passes a headless Node.js adaptation of the > > `dash` test suite. > What test suite did you use? dash does not have one. As some basic shell > constructs require forking, they do not work (as I think you expect), > and I would have expected these to be covered by any test suite. > > # echo 1 & > ./this.program: 0: Cannot fork > # echo hello | cat > ./this.program: 0: Cannot fork > > It is totally fine to say you are not looking to fix this, I'm just > wondering if your test suite gave you some indication of what other > constructs may not work either. > > Cheers, > Harald van Dijk