setenv
no way to compare when less than two revisions
Differences
This shows you the differences between two versions of the page.
— | setenv [2006/08/29 20:18] (current) – created - external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | #$EPIC: setenv.txt, | ||
+ | ======Synopsis: | ||
+ | __setenv__ < | ||
+ | __setenv__ -< | ||
+ | |||
+ | ======Description: | ||
+ | In the first usage, __SETENV__ sets the environment variable < | ||
+ | to < | ||
+ | you [[exec command|EXEC]]. | ||
+ | variable < | ||
+ | [[exec command|EXEC]] processes. | ||
+ | |||
+ | Some systems (like Solaris) make changing and deleting environment | ||
+ | variables painful. | ||
+ | warning advising you that setting an environment variable will result | ||
+ | in a memory leak which is unavoidable. | ||
+ | have an easy way to unset environment variables. | ||
+ | get a warning telling you this. | ||
setenv.txt · Last modified: 2006/08/29 20:18 by 127.0.0.1