Shell Environment Variables/en - Versionsgeschichte

Cg: /* Referring to Configured Script Interpreters in Shell/Batch Scripts */

2022-07-28T11:00:12Z

Referring to Configured Script Interpreters in Shell/Batch Scripts

← Nächstältere Version		Version vom 28. Juli 2022, 11:00 Uhr
Zeile 51:		Zeile 51:
	The easiest way to find out which values are provided is by executing a shell script consisting of a "printenv" (unix) or "set" (windows) command only, and looking at the value at the "stdout" pin.		The easiest way to find out which values are provided is by executing a shell script consisting of a "printenv" (unix) or "set" (windows) command only, and looking at the value at the "stdout" pin.
	For example, to make sure that the same interpreter is used when using a shell script for pip-package installation, write a shell script like:		For example, to make sure that the same interpreter is used when using a shell script for pip-package installation, write a shell script like:
	%(EXPECCO_python3Command) -m pip install ~~<nameOfPackage>~~		$EXPECCO_python3Command -m pip install %(package)
			(notice that the first is a shell variable, which needs a dollar prefix, whereas the second is an expecco value coming from a pin named "package", which needs %(..) around.

			For batch/cmd scripts (which need percents around the shell variable's name). use:
			%EXPECCO_python3Command% -m pip install %(package)

Cg: /* Referring to Configured Script Interpreters in Shell/Batch Scripts */

2022-07-28T10:56:02Z

Referring to Configured Script Interpreters in Shell/Batch Scripts

← Nächstältere Version		Version vom 28. Juli 2022, 10:56 Uhr
Zeile 50:		Zeile 50:

	The easiest way to find out which values are provided is by executing a shell script consisting of a "printenv" (unix) or "set" (windows) command only, and looking at the value at the "stdout" pin.		The easiest way to find out which values are provided is by executing a shell script consisting of a "printenv" (unix) or "set" (windows) command only, and looking at the value at the "stdout" pin.
			For example, to make sure that the same interpreter is used when using a shell script for pip-package installation, write a shell script like:
			%(EXPECCO_python3Command) -m pip install <nameOfPackage>

Cg: /* Script Interpreters for External Language Scripts */

2022-07-28T10:54:39Z

Script Interpreters for External Language Scripts

← Nächstältere Version		Version vom 28. Juli 2022, 10:54 Uhr
Zeile 39:		Zeile 39:
	* '''GNUPLOT_SHELL''' (gnuplot scripts; defaults to "<code>gnuplot</code>")		* '''GNUPLOT_SHELL''' (gnuplot scripts; defaults to "<code>gnuplot</code>")
	* '''RSCRIPT_SHELL''' ('R' scripts; defaults to "<code>R.exe</code>" on Windows, "<code>r</code>" on OSX, "<code>R</code>" on Unix/Linux)		* '''RSCRIPT_SHELL''' ('R' scripts; defaults to "<code>R.exe</code>" on Windows, "<code>r</code>" on OSX, "<code>R</code>" on Unix/Linux)

			=== Referring to Configured Script Interpreters in Shell/Batch Scripts ===
			To refer to whatever language interpreter was configured in expecco from '''a shell or batch script''', the settings are provided as:
			* '''EXPECCO_pythonCommand''' - the value you gave in the settings for the generic (unspecified) python version
			* '''EXPECCO_python3Command''' - the value from the settings for explicit version3.x python
			* '''EXPECCO_python2Command''' - the value from the settings for explicit version2.x python
			* '''EXPECCO_ironPythonCommand''' -
			* '''EXPECCO_jythonCommand''' -
			* '''EXPECCO_nodeJSCommand''' -

			The easiest way to find out which values are provided is by executing a shell script consisting of a "printenv" (unix) or "set" (windows) command only, and looking at the value at the "stdout" pin.

Cg: /* Temporary Files Folder */

2022-06-12T10:28:58Z

Temporary Files Folder

← Nächstältere Version		Version vom 12. Juni 2022, 10:28 Uhr
Zeile 5:		Zeile 5:
	=== Temporary Files Folder ===		=== Temporary Files Folder ===

	Expecco (and Smalltalk) may create temporary files, which ~~may~~ outlive your ~~session, in case of an abnormal termination (or in case a suite fails to cleanup temporary files correctly).~~		Expecco (and Smalltalk) may create temporary files, which could outlive your sessio
			In normal operation, temp files are removed when expecco is terminated.
			However, in case of an abnormal termination (or in case a suite fails to cleanup temporary files correctly), files may be left in your file system.

	By default, temporary files are created inside a per-session temporary folder.		By default, temporary files are created inside a per-session temporary folder.
Zeile 20:		Zeile 22:
	(doing a "''printIt''" in a Smalltalk workspace),		(doing a "''printIt''" in a Smalltalk workspace),
	or via a corresponding action block in the standardlibrary.		or via a corresponding action block in the standardlibrary.

			It is good practice, to look at the temp folder from time to time, and remove old leftover files, to prevent your drive to become full (many unix/linux systems do this automatically if configured so).

	=== Script Interpreters for External Language Scripts ===		=== Script Interpreters for External Language Scripts ===

Cg: /* Script Interpreters for External Language Scripts */

2018-06-14T16:30:35Z

Script Interpreters for External Language Scripts

← Nächstältere Version		Version vom 14. Juni 2018, 16:30 Uhr
Zeile 24:		Zeile 24:

	If no script interpreter was defined in the settings dialog, fallbacks can be provided by the following shell variables:		If no script interpreter was defined in the settings dialog, fallbacks can be provided by the following shell variables:
	* '''CMD_SHELL''' (batch scripts; defaults to "cmd")		* '''CMD_SHELL''' (batch scripts; defaults to "<code>cmd</code>")
	* '''SHELL''' (shell commands and shell scripts; defaults to "bash" or "sh", whichever is found)		* '''SHELL''' (shell commands and shell scripts; defaults to "<code>bash</code>" or "<code>sh</code>", whichever is found)
	* '''POWERSHELL''' (powershell scripts; defaults to "powershell" or "pwsh", whichever is found)		* '''POWERSHELL''' (powershell scripts; defaults to "<code>powershell</code>" or "<code>pwsh</code>", whichever is found)
	* '''RUBY_SHELL''' (ruby scripts; defaults to "ruby")		* '''RUBY_SHELL''' (ruby scripts; defaults to "<code>ruby</code>")
	* '''PYTHON_SHELL''' (python scripts; defaults to "python")		* '''PYTHON_SHELL''' (python scripts; defaults to "<code>python</code>")
	* '''PERL_SHELL''' (perl scripts; defaults to "perl")		* '''PERL_SHELL''' (perl scripts; defaults to "<code>perl</code>")
	* '''TCL_SHELL''' (tcl scripts; defaults to "tclsh")		* '''TCL_SHELL''' (tcl scripts; defaults to "<code>tclsh</code>")
	* '''NODEJS_SHELL''' (node.js scripts; defaults to "node")		* '''NODEJS_SHELL''' (node.js scripts; defaults to "<code>node</code>")
	* '''GO_SHELL''' (go scripts; defaults to "go")		* '''GO_SHELL''' (go scripts; defaults to "<code>go</code>")
	* '''GNUPLOT_SHELL''' (gnuplot scripts; defaults to "gnuplot")		* '''GNUPLOT_SHELL''' (gnuplot scripts; defaults to "<code>gnuplot</code>")
	* '''RSCRIPT_SHELL''' ('R' scripts; defaults to "R.exe" on Windows, "r" on OSX, "R" on Unix/Linux)		* '''RSCRIPT_SHELL''' ('R' scripts; defaults to "<code>R.exe</code>" on Windows, "<code>r</code>" on OSX, "<code>R</code>" on Unix/Linux)

Cg: /* Temporary Files Folder */

2018-06-14T16:29:11Z

Temporary Files Folder

← Nächstältere Version		Version vom 14. Juni 2018, 16:29 Uhr
Zeile 18:		Zeile 18:
	The name of the temporary folder can be retrieved by evaluating and printing:		The name of the temporary folder can be retrieved by evaluating and printing:
	Filename tempDirectory		Filename tempDirectory
	(doing a "printIt" in a Smalltalk workspace),		(doing a "''printIt''" in a Smalltalk workspace),
	or via a corresponding action block in the standardlibrary.		or via a corresponding action block in the standardlibrary.

Cg: /* Script Interpreters for External Language Scripts */

2018-06-14T16:28:57Z

Script Interpreters for External Language Scripts

← Nächstältere Version		Version vom 14. Juni 2018, 16:28 Uhr
Zeile 26:		Zeile 26:
	* '''CMD_SHELL''' (batch scripts; defaults to "cmd")		* '''CMD_SHELL''' (batch scripts; defaults to "cmd")
	* '''SHELL''' (shell commands and shell scripts; defaults to "bash" or "sh", whichever is found)		* '''SHELL''' (shell commands and shell scripts; defaults to "bash" or "sh", whichever is found)
⚫	* '''GNUPLOT_SHELL''' (gnuplot scripts; defaults to "gnuplot")
⚫	* '''NODEJS_SHELL''' (node.js scripts; defaults to "node")
⚫	* '''PERL_SHELL''' (perl scripts; defaults to "perl")
	* '''POWERSHELL''' (powershell scripts; defaults to "powershell" or "pwsh", whichever is found)		* '''POWERSHELL''' (powershell scripts; defaults to "powershell" or "pwsh", whichever is found)
⚫	* '''PYTHON_SHELL''' (python scripts; defaults to "python")
⚫	* '''RSCRIPT_SHELL''' ('R' scripts; defaults to "R.exe" on Windows, "r" on OSX, "R" on Unix/Linux)
	* '''RUBY_SHELL''' (ruby scripts; defaults to "ruby")		* '''RUBY_SHELL''' (ruby scripts; defaults to "ruby")
		⚫	* '''PYTHON_SHELL''' (python scripts; defaults to "python")
		⚫	* '''PERL_SHELL''' (perl scripts; defaults to "perl")
	* '''TCL_SHELL''' (tcl scripts; defaults to "tclsh")		* '''TCL_SHELL''' (tcl scripts; defaults to "tclsh")
		⚫	* '''NODEJS_SHELL''' (node.js scripts; defaults to "node")
			* '''GO_SHELL''' (go scripts; defaults to "go")
		⚫	* '''GNUPLOT_SHELL''' (gnuplot scripts; defaults to "gnuplot")
		⚫	* '''RSCRIPT_SHELL''' ('R' scripts; defaults to "R.exe" on Windows, "r" on OSX, "R" on Unix/Linux)

Cg: /* Temporary Files Folder */

2018-06-14T16:27:29Z

Temporary Files Folder

← Nächstältere Version		Version vom 14. Juni 2018, 16:27 Uhr
Zeile 18:		Zeile 18:
	The name of the temporary folder can be retrieved by evaluating and printing:		The name of the temporary folder can be retrieved by evaluating and printing:
	Filename tempDirectory		Filename tempDirectory
	("printIt" in a Smalltalk workspace).		(doing a "printIt" in a Smalltalk workspace),
	or via a corresponding action block in the standardlibrary.		or via a corresponding action block in the standardlibrary.

Cg: /* Temporary Files Folder */

2018-06-14T16:27:01Z

Temporary Files Folder

← Nächstältere Version		Version vom 14. Juni 2018, 16:27 Uhr
Zeile 8:		Zeile 8:

	By default, temporary files are created inside a per-session temporary folder.		By default, temporary files are created inside a per-session temporary folder.
	This per-session temporary folder is named "stx_tmp_xxxx" and is created in the ''tempdir'' folder.		This per-session temporary folder is named "<code>stx_tmp_xxxx</code>" (where xxxx is a session/process-ID) and is created in the ''tempdir'' folder.
	The ''tempdir'' folder is specified by any of: STX_TMPDIR, TMP_DIR, TEMP_DIR, TMPDIR or TEMPDIR,		The ''tempdir'' folder is specified by any of: <code>STX_TMPDIR</code>, <code>TMP_DIR</code>, <code>TEMP_DIR</code>, <code>TMPDIR</code> or <code>TEMPDIR</code>,
	whichever is found in the shell environment.		whichever is found in the shell environment.
	If none of the above is found in the shell environment, "/tmp" is used as tempdir.		If none of the above is found in the shell environment, "<code>/tmp</code>" is used as tempdir.

	All per-session temporary files are created in this one temporary folder, to make it easier to cleanup leftover session files. Actually, if no expecco/Smalltalk is running, all temporary files folders named "stx_tmp_xxx" can be removed without danger (although temp-file cleanup is typically done automatically by the operating system in regular intervals)		All per-session temporary files are created in this one temporary folder, to make it easier to cleanup leftover session files.
			Actually, if no expecco/Smalltalk is running, all temporary file folders named "<code>stx_tmp_xxx</code>" can be removed without danger (although temp-file cleanup is typically done automatically by the operating system in regular intervals)

	The name of the temporary folder can be retrieved by evaluating and printing:		The name of the temporary folder can be retrieved by evaluating and printing:

Cg: /* Script Interpreters for External Language Scripts */

2018-06-05T04:29:46Z

Script Interpreters for External Language Scripts

← Nächstältere Version		Version vom 5. Juni 2018, 04:29 Uhr
Zeile 33:		Zeile 33:
	* '''RUBY_SHELL''' (ruby scripts; defaults to "ruby")		* '''RUBY_SHELL''' (ruby scripts; defaults to "ruby")
	* '''TCL_SHELL''' (tcl scripts; defaults to "tclsh")		* '''TCL_SHELL''' (tcl scripts; defaults to "tclsh")


	PYTHON_SHELL,