etc/run.domainname.cfg
etc/run.cfg
The configuration file(s) are read in the sequence: run.hostname.cfg -> run.domainname.cfg -> run.cfg when existing. The hostname is replaced by the %COMPUTERNAME% and domainname is replaced by the %USERDOMAIN% environment variable.
APPLICATION;EXECUTABLE;OPTIONS;DESCRIPTION;
It is allowed to have multiple entries with the identical APPLICATION name. In this case the run command starts the first EXECUTABLE found. Doing this it is possible to start different versions of an application depending on availability on the related system always thru the same run APPLICATION call.
Where:
The APPLICATION field entry can be a comma separated list representing aliases of the same application:
Firefox,FF;FirefoxPortable\FirefoxPortable.exe;-private-window;
where the FirefoxPortable.exe can be started either calling run Firefox or run FF .
When calling run application the case of application does not need to match to the entry in the APPLICATION field.
When calling
run -i application
the shortcut on the
'Desktop'
is precisely created as defined in the
APPLICATION
field (in upper-/lower-case as specified).
The run command supports to start executables with the suffixes .exe, .cmd and .bat.
To start executables with the suffixes .jar, .vbs, .ps1 or .lua an APPLICATION with the name run.suffix has to be defined in run.cfg to locate the related interpreter and to set the desired default options for it as for example:
# # run.cfg - configuration file for run.exe # # [00] 20.07.2018 CWa Initial Version # APPLICATION;EXECUTABLE;OPTIONS;DESCRIPTION; run.jar;bin\javaw.exe;-jar;start .jar from run; run.lua;lib\lua.exe;;start .lua from run; run.ps1;c:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe;-executionpolicy bypass -File;start .ps1 from run; run.vbs;c:\Windows\system32\cscript.exe;//Nologo;start .vbs from run;
When specifying executables with other suffixes, then system wide file associations apply to load/start the related executable file.
The same (environment)variables as in the OPTIONS column can also be used in the EXECUTABLE column.
The following time and date related variables can also be used in the OPTIONS column:
(The date used in the examples is February 26th, 1986 14:59:31)
The following (environment)variables can also be used in the OPTIONS column:
The DESCRIPTION field is optional.
# # run.cfg - configuration file for run.exe # # [00] 20.07.2018 CWa Initial Version # APPLICATION;EXECUTABLE;OPTIONS;DESCRIPTION; Excel;Microsoft Office\Office14\excel.exe;;Spreadsheet; Excel;Microsoft Office\Office16\excel.exe;;Spreadsheet; GIMP;GIMPPortable\GIMPPortable.exe;;Photo Editor; Firefox,FF;FirefoxPortable\FirefoxPortable.exe;-private-window;Web Browser; XMind;XMindPortable\XMind 8 Update 1\XMind.exe;;Mind Mapping; Gnuplot;Octave\octave-4.2.1\bin\wgnuplot.exe;;Math. Plotting; Writer;OfficePortable\Writer.exe;;Text Editor;
[ h:\bin\WA2LWinTools\etc ] [ fred@ACME007 ][*wtshell*/cmd]: ..\lib\cfgcat -f run.cfg
or
[ h:\bin\WA2LWinTools\lib ] [ fred@ACME007 ][*wtshell*/cmd]: run -l | cfgcat -f -
to expand the variables.
This is free software; see WA2LWinTools/doc/COPYING for copying conditions. There is ABSOLUTELY NO WARRANTY; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.