|
|
1.1 root 1:
2:
3: export Command export
4:
5:
6:
7:
8: Add shell variables to environment
9:
10: eexxppoorrtt [_n_a_m_e ...]
11: eexxppoorrtt [_n_a_m_e=_v_a_l_u_e]
12:
13: When the shell sh executes a command, it passes the command an
14: environment. By convention, the environment consists of as-
15: signments, each of the form name=value. For example, typing
16:
17:
18: export TERM=vt100
19:
20:
21: sets the environmental variable TERM to equal the string vt100.
22:
23: A command may look for information in the environment or may
24: simply ignore it. In the above example, a program that reads the
25: variable TERM (such as MicroEMACS) will assume that you are
26: working on a DEC VT-100 terminal or one that emulates it.
27:
28: The shell places the name and the value of each shell variable
29: that appears in an export command into the environment of subse-
30: quently executed commands. It does not place a shell variable
31: into the environment until it appears in an export command.
32:
33: With no arguments, export prints the name and the value of each
34: shell variable currently marked for export.
35:
36: The shell executes export directly.
37:
38: ***** See Also *****
39:
40: commands, environ, exec, sh
41:
42:
43:
44:
45:
46:
47:
48:
49:
50:
51:
52:
53:
54:
55:
56:
57:
58:
59:
60:
61:
62:
63:
64: COHERENT Lexicon Page 1
65:
66:
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.