The Settings File

 You can save a selector script as "ENV:Selector.Settings" that contains
 your default settings for all your scripts. You can use all commands
 except SCREEN and POPUP. If you want this file to be copied
 to ENV: when you boot your system, then you should also copy the file
 to ENVARC: as all files in ENVARC: are copied to ENV: by the system
 startup-sequence.
 
 Here is an example of such a settings file:
 
   MarkButton ants
   background 3
   gap 0
   onchange selector.terminate exit
 
 Press here to copy it to ENV:Selector.Settings

 As allready said, this is the DEFAULT settings, so if another script
 also use for example the "gap" command, then this command will
 override the command in the settings file. But this is only true for
 commands that only can be used once in a script. For example the
 OnChange command in the example above is not discarded if
 onchange is used in another script. This command makes ALL running
 selectors to exit, if the env variable "selector.terminate" is changed.
 So, if you like, you can for example put some buttons in this settings
 file, that will appear in ALL selector windows...


 Also try the Prefs script! It edits the settings file for you!

 You can change settings file with the settings command.
 
 You can turn off the settings completely by starting selector with the
 -ns "no settings" option.

   
 Also see: Include