diff options
| author | Jan Christoph Nordholz <hesso@pool.math.tu-berlin.de> | 2009-12-18 16:42:12 -0500 |
|---|---|---|
| committer | Sadrul Habib Chowdhury <sadrul@users.sourceforge.net> | 2009-12-18 16:42:12 -0500 |
| commit | f6c4b82a35420b679af178dbcb17f4225723dea3 (patch) | |
| tree | 744e4222988cfecbdc3374597977b5021a3c47de | |
| parent | 1e450254e75877b6bb5cacedd5466245dbb54576 (diff) | |
| download | screen-f6c4b82a35420b679af178dbcb17f4225723dea3.tar.gz | |
Clarify the manual a little.
Document the fact that when calling 'env=var screen app arg' from inside
screen the environment variable will go up in smoke.
| -rw-r--r-- | src/doc/screen.1 | 4 | ||||
| -rw-r--r-- | src/doc/screen.texinfo | 3 |
2 files changed, 6 insertions, 1 deletions
diff --git a/src/doc/screen.1 b/src/doc/screen.1 index 1c75652..de3df24 100644 --- a/src/doc/screen.1 +++ b/src/doc/screen.1 @@ -97,7 +97,9 @@ but will instead supply the command name and its arguments to the window manager (specified in the $STY environment variable) who will use it to create the new window. The above example would start the emacs editor (editing prog.c) and switch -to its window. +to its window. - Note that you cannot transport environment variables from +the invoking shell to the application (emacs in this case), because it is +forked from the parent screen process, not from the invoking shell. .PP If \*Q/etc/utmp\*U is writable by .IR screen , diff --git a/src/doc/screen.texinfo b/src/doc/screen.texinfo index a56e02f..0bed653 100644 --- a/src/doc/screen.texinfo +++ b/src/doc/screen.texinfo @@ -175,6 +175,9 @@ run another copy of @code{screen}, but will instead supply the command name and its arguments to the window manager (specified in the $STY environment variable) who will use it to create the new window. The above example would start the @code{emacs} editor (editing @file{prog.c}) and switch to its window. +- Note that you cannot transport environment variables from +the invoking shell to the application (emacs in this case), because it is +forked from the parent screen process, not from the invoking shell. If @file{/etc/utmp} is writable by @code{screen}, an appropriate record will be written to this file for each window, and removed when the |