Enable or disable the specified script or scripts. The script name should match the filename(s) of the script add-in(s) you wish to affect.
If the global option to disable all script add-ins is in effect, no individual script can be enabled.
The script name can use simple * wildcards to match multiple filenames. While this can be used to enable or disable multiple scripts at once, it is intended to avoid worrying about whether a script is installed with ".js" and ".vbs" or ".js.txt" and ".vbs.txt" style extensions.
(As a special case, if the script name wildcard is literally "*" or "*.*", the command acts the same as if no script name was specified, and toggles the global option to disable all script add-ins.)
If the script name is the only parameter, the script will be toggled (enabled if currently disabled; disabled if currently enabled). If multiple scripts match the pattern, they will all be set to the same state as the first match, and not toggled individually.
Example: Prefs SCRIPTDISABLE="My Script.js\*"
If a script is inside a Script Package (.osp file), the package must be included in the name:
Example: Prefs SCRIPTDISABLE="My Package.osp\My Script.vbs"
Wildcards can make dealing with script packages easier, and can also handle script packages which contain multiple scripts, or where you distribute a script to people as a .osp but work on it privately as a text file:
Example: Prefs SCRIPTDISABLE="My Package.osp\*"
Example: Prefs SCRIPTDISABLE="*My Script.vbs\*"
