A shared link can now carry the language alongside the command, e.g.
/playground?lang=fr-FR&cmd=cut+-f+1,4-2,9-12+fruits.txt to show a
localized error message.
The value accepts both the short (fr) and full (fr-FR) form, is
validated against the locales the build ships, and is applied before
the ?cmd= commands run. The share-link button appends it when the
locale is not the default, and the Language dropdown stays in sync
via a new uutils:locale-changed event.
The caret diagnostics are the most demo-able thing in 0.11.0 and the
playground never showed them. Add a section of arguments that fail to parse
(tr set, cut range, sort key, expr and test operands, numfmt and printf
formats, head SIZE, csplit regex), all on files the playground ships, and
point at the blog post for the rest.
chmod, mkfifo, mknod, install, stat, env, du, df and stdbuf are not in
feat_wasm, so their "try it" links could only ever answer "command not
found". Show those commands as plain code, drop the two inline playground
links for chmod and env, and say that the linked examples are the ones the
WebAssembly build ships.
The CI wasm-standalone matrix has no awk entry, so /wasm/awk.wasm has never
been deployed and the live commands.js carries no awk: the Load button, the
examples and the help text all pointed at a module that isn't there.
Remove awk from the terminal engine (module, group, WIP note, fallback
command list, argument handling, awkReady), from the page wiring and its
version line, and from the playground pages. The /awk project page stays.
Eight examples, each replayed in a terminal with xterm.js from a cast of
what the utility really printed. The static report stays visible when
JavaScript does not run.
Sylvestre Ledru