diff options
author | jnweiger <jnweiger> | 2005-12-16 17:25:08 +0000 |
---|---|---|
committer | jnweiger <jnweiger> | 2005-12-16 17:25:08 +0000 |
commit | a5c2d002715930526cf968553c73a317ac4086fd (patch) | |
tree | cd2ea47d7d1ebe0c2b3e5d87e6972a0ec2829e9d /src/README | |
parent | c81f3249a4a75d1aa9b9070673c7170e9401c32e (diff) | |
download | screen-a5c2d002715930526cf968553c73a317ac4086fd.tar.gz |
historic version screen-3.3.4 Oct 21 2002
Diffstat (limited to 'src/README')
-rw-r--r-- | src/README | 56 |
1 files changed, 0 insertions, 56 deletions
diff --git a/src/README b/src/README deleted file mode 100644 index ee8cd0e..0000000 --- a/src/README +++ /dev/null @@ -1,56 +0,0 @@ -"screen" is a window manager that allows you to handle several independent -screens (UNIX ttys) on a single physical terminal; each screen has its own -set of processes connected to it (typically interactive shells). Each -virtual terminal created by "screen" emulates a DEC VT100 plus several ANSI -X3.64 and ISO 2022 functions (including DEC VT102 features such as line and -character deletion and insertion). - -Since "screen" uses pseudo-ttys, the select system call, and UNIX-domain -sockets, it will not run under a system that does not include these -features of 4.2 and 4.3 BSD UNIX. - -To compile and install screen: - -Read through the "Site Configuration" section of config.h.in, and edit -it to suit your site. Each define is well commented to help you decide -what to choose. Then follow the instructions in the file INSTALL. -A comment near the top of config.h.in explains why it's best to -install screen setuid to root. - - -If you want to get a quick idea how "screen" works but don't want to read -the entire manual, do the following: - - - run "screen" without arguments - - wait for the shell prompt; execute some commands - - type ^A ^C (Control-A followed by Control-C) - - wait for the shell prompt; do something in the new window - - type ^A ^A repeatedly to switch between the two windows - - terminate the first shell ("screen" switches to the other window) - - terminate the second shell - -If you have "vttest" (the VT100 test program from mod.sources) you -may want to run it from within "screen" to verify that it correctly -emulates a VT100 on your terminal (except for things your terminal is -incapable of handling, like 132 column mode and double width/height -characters, of course). - -By the way, "screen" can be used to compensate for certain bugs of "real" -VT100 terminals. For instance, our 4.2 BSD version of mille(6) garbles -the display on terminals of the VT100 family, but it works quite fine -when it is invoked from within "screen". In addition, "screen" enables -you to use EMACS on terminals that are unable to generate Control-S and -Control-Q from the keyboard or that require flow control using Control-S -and Control-Q. This is the reason why I have an alias like - - alias emacs "screen emacs" - -in my .cshrc file. Users who run EMACS on terminals which normally have no -trouble with Control-S and Control-Q will probably want to run screen with -the -fn or -fa options, or put the line "flow off" or "flow auto" in their -.screenrc file. - -Send your questions, comments and bug reports for screen to: - jnweiger@immd4.informatik.uni-erlangen.de (Juergen Weigert) -and also to: - bug-gnu-utils@prep.ai.mit.edu |