02.05.2013 Views

Description - Mks.com

Description - Mks.com

Description - Mks.com

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

NAME<br />

envvar — standard environment variables<br />

SYNOPSIS<br />

export NAME=value<br />

set NAME=value<br />

echo $NAME<br />

DESCRIPTION<br />

envvar -- Miscellaneous Information<br />

When a process is executed, it inherits a set of strings called the environment. It is conventional for<br />

these strings to have the form:<br />

NAME=value<br />

The export <strong>com</strong>mand built into the MKS KornShell can be used to set the variable NAME into the<br />

environment of every child process. The set <strong>com</strong>mand built into <strong>com</strong>mand.<strong>com</strong> or cmd.exe does<br />

the same. The echo <strong>com</strong>mand prints the value of environment variable NAME inside the MKS<br />

KornShell.<br />

Note:<br />

The shell maintains additional shell variables that are not exported to child processes;<br />

because these variables are not passed on, they are not environment variables.<br />

The following environment variables are used throughout MKS Toolkit:<br />

COLUMNS<br />

If you set this variable to a numeric value, various <strong>com</strong>mands use its value as the width of<br />

the output device in columns. This overrides the default.<br />

COMSPEC<br />

The value of this variable must point to the standard <strong>com</strong>mand interpreter (<strong>com</strong>mand.<strong>com</strong> or<br />

cmd.exe), if you want to use that <strong>com</strong>mand interpreter in any way. This variable is called<br />

ComSpec under Windows NT/2000/XP/2003.<br />

ENV<br />

327 of 457

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!