You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
Julian Noble 7f32862d2f runtime.cmd: active-runtime selection (use subcommand + active.toml), bash checksum parity, scriptset moved to src/scriptapps/bin (punkshell 0.7.0) 1 week ago
..
bin runtime.cmd: active-runtime selection (use subcommand + active.toml), bash checksum parity, scriptset moved to src/scriptapps/bin (punkshell 0.7.0) 1 week ago
wrappers misc scriptapps and file/folder organisation 10 months ago
AGENTS.md runtime.cmd: active-runtime selection (use subcommand + active.toml), bash checksum parity, scriptset moved to src/scriptapps/bin (punkshell 0.7.0) 1 week ago
README.md src/scriptapps/README.md 10 months ago
SELFSIGN.PS1 scriptapps misc 2 weeks ago
argsrecord.tcl
argsrecord.txt
bits.pl minor bin experiments 10 months ago
bits.ps1
bits.sh
bits_wrap.toml
create-localmachine-selfsigned-cert.ps1
dtplite.tcl
example.sh
example.tcl
example_wrap.toml make.tcl and console rawmode fixes 10 months ago
fetchruntime.bash
fetchruntime.ps1 scriptapps misc 2 weeks ago
fetchruntime.tcl
fetchruntime_bits.ps1 scriptapps misc 2 weeks ago
fetchruntime_old.ps1 scriptapps misc 2 weeks ago
fetchruntime_wrap.toml scriptapps misc 2 weeks ago
getpunk.bash
getpunk.ps1 scriptapps update 10 months ago
getpunk_wrap.toml scriptapps update 10 months ago
kettle.tcl
punk.tcl scriptapps misc 2 weeks ago
selfsign_wrap.toml scriptapps misc 2 weeks ago
tclargs.tcl
tclargs_wrap.toml
tcltm.tcl scriptapps misc 2 weeks ago
wrapfiletofile.tcl

README.md

Create multishell scripts from your .tcl .sh and .ps1 scripts that are stored here.

Use the deck scriptwrap commands to generate a multishell .cmd file from your scripts. This .cmd is a 'polyglot' script - it should run when called from any of the target interpreters.

A multishell .cmd file is a cross-platform script that can easily be run on Windows and unix-like platforms.

The .cmd extension is primarily a convenience so that it can be run easily by name on windows but it is ok to either leave it as that on other platforms, or rename it appropriately.

On unix-like platforms it can be called with a bourne shell such as sh or bash.

On windows, it can also be called with sh or bash if they are available - but the usual method would be to run it under cmd.exe initially just by opening a cmd prompt and running it. This will run some windows batch script to automatically generate a corresponding .ps1 file and execution will switch to powershell 5 or powershell 7 (pwsh) if available. Subsequently the command can be run directly from powershell.

Whether called from Bourne shell, or cmd.exe or powershell - the usual payload would be your wrapped Tcl code - but it's also possible for powershell or sh/bash to be the primary payload script. Any of these languages could easily be used to detect and launch other scripts/utilities that you may distribute with your app.