Add a path option to the online shell script editor page allowing to set the path to the shell interpreter. Also have several pre-defined options.

For example, if I wanted to create a Powershell script in the K1 script editor, I could click on the "Powershell 5" or "Powershell 7" radio-button. If I needed the 64-bit version of Powershell 5 instead of the 32-bit version, I could enter the path to the 64-bit version. If I wanted to run a python3 script, I could enter into the path option "#!/usr/bin/env python3". If I wanted to run a Julia or a Rust script, I could enter the path to that interpreter.

Then I'm able to directly edit in the editor window almost any version of any scripting language, instead of being limited to Windows Command Prompt batch language and/or 32-bit Powershell.

Currently the only way to run a 64-bit Powershell script is to package it as a Dependency, and then to call the 64-bit interpreter from the editor window's batch language. If I need to debug the script, I have to download it, edit it, then re-upload it as a replacement dependency. It would be so much better to be able to edit it directly within the editor window of the K1. (And a nicer editor, with syntax highlighting and line-numbering, etc, wouldn't be objectionable, but that's for three or seven versions down the road.)