+prefix = @prefix@

+mandir = @mandir@

+infodir = @infodir@

+From bargi@dots.physics.orst.edu Thu Aug 31 23:42 MET 1995

+Received: from faui45.informatik.uni-erlangen.de (root@faui45.informatik.uni-erlangen.de [131.188.34.45]) by immd4.informatik.uni-erlangen.de with ESMTP

+ id XAA14775 (8.6.12/7.4f-FAU);; Thu, 31 Aug 1995 23:42:15 +0200

+Received: from dots.physics.orst.edu (bargi@dots.PHYSICS.ORST.EDU [128.193.96.106]) by uni-erlangen.de with ESMTP

+ id XAA03048 (8.6.12/7.4f-FAU); for <screen@uni-erlangen.de>; Thu, 31 Aug 1995 23:42:03 +0200

+Received: (from bargi@localhost) by dots.physics.orst.edu (8.6.11/8.6.9) id OAA15627; Thu, 31 Aug 1995 14:41:47 -0700

+From: Hadi Bargi Rangin <bargi@dots.physics.orst.edu>

+Message-Id: <199508312141.OAA15627@dots.physics.orst.edu>

+Subject: README.DOTSCREEN

+To: screen@uni-erlangen.de

+Date: Thu, 31 Aug 1995 14:41:47 -0700 (PDT)

+Cc: bargi@dots.physics.orst.edu (Hadi Bargi Rangin)

+X-Mailer: ELM [version 2.4 PL24]

+MIME-Version: 1.0

+Content-Transfer-Encoding: 7bit

+Content-Type: text/plain; charset=US-ASCII

+Content-Length: 5423

+Status: RO

+

+Hallo,

+

+ leider war readme file fuer dotscreen nicht in unserem dotscreen-Packet,

+deshalb schicke ich es Euch nachtraeglich. Nachdem Ihr unseren packet

+getestet habt, koennen wir Euch anrufen und vielleicht mehr ueber die

+Einzelnheiten sprechen, ob wir unsere Weiterentwicklung koordinieren

+wollen.

+

+Danke,

+

+Gruss,

+Hadi

+

+===============================================================================

+Quick introduction to dotscreen

+-------------------------------

+

+1. Introduction

+2. Is dotscreen different as screen?

+3. Installation instructions

+4. Functions description

+5. Further development

+

+

+1. Introduction

+===============

+

+Dotscreen, is a system which allow a person direct access to unix via

+a braille display. The emphasis is on direct, because the braille

+display is connected directly to the serial port on the unix

+machine. You no longer must use a dos machine running a terminal

+emulation logged into a unix machine. Dotscreen is built on top of

+screen, a powerful full-screen window manager for unix tty terminals.

+Screen keeps track of what is being displayed in each window that it

+is managing so that it can easily switch back and forth between these

+windows. Dotscreen makes this stored window information available via

+a braille display. Dotscreen only allows access to tty terminal

+sessions, it does not allow access to X-Windows, however, it will run

+in an xterm window. Currently, it works with the TSI Navigator 40 and

+the TSI PowerBraille 40 braille displays. We plan to support other

+displays as demand and information about other displays is made

+available to us

+

+2. Is dotscreen different than screen?

+======================================

+

+All of screens functions still work in dotscreen. A few of the

+functions are not accessible via braille, but we expect to remedy that

+in future releases.

+

+3. Installation instructions

+============================

+

+Please read the INSTALL file for full installation instructions.

+In addition to those instructions, note that you must create

+a .screenrc file and that file must contain the type of braille

+display that you are using and the serial device that the display

+is connected to. A minimal .screenrc file should contain something

+like the following four lines, (these are only examples, please

+customize them for your configuration)

+

+

+# example of .screenrc when using braille display

+bd_start_braille on

+bd_type powerbraille_40

+bd_port /dev/ttyS0

+bd_braille_table /home/gardner/us-braille.tbl

+# end of example

+

+

+4. Functions description

+========================

+

+The basic operation of screen is described in README. The braille

+navigation commands are similar to commands usually found on dos

+braille screenreaders. Also, because dotscreen is built on top of

+screen, the user can switch back and forth easily between many running

+applications. The braille commands can be changed any time after

+starting screen using the internal screen "C-a :" command line. All

+braille commands begin with "bd_"; following is the list of braille

+commands:

+

+bd_start_braille on/off # Starts/stops using braille features on screen

+bd_link on/off # links/unlinks braille cursor to/from screen cursor

+bd_bell on/off # turn on/off sending bell-signal to terminal

+bd_scroll on/off # enables/disables scrolling

+bd_skip on/off # skip/don't skip balnk lines

+bd_width <integer-value> # number of braille cells that user want to use,

+ # this value is always <= total number of cells

+bd_ncrc <interger-value> # number of cells displayed on the right side

+ # of physical cursor (default = 1)

+bd_info <integer-value> # displays braille/screen cursor position

+ # depending on its value, (no info: 0, only

+ # bc-info: 1, only sc-info: 2, bc- and sc-info: 3

+bd_port <serial-device> # serial port which braille display is connected to

+bd_braille_table <bl-table> # braille table to be used. German, US and GS

+ # braille tables are provided

+bd_type <braille-display-type>

+ # braille display type being used

+

+Note: currently valid value for some parameters:

+bd_type:

+ 1. navigator_40

+ 2. powerbraille_40.

+

+bd_braille_table:

+ 1. gr-braille.tbl German braille code

+ 2. us-braille.tbl US computer braille code

+ 3. gs-braille.tbl GS braille code

+

+Since the braille tables are in files, you should give the full

+pathnames of the files either in .screenrc or using the

+internal screen "C-a :" command line.

+

+5. Further development

+======================

+

+As mentioned above, currently Dotscreen works with Telesensory braille

+displays the PowerBraille and the Navigator because Telesensory has

+given us the information needed to program their braille display. We

+plan to add support for other braille displays when and if we get the

+requisite information from the braille display manufacturer.

+Also some things such as cursor navigation from the braille display

+have not been implemented. If you find a feature missing that

+you wish to have, please contact us.

+

+This software has been developed within the Science Access Project at

+Oregon State University under the direction of John Gardner.

+

+Authors: Hadi Bargi Rangin (bargi@dots.physics.orst.edu)

+ Bill Barry (barryb@dots.physics.orst.edu)

+

+../install.sh \ No newline at end of file

+######

+######

+###### The following lines should be obsolete because of the 'configure' script.

+###### It is here only for reference if 'configure' needs human help.

+######

+

+

+### If you choose to compile with the tried and true:

+#CC= cc

+#CFLAGS= -O

+#CFLAGS= -g

+### gcc specific CFLAGS:

+#CC= gcc

+# If your system include files are bad, don't use -Wall

+#CFLAGS= -O6 -g #-Wall

+#CFLAGS = -g -fstrength-reduce -fcombine-regs -finline-functions #-Wall

+

+### On some machines special CFLAGS are required:

+#M_CFLAGS=

+#M_CFLAGS= -D__NetBSD__ # NetBsd Machines like this (a.kalb@rrze)

+#M_CFLAGS= -Dapollo -A cpu,mathchip -A nansi # Apollo DN3000/4000/4500

+#M_CFLAGS= -DISC -D_POSIX_SOURCE # isc

+#M_CFLAGS= -systype bsd43 -DMIPS # mips

+#M_CFLAGS= -fforce-mem -fforce-addr\

+# -fomit-frame-pointer -finline-functions -bsd # NeXT

+#M_CFLAGS= -qlanglvl=ansi # RS6000/AIX

+#M_CFLAGS= -qlanglvl=ansi -D_AIX32 # RS6000/AIX 3.2

+#M_CFLAGS= -ansi # sgi/IRIX 3.x ansi

+#M_CFLAGS= -xansi # sgi/IRIX 4.x ext ansi

+#M_CFLAGS= -YBSD # Ultrix 4.x

+#M_CFLAGS= -DSVR4=1 # Bob Kline rvk@blink.att.com 80386 Unix SVR4.0

+#M_CFLAGS= -D_CX_UX # Ken Beal kbeal@amber.ssd.csd.harris.com Harris CX/UX

+#M_CFLAGS= -K pentium # Thanh Ma tma@encore.com Unixware, SVR4-2

+

+### Choose one of the LIBS setting below:

+#LIBS= -ltermcap -lc -lsocket -linet -lsec -lseq # Sequent/ptx

+#LIBS= -lcurses -lelf -lcrypt -lsocket -lnsl # Solaris, when it sucks

+#LIBS= -ltermcap # SunOS, Linux, Apollo,

+# gould_np1, NeXT, Ultrix

+#LIBS= -ltermcap -lelf # SVR4

+#LIBS= -ltermlib -linet -lcposix # isc

+#LIBS= -ltermcap -lmld # mips (nlist is in mld)

+#LIBS= -ltermlib -lsun -lmld #-lc_s # sgi/IRIX

+#LIBS= -lcurses # RS6000/AIX

+#LIBS= -lcrypt_d -ltinfo # sco32

+#LIBS= -lcrypt_i -ltinfo # sco32

+#LIBS= -lcrypt -lsec # sco322 (msilano@sra.com)

+#LIBS= -ltermcap -lcrypt.o -ldir -lx # SCO XENIX 2.3.4

+#LIBS= -ltermcap -lcrypt -ldir -l2.3 -lx # SCO UNIX XENIX cross dev.

+#LIBS= -ltermcap -lelf -lcrypt -lsocket -lnet -lnsl # Bob Kline SVR4

+#LIBS= -lcurses -lelf -lcrypt -lgen # Thanh Ma, Unixware, SVR4-2

+.TH SCREEN 1 "10 Jun 1999"

+[[\fIpid\fP\fB.\fP]\fItty\fP[\fB.\fP\fIhost\fP]]

+.br

+.B screen \-r

+\fIsessionowner\fP\fB/\fP[[\fIpid\fP\fB.\fP]\fItty\fP[\fB.\fP\fIhost\fP]]

+from the ISO 6492 (ECMA 48, ANSI X3.64) and ISO 2022 standards

+in whatever manner you wish, etc. All windows run their programs completely

+independent of each other. Programs continue to run when their window

+is currently not visible and even when the whole

+.I screen

+session is detached from the user's terminal. When a program terminates,

+.I Screen

+does not understand the prefix \*QC-\*U to mean control.

+Please use the caret notation (\*Q^A\*U instead of \*QC-a\*U) as arguments

+to e.g. the

+.I escape

+command or the

+.I -e

+option.

+.I Screen

+will also print out control characters in caret notation.

+.PP

+.IR screen .

+If all you've got is a \*Qtrue\*U auto-margin terminal

+.I screen

+.IR screen 's

+If no session can be detached, this option is ignored. In combination with the

+\fB\-r\fP/\fB\-R\fP option more powerful effects can be achieved:

+.TP 8

+.B \-d \-r

+Reattach a session and if necessary detach it first.

+.TP 8

+.B \-d \-R

+Reattach a session and if necessary detach or even create it first.

+.TP 8

+.B \-d \-RR

+Reattach a session and if necessary detach or create it. Use the first

+session if more than one session is available.

+.TP 8

+.B \-D \-r

+Reattach a session. If necessary detach and logout remotely first.

+.TP 8

+.B \-D \-R

+Attach here and now. In detail this means: If a session is running, then

+reattach. If necessary detach and logout remotely first.

+If it was not running create it and notify the user. This is the

+author's favorite.

+.TP 8

+.B \-D \-RR

+Attach here and now. Whatever that means, just do it.

+.IP "" 5

+Note: It is always a good idea to check the status of your sessions by means of

+`attached' are running and have a controlling terminal. If the session runs in

+multiuser mode, it is marked `multi'. Sessions marked as `unreachable' either

+live on a different host or are `dead'.

+An unreachable session is considered dead, when its name

+matches either the name of the local host, or the specified parameter, if any.

+See the \fB-r\fP flag for a description how to construct matches.

+Sessions marked as `dead' should be thoroughly checked and removed.

+Ask your system administrator if you are not sure. Remove sessions with the

+\fB-wipe\fP option.

+the screen. This can also be set in your .screenrc by specifying `LP' in a

+\*Qtermcap\*U command.

+session or not. This flag has a special meaning in connection

+with the `-d' option:

+.TP 8

+.B \-m \-d

+Start

+.I screen

+in \*Qdetached\*U mode. This creates a new session but doesn't

+attach to it. This is useful for system startup scripts.

+.TP 8

+.B \-m \-D

+This also starts screen in \*Qdetached\*U mode, but doesn't fork

+a new process. The command exits if the session terminates.

+.B \-q

+Suppress printing of error messages. In combination with \*Q-ls\*U the exit

+value is as follows: 9 indicates a directory without sessions. 10

+indicates a directory with running but not attachable sessions. 11 (or more)

+indicates 1 (or more) usable sessions.

+In combination with \*Q-r\*U the exit value is as follows: 10 indicates that

+there is no session to resume. 12 (or more) indicates that there are 2 (or

+more) sessions to resume and you should specify which one to choose.

+In all other cases \*Q-q\*U has no effect.

+.TP 5

+.PD 0

+.TP 5

+.BR \-r " \fIsessionowner/[" \fIpid.tty.host ]

+.PD

+session. No other options (except combinations with \fB\-d\fP/\fB\-D\fP) may

+be specified, though an optional prefix of [\fIpid.\fP]\fItty.host\fP

+sessions. The second form is used to connect to another user's screen session

+which runs in multiuser mode. This indicates that screen should look for

+sessions in another user's directory. This requires setuid-root.

+session it finds. If successful, all other command-line options are ignored.

+For combinations with the \fB\-d\fP/\fB\-D\fP option see there.

+.BR \-wipe " [" \fImatch ]

+An unreachable session is considered dead, when its name matches either

+the name of the local host, or the explicitly given parameter, if any.

+See the \fB-r\fP flag for a description how to construct matches.

+.IP "\fBC-a -\fP (select -)"

+.PD

+Switch to window number 0 \- 9, or to the blank window.

+.IP "\fBC-a tab\fP (focus)"

+Switch the input focus to the next region.

+unless overridden. For instance, if you use the option \*Q\fB\-e]x\fP\*U,

+this command becomes \*Q]]\*U.

+.IP "\fBC-a F\fP (fit)"

+Resize the window to the current region size.

+.IP "\fBC-a Q\fP (only)"

+Delete all regions but the current one.

+.IP "\fBC-a S\fP (split)"

+Split the current region into two new ones.

+.IP "\fBC-a X\fP (remove)"

+Kill the current region.

+current window.

+.IP "\fBC-a *\fP (displays)"

+Show a listing of all currently attached displays.

+is not running setuid-root, the user can specify any mode 700 directory

+global screenrc file

+screenrc file is searched in $SCREENRC, then $HOME/.screenrc.

+The command line option \fB-c\fP takes

+Commands may contain references to environment variables. The

+syntax is the shell-like "$VAR " or "${VAR}". Note that this causes

+incompatibility with previous

+Two configuration files are shipped as examples with your screen distribution:

+\*Qetc/screenrc\*U and \*Qetc/etcscreenrc\*U. They contain a number of

+useful examples for various commands.

+.PP

+.sp

+.RI [ crypted-pw ]

+.br

+.BI addacl " usernames"

+user or a comma separated list of users. This command enables to attach to the

+If an optional second parameter is supplied, it should be a crypted password

+for the named user(s). `Addacl' is a synonym to `acladd'.

+.sp

+.br

+.BI chacl " usernames permbits list"

+Change permissions for a comma separated list of users. Permission bits are

+represented as `r', `w' and `x'. Prefixing `+' grants the permission, `-'

+removes it. The third parameter is a comma separated list of commands and/or

+windows (specified either by number or title). The special list `#' refers to

+user obtains a writelock for this window.

+Other bits are currently ignored.

+To allow read-only access to the session: `aclchg \fIusername\fP

+-w \&"#\&"'. As soon as a user's name is known to

+.I screen

+he can attach to the session and (per default) has full permissions for all

+Rights of the special username

+.B nobody

+cannot be changed (see the \*Qsu\*U command).

+`Chacl' is a synonym to `aclchg'.

+.BI aclgrp " username"

+.RI [ groupname ]

+.PP

+Creates groups of users that share common access rights. The name of the

+group is the username of the group leader. Each member of the group inherits

+the permissions that are granted to the group leader. That means, if a user

+fails an access check, another check is made for the group leader.

+A user is removed from all groups the special value \*Qnone\*U is used for

+.IR groupname .

+If the second parameter is omitted all groups the user is in are listed.

+.sp

+.ne 3

+.B aclumask

+.RI [[ users ] +bits

+.RI |[ users ] -bits " .... ]"

+.B umask

+.RI [[ users ] +bits

+.RI |[ users ] -bits " .... ]"

+.PP

+This specifies the access other users have to windows that will be created by

+the caller of the command.

+.I Users

+may be no, one or a comma separated list of known usernames. If no users are

+specified, a list of all currently known users is assumed.

+.I Bits

+is any combination of access control bits allowed defined with the

+\*Qaclchg\*U command. The special username \*Q?\*U predefines the access

+that not yet known users will be granted to any window initially.

+The special username \*Q??\*U predefines the access that not yet known

+users are granted to any command.

+Rights of the special username

+.B nobody

+cannot be changed (see the \*Qsu\*U command).

+`Umask' is a synonym to `aclumask'.

+.sp

+.ne 3

+and each occurrence of `^G' is replaced by the definition for bell

+ 'Activity in window %n'

+This affects all windows and is useful for slow terminal lines. The

+default redraw behavior of newly created windows.

+setting) of the command. If the first parameter describes a

+non-unique context, the command will be executed multiple times. If the first

+user names. The command is executed once for each display of the selected

+user(s). If the first parameter is of the form `\fIidentifier\fP%' identifier

+is matched against displays. Displays are named after the ttys they

+If \fIidentifier\fP has a `#' or nothing appended it is matched against

+window numbers and titles. Omitting an identifier in front of the `#', `*' or

+what happened. Permission is checked for initiator of the \*Qat\*U command,

+not for the owners of the affected display(s).

+Note that the '#' character works as a comment introducer when it is preceded by

+whitespace. This can be escaped by prefixing a '\e'.

+Permission is checked for the initiator of the \*Qat\*U command, not for the

+owners of the affected display(s).

+.br

+Caveat:

+When matching against windows, the command is executed at least

+once per window. Commands that change the internal arrangement of windows

+(like \*Qother\*U) may be called again. In shared windows the command will

+be repeated for each attached display. Beware, when issuing toggle commands

+like \*Qlogin\*U!

+Some commands (e.g. \*Qstuff\*U, \*Qprocess\*U or \*Qpaste\*U) require that

+a display is associated with the target windows. These commands may not work

+correctly under \*Qat\*U looping over windows.

+Sets whether

+When turned off, a hangup signal will terminate

+.BR "autofixterm on" | off

+.PP

+Sets whether

+.I screen

+will add missing capabilities to the termcap/info entry. It is on

+by default.

+.sp

+.ne 3

+.B bell_msg

+.RI [ message ]

+The notification message can be re-defined by this command.

+and each occurrence of `^G' is replaced by the definition for bell

+ 'Bell in window %n'

+An empty message can be supplied to the \*Qbell_msg\*U command to suppress

+output of a message line (bell_msg "").

+Without parameter, the current message is shown.

+.BI "bind " key

+ bind ^k

+ bind k

+ bind K kill

+would also be available as \*QC-a space\*U). The next three lines

+remove the default kill binding from \*QC-a C-k\*U and \*QC-a k\*U.

+\*QC-a K\*U is then bound to the kill command. Then it

+binds \*QC-f\*U to the command \*Qcreate a window with a TELNET

+a superuser shell and a scrollback buffer of 1000 lines.

+option tells screen not to do inter-character timing. One cannot

+turn off the timing if a termcap capability is used.

+is omitted the key-binding is removed from the table.

+Make "foo" an abbreviation of the word "barfoo". Timeout is disabled

+This key-binding makes \*Q^T\*U an escape character for key-bindings. If

+For non-Posix systems the time interval may be rounded up to full seconds.

+Most useful if a character device is attached to the window rather than

+a shell process (See also chapter \*QWINDOW TYPES\*U). The maximum duration of

+a break signal is limited to 15 seconds.

+.sp

+.ne 3

+.B breaktype

+.RI [ tcsendbreak | TIOCSBRK

+.RI | TCSBRK ]

+.PP

+Choose one of the available methods of generating a break signal for

+terminal devices. This command should affect the current window only.

+But it still behaves identical to \*Qdefbreaktype\*U. This will be changed in

+the future.

+Calling \*Qbreaktype\*U with no parameter displays the break method for the

+current window.

+If the optional argument to the \*Qbufferfile\*U command is omitted,

+The following example will paste the system's password file into

+.BR "caption always" | splitonly

+.RI [ string ]

+.br

+.B "caption string"

+.RI [ string ]

+.PP

+This command controls the display of the window captions. Normally

+a caption is only used if more than one window is shown on the

+display (split screen mode). But if the type is set to

+.B always

+screen shows a caption even if only one window is displayed. The default

+is

+.BR splitonly .

+.P

+The second form changes the text used for the caption. You can use

+all escapes from the \*QSTRING ESCAPES\*U chapter. Screen uses

+a default of `%3n %t'.

+.P

+You can mix both forms by providing a string as an additional argument.

+.sp

+.ne 3

+Allows you to enter \*Q.screenrc\*U command lines. Useful

+for on-the-fly modification of key bindings,

+keyword no longer exists! Usually commands affect the current window rather

+starting with 'def...'.

+If you consider this as the `Ex command mode' of

+.sp

+.sp

+.ne 3

+.BR "compacthist " [ on | off ]

+.PP

+This tells screen weather to suppress trailing blank lines when

+scrolling up text into the history buffer.

+.sp

+Grabs or un-grabs the machines console output to a window.

+.IR Note :

+Only the owner of /dev/console can grab the console output.

+This command is only available if the machine supports the ioctl TIOCCONS.

+\fBh\fP, \fBj\fP, \fBk\fP, \fBl\fP move the cursor line by line or

+of the top, center or bottom line of the window.

+.br

+.br

+\fBC-u\fP and \fBC-d\fP scroll the display up/down by the specified amount of

+lines while preserving the cursor position. (Default: half screen-full).

+(E.\|g. markkeys "h=^B:l=^F:$=^E") There is no simple method for a full

+The copy range is specified by setting two marks. The text between these marks

+will be highlighted. Press

+\fBY\fP and \fBy\fP used to mark one whole line or to mark from

+\fBW\fP marks exactly one word.

+.br

+Any of these commands can be prefixed with a repeat count number by pressing

+digits

+is taken as a repeat count.

+.ti -2n

+does. Press

+given, both default to the current cursor position.

+Example: Try this on a rather full text screen:

+\fBJ\fP joins lines. It toggles between 4 modes: lines separated by a

+newline character (012), lines glued seamless, lines separated by a single

+whitespace and comma separated lines. Note that you can prepend the newline

+.I vi

+and 1. Press

+the screen-exchange file (/tmp/screen-exchange per default) once copy-mode is

+finished.

+This example demonstrates how to dump the whole scrollback buffer

+.BR "crlf " [ on | off ]

+to `on', lines will be separated by the two character sequence `CR' - `LF'.

+When no parameter is given, the state is toggled.

+Turns runtime debugging on or off. If

+has been compiled with option -DDEBUG debugging available and is turned on per

+default. Note that this command only affects debugging output from the main

+\*QSCREEN\*U process correctly. Debug output from attacher processes can only

+be turned off once and forever.

+.B defbreaktype

+.RI [ tcsendbreak | TIOCSBRK

+.RI | TCSBRK ]

+.PP

+Choose one of the available methods of generating a break signal for

+terminal devices. The preferred methods are

+.IR tcsendbreak " and " TIOCSBRK .

+The third,

+.IR TCSBRK ,

+blocks the complete

+.I screen

+session for the duration

+of the break, but it may be the only way to generate long breaks.

+.IR Tcsendbreak " and " TIOCSBRK

+may or may not produce long breaks with spikes (e.g. 4 per

+second). This is not only system dependant, this also differs between

+serial board drivers.

+Calling \*Qdefbreaktype\*U with no parameter displays the current setting.

+.sp

+.ne 3

+Set the default command characters. This is equivalent to the

+.BR "defflow on" | off | auto

+Same as the \fBflow\fP command except that the default setting for new windows

+.BR \-i .

+This was done to make a misinterpretation of program generated

+Same as the \fBlogin\fP command except that the default setting for new windows

+Same as the \fBmonitor\fP command except that the default setting for new

+Same as the \fBscrollback\fP command except that the default setting for new

+.BI "defshell " command

+.PP

+Synonym to the \fBshell\fP command. See there.

+.sp

+.ne 3

+.BR "defsilence on" | off

+.PP

+Same as the \fBsilence\fP command except that the default setting for new

+windows is changed. Initial setting is `off'.

+.sp

+.ne 3

+.BI "defslowpaste " msec"

+.PP

+Same as the \fBslowpaste\fP command except that the default setting for new

+windows is changed. Initial setting is 0 milliseconds, meaning `off'.

+.sp

+.ne 3

+Same as the \fBwrap\fP command except that the default setting for new

+windows is changed. Initially line-wrap is on and can be toggled with the

+Same as the \fBwritelock\fP command except that the default setting for new

+windows is changed. Initially writelocks will off.

+Detach the

+.B displays

+.PP

+Shows a tabular listing of all currently connected user front-ends (displays).

+This is most useful for multiuser sessions.

+.sp

+.ne 3

+will treat the following characters (up to three) as an octal

+active window to the file \*Q.termcap\*U in the user's

+\*Q$HOME/.screen\*U directory (or wherever

+like

+and then compile the entry with

+The echo command may be used to annoy

+day'. Typically installed in a global /local/etc/screenrc.

+The option \*Q-n\*U may be used to suppress the line feed.

+See also \*Qsleep\*U.

+command character (by triggering the \*Qmeta\*U command) to \fIy\fP (similar

+to the \-e option).

+Run a unix subprocess (specified by an executable path \fInewcommand\fP and its

+optional arguments) in the current window. The flow of data between

+newcommands stdin/stdout/stderr, the process originally started in the window

+(let us call it "application-process") and screen itself (window) is

+controlled by the filedescriptor pattern fdpat.

+descriptor to be connected to the application-process. A colon (:) combines

+User input will go to newcommand unless newcommand receives the

+application-process'

+output (fdpats first character is `!' or `:') or a pipe symbol (|) is added

+(as a fourth character) to the end of fdpat.

+running subprocess in this window. Only one subprocess a time can be running

+in each window.

+Refer to the postscript file `doc/fdpat.ps' for a confusing illustration

+`W' is the usual pty that has the application-process on its slave side.

+Abbreviations:

+Whitespace between the word `exec' and fdpat and the command

+can be omitted. Trailing dots and a fdpat consisting only of dots can be

+Creates another shell in the same window, while the original shell is still

+Set the speed of the window's tty. If your stty command operates on stdout,

+then add another `!'.

+give the user control over the pager although it gets its input from the

+.B fit

+.PP

+Change the window size to the size of the current region. This

+command is needed because screen doesn't adapt the window size

+automatically if the window is displayed more than once.

+.sp

+.ne 3

+Without parameters it cycles the current window's flow-control setting from

+See the discussion on \*QFLOW-CONTROL\*U later on in this document for full

+.B focus

+.PP

+Move the input focus to the next region. This is done in a cyclic

+way so that the top region is selected after the bottom one.

+.sp

+.ne 3

+Turn GR charset switching on/off. Whenever screen sees an input

+character with the 8th bit set, it will use the charset stored in the

+of the current window.

+If set to "on",

+will append to the "hardcopy.n" files created by the command \*QC-a h\*U,

+.br

+.BR "hardstatus \fR[\fBalways\fR]\fBlastline" | message | ignore

+.RI [ string ]

+.br

+.B "hardstatus string"

+.RI [ string ]

+.PP

+This command configures the use and emulation of the terminal's

+hardstatus line. The first form

+toggles whether

+.I screen

+will use the hardware status line to display messages. If the

+flag is set to `off', these messages

+are overlaid in reverse video mode at the display line. The default

+setting is `on'.

+.P

+The second form tells

+.I screen

+what to do if the terminal doesn't

+have a hardstatus line (i.e. the termcap/terminfo capabilities

+"hs", "ts", "fs" and "ds" are not set). If the type

+\*Qlastline\*U is used,

+.I screen

+will reserve the last line of the

+display for

+the hardstatus. \*Qmessage\*U uses

+.I screen's

+message mechanism and

+\*Qignore\*U tells

+.I screen

+never to display the hardstatus.

+If you prepend the word \*Qalways\*U to the type,

+.I screen

+will use the type even if the terminal supports a hardstatus.

+.P

+The third form specifies the contents of the hardstatus line.

+'%h' is used as default string, i.e. the stored hardstatus of the

+current window (settable via \\E]0;^G or \\E_\\\\) is displayed.

+You can customize this to any string you like including

+the escapes from the \*QSTRING ESCAPES\*U chapter. If you leave

+out the argument

+.IR string ,

+the current string is displayed.

+.P

+You can mix the second and third form by providing the string as

+additional argument.

+Not really a online help, but

+displays a help

+.I screen

+showing you all the key bindings.

+For example csh has the command \*Q!!\*U to repeat the last command executed.

+tries to find a previous line that matches with the `prompt character'

+scrollback buffer).

+.sp

+.ne 3

+.BI "hstatus " status

+.PP

+Change the window's hardstatus line to the string \fIstatus\fP.

+the terminal width and height plus the size of the scrollback buffer in lines,

+like in \*Q(80,24)+50\*U, the current state of window XON/XOFF flow control

+is shown like this (See also section FLOW CONTROL):

+

+.nf

+ +flow automatic flow control, currently on.

+ -flow automatic flow control, currently off.

+ +(+)flow flow control enabled. Agrees with automatic control.

+ -(+)flow flow control disabled. Disagrees with automatic control.

+ +(-)flow flow control enabled. Disagrees with automatic control.

+ -(-)flow flow control disabled. Agrees with automatic control.

+.fi

+

+The current line wrap setting (`+wrap' indicates enabled, `\-wrap' not) is

+also shown. The flags `ins', `org', `app', `log', `mon' or `nored' are

+displayed when the window is in insert mode, origin mode,

+application-keypad mode, has output logging,

+insert mode, origin mode, application-keypad mode, output logging,

+activity monitoring or partial redraw enabled.

+

+The currently active character set (\fIG0\fP, \fIG1\fP, \fIG2\fP,

+or \fIG3\fP) and in square brackets the terminal character sets that are

+currently designated as \fIG0\fP through \fIG3\fP is shown.

+

+Additional modes depending on the type of the window are displayed at the end of the status line (See also chapter \*QWINDOW TYPES\*U).

+.br

+If the state machine of the terminal emulator is in a non-default state,

+the info line is started with a string identifying the current state.

+.br

+Tell

+.I screen

+how to process kanji input/output. The first argument

+a different type. The optional second parameter tells

+.I screen

+.br

+(shell) running in the window receives a HANGUP condition,

+the window structure is removed and

+.I screen

+(your display) switches to another

+window. When the last window is destroyed,

+After a kill

+.I screen

+switches to the previously displayed window.

+.br

+Useful if you're typing when a message appears, because the message goes

+is started without options, which should be often enough. See also

+terminates. Meanwhile processes in the windows may continue, as the windows

+environment variable $LOCKPRG (which must be set in the shell from which

+.br

+Warning:

+When you leave other shells unlocked and you have no password set on

+.IR screen ,

+the lock is void: One could easily re-attach from an unlocked

+shell. This feature should rather be called `lockterminal'.

+Start/stop writing output of the current window to a file

+\*Qscreenlog.\fIn\fP\*U in the window's default directory, where \fIn\fP

+of logging is toggled. The session log is appended to the previous contents

+of the file if it already exists. The current contents and the contents

+.br

+.BI "logfile flush " secs

+\*Qscreenlog.%n\*U. The second form changes the number of seconds

+.I screen

+will wait before flushing the logfile buffer to the file-system. The

+default value is 10 seconds.

+The default setting (in config.h.in) should be \*Qon\*U for a

+Use the \*Qdeflogin\*U command to change the default login state for new

+windows. Both commands are only present when

+.BR "logtstamp " [ on | off ]

+.br

+.B "logtstamp after"

+.RI [ secs ]

+.br

+.B "logtstamp string"

+.RI [ string ]

+.PP

+This command controls logfile time-stamp mechanism of

+.I screen.

+If

+time-stamps are turned \*Qon\*U,

+.I screen

+adds a string containing

+the current time to the logfile after two minutes of inactivity.

+When output continues and more than another two minutes have passed,

+a second time-stamp is added to document the restart of the

+output. You can change this timeout with the second form

+of the command. The third form is used for customizing the time-stamp

+string (`-- %n:%t -- time-stamp -- %M/%d/%y %c:%s --\\n' by

+default).

+.sp

+.ne 3

+Tell

+.I screen

+that the next input character should only be looked up

+Set the inter-character timer for input sequence detection to a timeout

+separated by `:'. Example: The string \*QB=^B:F=^F\*U will change the

+If your terminal sends characters, that cause you to abort copy mode,

+then this command may help by binding these characters to do nothing.

+The no-op character is `@' and is used like this: \*Qmarkkeys

+@=L=H\*U if you do not want to use the `H' or `L' commands any longer.

+As shown in this example, multiple keys can be assigned to one function in a

+single statement.

+Defines the time

+.I screen

+delays a new message when one message is currently displayed.

+Defines the time a message is displayed if

+`aclchg', `aclgrp' and `acldel'

+can be used to enable (and disable) other users accessing this

+.I screen

+session.

+This option is only

+default setting is then determined by the presence of the environment

+.B nonblock

+.RB [ on | off ]

+.PP

+Enable or disable flow control for the current user interface (display).

+It is used to prevent a slow display from slowing down the processing of

+data output by a window. This command may be helpful when multiple displays

+show the same window. Nonblock is initially off for all displays.

+.sp

+.ne 3

+Change the current windows number. If the given number \fIn\fP is already

+.B only

+.PP

+Kill all regions but the current one.

+.sp

+.ne 3

+Switch to the window displayed previously. If this window does no longer exist,

+\fIother\fP has the same effect as \fInext\fP.

+Default is `off', of course. This default is fixed, as there is currently no

+paste buffer. If no parameter is given the user is prompted for a single

+The paste buffer can be filled with the \fIcopy\fP, \fIhistory\fP and

+\fIreadbuf\fP commands.

+Other registers can be filled with the \fIregister\fP, \fIreadreg\fP and

+registers is pasted into the named destination register rather than

+Note, that \*Qpaste\*U uses a wide variety of resources: Whenever a second

+only contains registers (not the paste buffer) then there need not be a current

+display (terminal attached), as the registers are a global resource. The

+Tell

+.I screen

+to include font information in the paste buffer. The

+default is not to do so. This command is especially useful for

+Power detach.

+CAUTION: This will result in a logout, when

+.B pow_detach_msg

+.RI [ message ]

+performed. It may be used as a replacement for a logout message or to reset

+baud rate, etc.

+Without parameter, the current message is shown.

+is not an empty string,

+.I screen

+will not use the terminal capabilities

+Stuff the contents of the specified register into

+.IR screen 's

+Reads the contents of the current screen-exchange file into the paste buffer.

+.B readreg

+or entered at the prompt. With two arguments it reads the contents of the named

+The following example will paste the system's password file into

+the

+.I screen

+window (using register p, where a copy remains):

+.B "remove"

+.PP

+Kill the current region. This is a no-op if there is only one region.

+.sp

+.ne 3

+Unlinks the screen-exchange file used by the commands \*Qwritebuf\*U and

+\*Qreadbuf\*U.

+.PP

+, terminal type option (\fB-T\fP <term>), the all-capability-flag (\fB-a\fP)

+and scrollback option (\fB-h\fP <num>) may be specified with each command.

+The option (\fB-M\fP) turns monitoring on for this window.

+The option (\fB-L\fP) turns output logging on for this window.

+ screen -fn -t foobar -L 2 telnet foobar

+in window #2) and will write a logfile (\*Qscreenlog.2\*U) of the telnet

+session.

+Note, that unlike previous versions of

+no additional default window is created when \*Qscreen\*U commands are

+.br

+Screen has built in some functionality of \*Qcu\*U and \*Qtelnet\*U.

+See also chapter \*QWINDOW TYPES\*U.

+Set the size of the scrollback buffer for the current windows to \fInum\fP

+See also the \*Qdefscrollback\*U command and use \*QC-a i\*U to view the

+.BR "select " [ \fIWindowID ]

+Switch to the window identified by \fIWindowID\fP.

+This can be a prefix of a window title (alphanumeric window name) or a window

+number.

+The parameter is optional and if omitted, you get prompted for an identifier.

+Thus, the first window can be activated by \*Qselect 0\*U.

+The number of windows is limited at compile-time by the MAXWIN

+configuration parameter.

+is omitted, the name of this session is displayed. Caution: The $STY

+environment variables still reflects the old name. This may result in

+confusion.

+.B "setenv "

+timeout can be changed with the `silencewait' command or by specifying a

+.B "slowpaste \fImsec\fP"

+Define the speed at which text is inserted into the current window by the

+paste ("C-a ]") command.

+will make a pause of \fImsec\fP milliseconds after each single character write

+to allow the application to process its input. Only use slowpaste if your

+underlying system exposes flow control problems while pasting large amounts of

+text.

+Change the way

+.I screen

+does highlighting for text marking and printing messages.

+foreground/background of the highlighted text.

+Some knowledge of

+.IR screen 's

+internal character representation is

+.B split

+.PP

+Split the current region into two new ones. All regions on the

+display are resized to make room for the new region. The blank

+window is displayed on the new region.

+.sp

+.ne 3

+large buffers with the \*Qstuff\*U command. It is most useful for key

+.B su

+.RB [ username " [" password

+.RB [ password2 ]]

+.PP

+Substitute the user of a display. The command prompts for all parameters that

+are omitted. If passwords are specified as parameters, they have to be

+specified un-crypted. The first password is matched against the systems

+passwd database, the second password is matched against the

+.I screen

+password as set with the commands \*Qacladd\*U or \*Qpassword\*U.

+\*QSu\*U may be useful for the

+.I screen

+administrator to test multiuser setups.

+.\" XXX removed in 3.8.0 XXX

+.\" but it is mainly used implicitly

+.\" by the \*Qconnect\*U command to identify users that access a remote session.

+When the identification fails, the user has access to the commands available

+for user

+.BR nobody .

+These are \*Qdetach\*U, \*Qlicense\*U, \*Qversion\*U, \*Qhelp\*U and

+\*Qdisplays\*U.

+.sp

+.ne 3

+The windows are in the `detached' state, while

+.I screen

+opens, the $TERM variable is set to \*Qscreen\*U by default.

+\*Qvt100\*U. This won't do much harm, as

+Use this command to modify your terminal's termcap entry without going

+through all the hassles involved in creating a custom termcap entry.

+You have to place these commands in one of the screenrc startup files, as

+they are meaningless once the terminal emulator is booted.

+.br

+If your system works uses the terminfo database rather than termcap,

+.I screen

+will understand the `terminfo' command, which has the same effects as the

+`termcap' command. Two separate commands are provided, as there are subtle

+Set the name of the current window to \fIwindowalias\fP. If no name is

+.B vbell

+.RB [ on | off ]

+Sets the visual bell setting for this window. Omitting the parameter

+toggles the setting. If vbell is switched on, but your terminal does not

+support a visual bell, a `vbell-message' is displayed in the status line when

+the bell character (^G) is received.

+Visual bell support of a terminal is defined by the termcap variable `vb'

+(terminfo: 'flash').

+.br

+Per default, vbell is off, thus the audible bell is used.

+See also `bell_msg'.

+.B vbell_msg

+.RI [ message ]

+the window receives a bell character (^G), vbell is set to \*Qon\*U, but the

+terminal does not support a visual bell.

+Without parameter, the current message is shown.

+Define a delay in seconds after each display of

+.B verbose

+.RB [ on | off ]

+.PP

+If verbose is switched on, the command name is echoed, whenever a window

+is created (or resurrected from zombie state). Default is off.

+Without parameter, the current setting is shown.

+.sp

+.ne 3

+Toggle the window width between 80 and 132 columns or set it to \fInum\fP

+columns if an argument is specified.

+a window which has output logging turned on is marked with `(L)';

+by the command \*Qwritelock off\*U. If the user issues the command

+.I screen

+The \fBkill\fP command may be used to remove such a window. Pressing the

+first key in the dead window has the same effect. When pressing the second

+key,

+.I screen

+will attempt to resurrect the window. The process that was

+initially running in the window will be launched again. Calling \fBzombie\fP

+.SH "WINDOW TYPES"

+Screen provides three different window types. New windows are created with

+.IR screen 's

+.B screen

+command (see also the entry in chapter \*QCUSTOMIZATION\*U). The first

+parameter to the

+.B screen

+command defines which type of window is created. The different window types are

+all special cases of the normal type. They have been added in order

+to allow

+.I screen

+to be used efficiently as a console multiplexer with 100 or more windows.

+

+.IP \(bu 3

+The normal window contains a shell (default, if no parameter is given) or any

+other system command that could be executed from a shell (e.g.

+.BR slogin ,

+etc...)

+

+.IP \(bu

+If a tty (character special device) name (e.g. \*Q/dev/ttya\*U)

+is specified as the first parameter, then the window is directly connected to

+this device.

+This window type is similar to \*Qscreen cu -l /dev/ttya\*U.

+Read and write access is required on the device node, an exclusive open is

+attempted on the node to mark the connection line as busy.

+An optional parameter is allowed consisting of a comma separated list of flags

+in the notation used by stty(1):

+.RS

+.IP <baud_rate>

+Usually 300, 1200, 9600 or 19200. This affects transmission as well as receive speed.

+.IP "cs8 or cs7"

+Specify the transmission of eight (or seven) bits per byte.

+.IP "ixon or -ixon"

+Enables (or disables) software flow-control (CTRL-S/CTRL-Q) for sending data.

+.IP "ixoff or -ixon"

+Enables (or disables) software flow-control for receiving data.

+.IP "istrip or -istrip"

+Clear (or keep) the eight bit in each received byte.

+.PP

+You may want to specify as many of these options as applicable. Unspecified

+options cause the terminal driver to make up the parameter values of the

+connection. These values are system dependant and may be in defaults or values

+saved from a previous connection.

+.PP

+For tty windows, the

+.B info

+command shows some of the modem control lines

+in the status line. These may include `RTS', `CTS', 'DTR', `DSR', `CD' and more.

+This depends on the available ioctl()'s and system header files as well as the

+on the physical capabilities of the serial board.

+Signals that are logical low (inactive) have their name preceded by

+an exclamation mark (!), otherwise the signal is logical high (active).

+Signals not supported by the hardware but available to the ioctl() interface

+are usually shown low.

+.br

+When the CLOCAL status bit is true, the whole set of modem signals is placed

+inside curly braces ({ and }).

+When the CRTSCTS or TIOCSOFTCAR bit is set, the signals `CTS' or `CD'

+are shown in parenthesis, respectively.

+

+

+For tty windows, the command

+.B break

+causes the Data transmission line (TxD) to go low for a specified period of

+time. This is expected to be interpreted as break signal on the other side.

+No data is sent and no modem control line is changed when a

+.B break

+is issued.

+.RE

+.IP \(bu

+If the first parameter is \*Q//telnet\*U, the second parameter is expected to

+be a host name, and an optional third parameter may specify a TCP port number

+(default decimal 23). Screen will connect to a server listening on the remote

+host and use the telnet protocol to communicate with that server.

+.br

+.br

+For telnet windows, the command

+.B info

+shows details about the connection in square brackets ([ and ]) at the end of

+the status line.

+.RS

+.IP b

+BINARY. The connection is in binary mode.

+.IP e

+ECHO. Local echo is disabled.

+.IP c

+SGA. The connection is in `character mode' (default: `line mode').

+.IP t

+TTYPE. The terminal type has been requested by the remote host.

+Screen sends the name \*Qscreen\*U unless instructed otherwise (see also

+the command `term').

+.IP w

+NAWS. The remote site is notified about window size changes.

+.IP f

+LFLOW. The remote host will send flow control information.

+(Ignored at the moment.)

+.PP

+Additional flags for debugging are x, t and n (XDISPLOC, TSPEED and

+NEWENV).

+.PP

+For telnet windows, the command

+.B break

+sends the telnet code IAC BREAK (decimal 243) to the remote host.

+

+

+This window type is only available if

+.I screen

+was compiled with the BUILTIN_TELNET option defined.

+.RE

+

+

+.SH "STRING ESCAPES"

+Screen provides an escape mechanism to insert information like the

+current time into messages or file names. The escape character

+is '%' with one exception: inside of a window's hardstatus '^%' ('^E')

+is used instead.

+

+Here is the full list of supported escapes:

+.IP %

+the escape character itself

+.IP a

+either 'am' or 'pm'

+.IP A

+either 'AM' or 'PM'

+.IP c

+current time HH:MM in 24h format

+.IP C

+current time HH:MM in 12h format

+.IP d

+day number

+.IP D

+weekday name

+.IP h

+hardstatus of the window

+.IP l

+current load of the system

+.IP m

+month number

+.IP M

+month name

+.IP n

+window number

+.IP s

+seconds

+.IP t

+window title

+.IP u

+all other users on this window

+.IP w

+all window numbers and names

+.IP W

+all window numbers and names except the current one

+.IP y

+last two digits of the year number

+.IP Y

+full year number

+.IP ?

+the part to the next '%?' is displayed only if an escape expands to an

+nonempty string

+.IP :

+else part of '%?'

+.P

+The 'c' and 'C' escape may be qualified with a '0' to make

+.I screen

+use zero instead of space as fill character. The 'n' escape understands

+a length qualifier (e.g. '%3n').

+VT100 emulator is hard-coded, no other terminal types can be emulated.

+offers a way to deal with these cases.

+When

+Note that

+to enable and start the graphics character set rather than \fISI\fP.

+by character translation string that is used during semi-graphics mode. This

+Data sent to the printer is not displayed in the window. The

+.I info

+command displays a line starting `PRIN' while the printer is active.

+the line will be displayed as a standard

+.I screen

+message.

+scrolling regions. Note that this may provoke confusion, when

+same as above

+.B "ESC [ \fPPn\fB E"

+Cursor next line

+.TP 27

+.B "ESC [ \fPPn\fB F"

+Cursor previous line

+.TP 27

+.B "ESC [ \fPPn\fB G"

+Cursor horizontal position

+.TP 27

+.B "ESC [ \fPPn\fB `"

+same as above

+.TP 27

+.B "ESC [ \fPPn\fB d"

+Cursor vertical position

+.TP 27

+.B "ESC [ \fPPn\fB ^"

+same as above

+.TP 27

+In order to do a full VT100 emulation

+.I screen

+has to detect

+this by making it possible to map arbitrary commands on arbitrary

+that are recognized by

+.I screen

+and are not in the termcap(5) manual.

+this capability is obsolete because

+.I screen

+uses the standard 'xn' instead.

+Switch cursor-keys to application mode.

+Switch cursor-keys back to normal mode.

+Change character foreground color in an ANSI conform way. This

+.TP 13

+.BI TF " (bool)"

+Add missing capabilities to the termcap/info entry. (Set by default).

+A \fI<charset-mapping>\fP tells

+.I screen

+how to map characters

+strings to switch to and from another charset). Each occurrence

+This tells .I

+screen

+how to translate ISOlatin1 (charset 'B')

+whenever

+.I screen

+switches to the corresponding \fI<designator>\fP. In this

+the charset switch sequence and the character mappings normally

+If

+.I screen

+has to change to the 'K' charset, '\eE(B' will be sent

+.IP LINES

+.IP .../screen-3.?.??/etc/screenrc 34

+.IP .../screen-3.?.??/etc/etcscreenrc

+Examples in the

+.I screen

+distribution package for private and global initialization files.

+.IP $SYSSCREENRC

+.IP /usr/local/etc/screenrc

+.I screen

+initialization commands

+Read in after /usr/local/etc/screenrc

+.I screen

+`interprocess communication buffer'

+Copyright (C) 1999

+Toerless Eckert (eckert@immd4.informatik.uni-erlangen.de),

+Matthew Green (mrg@mame.mu.oz.au),

+This is version 3.9 Its roots are a merge of a custom version

+numbered 2.x are copyright by Oliver Laumann.

+.SH AVAILABILITY

+The latest official release of

+.I screen

+available via anonymous ftp from prep.ai.mit.edu, nic.funet.fi or any other

+.I GNU

+distribution site. The home site of

+.I screen

+is ftp.uni-erlangen.de (131.188.3.71), in the directory

+pub/utilities/screen. The subdirectory `private' contains the latest beta

+testing release. If you want to help, send a note to

+screen@uni-erlangen.de.

+has no clue about double-high or double-wide characters.

+But this is the only area where

+It is not possible to change the environment variable $TERMCAP when

+must be installed as set-uid with owner root on most systems in order

+to be able to correctly change the owner of the tty device file for

+each window.

+When the modem line was hung up,

+unless the device driver is configured to send a HANGUP signal.

+To detach a

+If a password is set, the command line options -d and -D still detach a

+session without asking.

+.IP \(bu

+Both \*Qbreaktype\*U and \*Qdefbreaktype\*U change the break generating

+method used by all terminal devices. The first should change a window

+specific setting, where the latter should change only the default for new

+windows.

+.IP \(bu

+When attaching to a multiuser session, the user's .screenrc file is not

+sourced. Each user's personal settings have to be included in the .screenrc

+file from which the session is booted, or have to be changed manually.

+.IP \(bu

+Send bug-reports, fixes, enhancements, t-shirts, money, beer & pizza to

+ Copyright (c) 1993-1995 Free Software Foundation, Inc.

+screen.info-1: 878

+screen.info-2: 50660

+screen.info-3: 100483

+screen.info-4: 150213

+Node: Top878

+Node: Overview2886

+Node: Getting Started6518

+Node: Invoking Screen8276

+Node: Customization16304

+Node: Startup Files16791

+Node: Colon18437

+Node: Commands19059

+Node: Default Key Bindings20017

+Node: Command Summary25596

+Node: New Window37785

+Node: Chdir38617

+Node: Screen Command39588

+Node: Setenv41289

+Node: Shell41809

+Node: Term42575

+Node: Window Types43356

+Node: Selecting47674

+Node: Next and Previous48228

+Node: Other Window48754

+Node: Select49163

+Node: Session Management49831

+Node: Detach50660

+Node: Power Detach51945

+Node: Lock52584

+Node: Multiuser Session53470

+Node: Multiuser54432

+Node: Acladd54819

+Node: Aclchg55384

+Node: Acldel56790

+Node: Aclgrp57125

+Node: Displays57776

+Node: Umask58070

+Node: Wall59051

+Node: Writelock59288

+Node: Su60184

+Node: Session Name60984

+Node: Suspend61531

+Node: Quit61863

+Node: Regions62288

+Node: Split62773

+Node: Focus63063

+Node: Only63325

+Node: Remove63489

+Node: Caption63698

+Node: Window Settings64443

+Node: Naming Windows65178

+Node: Title Command66678

+Node: Dynamic Titles66952

+Node: Title Prompts68486

+Node: Title Screenrc69567

+Node: Console71206

+Node: Kill71649

+Node: Login72541

+Node: Mode73360

+Node: Monitor73759

+Node: Windows75172

+Node: Hardstatus76234

+Node: Virtual Terminal77427

+Node: Control Sequences78485

+Node: Input Translation85315

+Node: Digraph89831

+Node: Bell90623

+Node: Clear92502

+Node: Info92705

+Node: Redisplay94567

+Node: Wrap95698

+Node: Reset96449

+Node: Window Size96767

+Node: Character Processing97612

+Node: Copy and Paste100483

+Node: Copy101088

+Node: Line Termination101933

+Node: Scrollback102342

+Node: Copy Mode Keys103079

+Node: Movement103894

+Node: Marking105048

+Node: Repeat count105423

+Node: Searching105737

+Node: Specials105999

+Node: Paste107953

+Node: Registers110625

+Node: Screen-Exchange111631

+Node: History112714

+Node: Subprocess Execution113454

+Node: Exec113818

+Node: Using Exec115564

+Node: Key Binding117403

+Node: Bind118046

+Node: Bind Examples119033

+Node: Command Character119713

+Node: Help121254

+Node: Bindkey121767

+Node: Bindkey Examples123313

+Node: Bindkey Control124202

+Node: Flow Control124799

+Node: Flow Control Summary125375

+Node: Flow128309

+Node: XON/XOFF129083

+Node: Termcap129456

+Node: Window Termcap130313

+Node: Dump Termcap135556

+Node: Termcap Syntax136271

+Node: Termcap Examples138438

+Node: Special Capabilities140479

+Node: Autonuke143042

+Node: Obuflimit143692

+Node: Character Translation144521

+Node: Message Line147134

+Node: Privacy Message148045

+Node: Hardware Status Line148542

+Node: Last Message150213

+Node: Message Wait150640

+Node: Logging151066

+Node: Hardcopy151390

+Node: Log152186

+Node: Startup153802

+Node: echo154209

+Node: sleep154617

+Node: Startup Message154958

+Node: Miscellaneous155231

+Node: At156339

+Node: Break158333

+Node: Debug159980

+Node: License160457

+Node: Nethack160722

+Node: Nonblock161400

+Node: Number161854

+Node: Silence162224

+Node: Time163160

+Node: Verbose163534

+Node: Version163868

+Node: Zombie164077

+Node: Printcmd165131

+Node: Sorendition165837

+Node: String Escapes166489

+Node: Environment167814

+Node: Files168849

+Node: Credits169936

+Node: Bugs171849

+Node: Known Bugs172319

+Node: Reporting Bugs174413

+Node: Availability175179

+Node: Installation175723

+Node: Socket Directory176113

+Node: Compiling Screen176643

+Node: Concept Index178035

+Node: Command Index180092

+Node: Keystroke Index188392

+ Copyright (c) 1993-1995 Free Software Foundation, Inc.

+3.9.0.

+* Session Management:: Suspend/detach, grant access, connect sessions.

+* Regions:: Split-screen commands.

+* Window Settings:: Titles, logging, etc.

+* String Escapes:: Inserting current information into strings

+in addition, several control functions from the ISO 6429 (ECMA 48, ANSI

+X3.64) and ISO 2022 standards (e.g. insert/delete line and support for

+multiple character sets). There is a scrollback history buffer for

+each virtual terminal and a copy-and-paste mechanism that allows the

+user to move text regions between windows.

+whole screen session is detached from the user's terminal.

+ `Screen' does not understand the prefix `C-' to mean control.

+Please use the caret notation (`^A' instead of `C-a') as arguments to

+e.g. the `escape' command or the `-e' option. `Screen' will also print

+out control characters in caret notation.

+

+ be detached, this option is ignored. In combination with the

+ `-r'/`-R' option more powerful effects can be achieved:

+

+ `-d -r'

+ Reattach a session and if necessary detach it first.

+

+ `-d -R'

+ Reattach a session and if necessary detach or even create

+ it first.

+

+ `-d -RR'

+ Reattach a session and if necessary detach or create it. Use

+ the first session if more than one session is available.

+

+ `-D -r'

+ Reattach a session. If necessary detach and logout remotely

+ first.

+

+ `-D -R'

+ Attach here and now. In detail this means: If a session is

+ running, then reattach. If necessary detach and logout

+ remotely first. If it was not running create it and notify

+ the user. This is the author's favorite.

+

+ `-D -RR'

+ Attach here and now. Whatever that means, just do it.

+

+ *Note*: It is a good idea to check the status of your sessions

+ with `screen -list' before using this option.

+`-ls [MATCH]'

+`-list [MATCH]'

+ controlling terminal. If the session runs in multiuser mode, it

+ is marked `multi'. Sessions marked as `unreachable' either live

+ on a different host or are dead. An unreachable session is

+ considered dead, when its name matches either the name of the

+ local host, or the specified parameter, if any. See the `-r' flag

+ for a description how to construct matches. Sessions marked as

+ `dead' should be thoroughly checked and removed. Ask your system

+ administrator if you are not sure. Remove sessions with the

+ `-wipe' option.

+ `screen' session or not. This flag has a special meaning in

+ connection with the `-d' option:

+ `-m -d'

+ Start `screen' in *detached* mode. This creates a new session

+ but doesn't attach to it. This is useful for system startup

+ scripts.

+

+ `-m -D'

+ This also starts `screen' in *detached* mode, but doesn't fork

+ a new process. The command exits if the session terminates.

+

+`-q'

+ Suppress printing of error messages. In combination with `-ls' the

+ exit value is set as follows: 9 indicates a directory without

+ sessions. 10 indicates a directory with running but not attachable

+ sessions. 11 (or more) indicates 1 (or more) usable sessions. In

+ combination with `-r' the exit value is as follows: 10 indicates

+ that there is no session to resume. 12 (or more) indicates that

+ there are 2 (or more) sessions to resume and you should specify

+ which one to choose. In all other cases `-q' has no effect.

+ Resume a detached `screen' session. No other options (except

+ combinations with `-d' or `-D') may be specified, though the

+ session name (*note Session Name::.) may be needed to distinguish

+ between multiple detached `screen' sessions. The second form is

+ used to connect to another user's screen session which runs in

+ multiuser mode. This indicates that screen should look for

+ sessions in another user's directory. This requires setuid-root.

+ set by default if screen is run as a login-shell. For combinations

+ with the `-D'/`-d' option see there.

+`-wipe [MATCH]'

+ sessions instead of marking them as `dead'. An unreachable

+ session is considered dead, when its name matches either the name

+ of the local host, or the explicitly given parameter, if any. See

+ the `-r' flag for a description how to construct matches.

+`C-a 0...9, -'

+ (select 0...select 9, select -)

+ Switch to window number 0...9, or the blank window. *Note

+ Selecting::.

+

+`C-a Tab'

+ (focus)

+ Switch the input focus to the next region. *Note Regions::.

+ Toggle to the window displayed previously. If this window does no

+ longer exist, `other' has the same effect as `next'. *Note

+ Selecting::.

+`C-a C-b'

+ (break)

+`C-a F'

+ (fit)

+ Resize the window to the current region size. *Note Window Size::.

+

+`C-a Q'

+ (only)

+ Delete all regions but the current one. *Note Regions::.

+

+`C-a S'

+ (split)

+ Split the current region into two new ones. *Note Regions::.

+

+`C-a X'

+ (remove)

+ Kill the current region. *Note Regions::.

+

+`C-a }'

+`C-a *'

+ (displays)

+ Show the listing of attached displays.

+

+`aclgrp USRNAME [GROUPNAME]'

+ Inherit permissions granted to a group leader. *Note Multiuser

+ Session::.

+

+`aclumask [USERS]+\-BITS ...'

+ Predefine access to new windows. *Note Umask::.

+

+`addacl USERNAMES'

+ Synonym to `acladd'. *Note Multiuser Session::.

+

+`bell_msg [MESSAGE]'

+`breaktype [TCSENDBREAK | TCSBRK | TIOCSBRK]'

+ Specify how to generate breaks. *Note Break::.

+

+`caption MODE [STRING]'

+ Change caption mode and string. *Note Regions::.

+

+`chacl USERNAMES PERMBITS LIST'

+ Synonym to `aclchg'. *Note Multiuser Session::.

+

+`compacthist [STATE]'

+ Selects compaction of trailing empty lines. *Note Scrollback::.

+

+`defbreaktype [TCSENDBREAK | TCSBRK | TIOCSBRK]'

+ Specify the default for generating breaks. *Note Break::.

+

+`defshell COMMAND'

+ Set the default program for new windows. *Note Shell::.

+

+`defsilence STATE'

+ Select default idle monitoring behavior. *Note Silence::.

+

+`defslowpaste MSEC'

+ Select the default inter-character timeout when pasting. *Note

+ Paste::.

+

+ Set default writelock behavior. *Note Multiuser Session::.

+`displays'

+ List currently active user interfaces. *Note Displays::.

+

+`fit'

+ Change window size to current display size. *Note Window Size::.

+

+`focus'

+ Move focus to next region. *Note Regions::.

+

+`hstatus STATUS'

+ Change the window's hardstatus line. *Note Hardstatus::.

+

+`logtstamp [STATE]'

+ Configure logfile time-stamps. *Note Log::.

+

+ Set the inter-character timeout used for keymapping. *Note Bindkey

+`nonblock STATE'

+ Disable flow control to the current display. *Note Nonblock::.

+

+`only'

+ Kill all other regions. *Note Regions::.

+

+`remove'

+ Kill current region. *Note Regions::.

+

+`split'

+ Split region into two parts. *Note Regions::.

+

+`su [USERNAME [PASSWORD [PASSWORD2]]]'

+ Identify a user. *Note Multiuser Session::.

+

+`umask [USERS]+\-BITS ...'

+ Synonym to `aclumask'. *Note Umask::.

+

+* Window Types:: Creating different types of windows.

+ terminal type option (`-T TERM'), the all-capability-flag (`-a')

+ and scrollback option (`-h NUM') may be specified with each

+ command. The option (`-M') turns monitoring on for this window.

+ The option (`-L') turns output logging on for this window. If an

+ optional number N in the range 0...9 is given, the window number N

+ is assigned to the newly created window (or, if this number is

+ already in-use, the next available number). If a command is

+ specified after `screen', this command (with the given arguments)

+ is started in the window; otherwise, a shell is created.

+

+ Screen has built in some functionality of `cu' and `telnet'.

+ *Note Window Types::.

+ screen -fn -t foobar 2 -L telnet foobar

+title `foobar' in window #2) and will write a logfile `screenlog.2' of

+the telnet session. If you do not include any `screen' commands in

+your `.screenrc' file, then `screen' defaults to creating a single

+shell window, number zero. When the initialization is completed,

+`screen' switches to the last window specified in your .screenrc file

+or, if none, it opens default window #0.

+ - Command: defshell COMMAND

+ `defshell' is currently a synonym to the `shell' command.

+

+File: screen.info, Node: Term, Next: Window Types, Prev: Shell, Up: New Window

+File: screen.info, Node: Window Types, Prev: Term, Up: New Window

+

+Window Types

+============

+

+ Screen provides three different window types. New windows are created

+with `screen''s `screen' command (*note Screen Command::.). The first

+parameter to the `screen' command defines which type of window is

+created. The different window types are all special cases of the normal

+type. They have been added in order to allow `screen' to be used

+efficiently as a console with 100 or more windows.

+ * The normal window contains a shell (default, if no parameter is

+ given) or any other system command that could be executed from a

+ shell. (e.g. `slogin', etc...).

+

+ * If a tty (character special device) name (e.g. `/dev/ttya') is

+ specified as the first parameter, then the window is directly

+ connected to this device. This window type is similar to `screen

+ cu -l /dev/ttya'. Read and write access is required on the device

+ node, an exclusive open is attempted on the node to mark the

+ connection line as busy. An optional parameter is allowed

+ consisting of a comma separated list of flags in the notation used

+ by `stty(1)':

+ `<baud_rate>'

+ Usually 300, 1200, 9600 or 19200. This affects transmission

+ as well as receive speed.

+

+ `cs8 or cs7'

+ Specify the transmission of eight (or seven) bits per byte.

+

+ `ixon or -ixon'

+ Enables (or disables) software flow-control (CTRL-S/CTRL-Q)

+ for sending data.

+

+ `ixoff or -ixoff'

+ Enables (or disables) software flow-control for receiving

+ data.

+

+ `istrip or -istrip'

+ Clear (or keep) the eight bit in each received byte.

+

+ You may want to specify as many of these options as applicable.

+ Unspecified options cause the terminal driver to make up the

+ parameter values of the connection. These values are system

+ dependant and may be in defaults or values saved from a previous

+ connection.

+

+ For tty windows, the `info' command shows some of the modem

+ control lines in the status line. These may include `RTS', `CTS',

+ `DTR', `CD' and more. This depends rather on on the available

+ `ioctl()''s and system header files than on the physical

+ capabilities of the serial board. The name of a logical low

+ (inactive) signal is preceded by an exclamation mark (`!'),

+ otherwise the signal is logical high (active). Unsupported but

+ shown signals are usually shown low. When the `CLOCAL' status bit

+ is true, the whole set of modem signals is placed inside curly

+ braces (`{' and `}'). When the `CRTSCTS' or `TIOCSOFTCAR' bit is

+ true, the signals `CTS' or `CD' are shown in parenthesis,

+ respectively.

+

+ For tty windows, the command `break' causes the Data transmission

+ line (TxD) to go low for a specified period of time. This is

+ expected to be interpreted as break signal on the other side. No

+ data is sent and no modem control line is changed when a `break'

+ is issued.

+

+ * If the first parameter is `//telnet', the second parameter is

+ expected to be a host name, and an optional third parameter may

+ specify a TCP port number (default decimal 23). Screen will

+ connect to a server listening on the remote host and use the

+ telnet protocol to communicate with that server.

+

+ For telnet windows, the command `info' shows details about the

+ connection in square brackets (`[' and `]') at the end of the

+ status line.

+ `b'

+ BINARY. The connection is in binary mode.

+

+ `e'

+ ECHO. Local echo is disabled.

+

+ `c'

+ SGA. The connection is in `character mode' (default: `line

+ mode').

+

+ `t'

+ TTYPE. The terminal type has been requested by the remote

+ host. Screen sends the name `screen' unless instructed

+ otherwise (see also the command `term').

+

+ `w'

+ NAWS. The remote site is notified about window size changes.

+

+ `f'

+ LFLOW. The remote host will send flow control information.

+ (Ignored at the moment.) Additional flags for debugging are

+ `x', `t' and `n' (XDISPLOC, TSPEED and NEWENV).

+

+ For telnet windows, the command `break' sends the telnet code `IAC

+ BREAK' (decimal 243) to the remote host.

+

+

+* Select:: Switch to a window (and to one after `kill').

+ (unless screen is compiled with a higher MAXWIN setting). The

+ special command `select -' switches to a blank window.

+File: screen.info, Node: Session Management, Next: Regions, Prev: Selecting, Up: Top

+ Copyright (c) 1993-1995 Free Software Foundation, Inc.

+File: screen.info, Node: Detach, Next: Power Detach, Up: Session Management

+

+Detach

+======

+

+ - Command: autodetach STATE

+ (none)

+ Sets whether `screen' will automatically detach upon hangup, which

+ saves all your running programs until they are resumed with a

+ `screen -r' command. When turned off, a hangup signal will

+ terminate `screen' and all the processes it contains. Autodetach is

+ on by default.

+

+ - Command: detach

+ (`C-a d', `C-a C-d')

+ Detach the `screen' session (disconnect it from the terminal and

+ put it into the background). A detached `screen' can be resumed by

+ invoking `screen' with the `-r' option. (*note Invoking Screen::.)

+

+ - Command: password [CRYPTED_PW]

+ (none)

+ Present a crypted password in your `.screenrc' file and screen will

+ ask for it, whenever someone attempts to resume a detached

+ session. This is useful, if you have privileged programs running

+ under `screen' and you want to protect your session from reattach

+ attempts by users that managed to assume your uid. (I.e. any

+ superuser.) If no crypted password is specified, screen prompts

+ twice a password and places its encryption in the paste buffer.

+ Default is `none', which disables password checking.

+

+

+File: screen.info, Node: Power Detach, Next: Lock, Prev: Detach, Up: Session Management

+

+Power Detach

+============

+

+ - Command: pow_detach

+ (`C-a D')

+ Mainly the same as `detach', but also sends a HANGUP signal to the

+ parent process of `screen'.

+ *Caution*: This will result in a logout if `screen' was started

+ from your login shell.

+

+ - Command: pow_detach_msg [MESSAGE]

+ (none)

+ The MESSAGE specified here is output whenever a power detach is

+ performed. It may be used as a replacement for a logout message or

+ to reset baud rate, etc. Without parameter, the current message

+ is shown.

+

+

+File: screen.info, Node: Lock, Next: Multiuser Session, Prev: Power Detach, Up: Session Management

+

+Lock

+====

+

+ - Command: lockscreen

+ (`C-a x', `C-a C-x')

+ Call a screenlock program (`/local/bin/lck' or `/usr/bin/lock' or

+ a builtin, if no other is available). Screen does not accept any

+ command keys until this program terminates. Meanwhile processes in

+ the windows may continue, as the windows are in the detached state.

+ The screenlock program may be changed through the environment

+ variable `$LOCKPRG' (which must be set in the shell from which

+ `screen' is started) and is executed with the user's uid and gid.

+

+ Warning: When you leave other shells unlocked and have no password

+ set on `screen', the lock is void: One could easily re-attach from

+ an unlocked shell. This feature should rather be called

+ `lockterminal'.

+

+

+File: screen.info, Node: Multiuser Session, Next: Session Name, Prev: Lock, Up: Session Management

+

+Multiuser Session

+=================

+

+ These commands allow other users to gain access to one single

+`screen' session. When attaching to a multiuser `screen' the

+sessionname is specified as `username/sessionname' to the `-S' command

+line option. `Screen' must be compiled with multiuser support to

+enable features described here.

+

+* Menu:

+

+* Multiuser:: Enable / Disable multiuser mode.

+* Acladd:: Enable a specific user.

+* Aclchg:: Change a users permissions.

+* Acldel:: Disable a specific user.

+* Aclgrp:: Grant a user permissions to other users.

+* Displays:: List all active users at their displays.

+* Umask:: Predefine access to new windows.

+* Wall:: Write a message to all users.

+* Writelock:: Grant exclusive window access.

+* Su:: Substitute user.

+

+

+File: screen.info, Node: Multiuser, Next: Acladd, Up: Multiuser Session

+

+Multiuser

+---------

+

+ - Command: multiuser STATE

+ (none)

+ Switch between single-user and multi-user mode. Standard screen

+ operation is single-user. In multi-user mode the commands

+ `acladd', `aclchg' and `acldel' can be used to enable (and

+ disable) other users accessing this `screen'.

+

+

+File: screen.info, Node: Acladd, Next: Aclchg, Prev: Multiuser, Up: Multiuser Session

+

+Acladd

+------

+

+ - Command: acladd USERNAMES

+ - Command: addacl USERNAMES

+ (none)

+ Enable users to fully access this screen session. USERNAMES can be

+ one user or a comma separated list of users. This command enables

+ to attach to the `screen' session and performs the equivalent of

+ `aclchg USERNAMES +rwx "#?"'. To add a user with restricted access,

+ use the `aclchg' command below. `Addacl' is a synonym to `acladd'.

+ Multi-user mode only.

+

+

+File: screen.info, Node: Aclchg, Next: Acldel, Prev: Acladd, Up: Multiuser Session

+

+Aclchg

+------

+

+ - Command: aclchg USERNAMES PERMBITS LIST

+ - Command: chacl USERNAMES PERMBITS LIST

+ (none)

+ Change permissions for a comma separated list of users.

+ Permission bits are represented as `r', `w' and `x'. Prefixing

+ `+' grants the permission, `-' removes it. The third parameter is

+ a comma separated list of commands or windows (specified either by

+ number or title). The special list `#' refers to all windows, `?'

+ to all commands. If USERNAMES consists of a single `*', all known

+ users is affected. A command can be executed when the user has

+ the `x' bit for it. The user can type input to a window when he

+ has its `w' bit set and no other user obtains a writelock for this

+ window. Other bits are currently ignored. To withdraw the

+ writelock from another user in e.g. window 2: `aclchg USERNAME

+ -w+w 2'. To allow read-only access to the session: `aclchg

+ USERNAME -w "#"'. As soon as a user's name is known to screen, he

+ can attach to the session and (per default) has full permissions

+ for all command and windows. Execution permission for the acl

+ commands, `at' and others should also be removed or the user may

+ be able to regain write permission. `Chacl' is a synonym to

+ `aclchg'. Multi-user mode only.

+

+

+File: screen.info, Node: Acldel, Next: Aclgrp, Prev: Aclchg, Up: Multiuser Session

+

+Acldel

+------

+

+ - Command: acldel USERNAME

+ (none)

+ Remove a user from screen's access control list. If currently

+ attached, all the user's displays are detached from the session.

+ He cannot attach again. Multi-user mode only.

+

+

+File: screen.info, Node: Aclgrp, Next: Displays, Prev: Acldel, Up: Multiuser Session

+

+Aclgrp

+------

+

+ - Command: aclgrp USERNAME [GROUPNAME]

+ (none)

+ Creates groups of users that share common access rights. The name

+ of the group is the username of the group leader. Each member of

+ the group inherits the permissions that are granted to the

+ group leader. That means, if a user fails an access check, another

+ check is made for the group leader. A user is removed from all

+ groups the special value `none' is used for GROUPNAME. If the

+ second parameter is omitted all groups the user is in are listed.

+

+

+File: screen.info, Node: Displays, Next: Umask, Prev: Aclgrp, Up: Multiuser Session

+

+Displays

+--------

+

+ - Command: displays

+ (`C-a *')

+ Shows a tabular listing of all currently connected user

+ front-ends (displays). This is most useful for multiuser

+ sessions.

+

+

+File: screen.info, Node: Umask, Next: Wall, Prev: Displays, Up: Multiuser Session

+

+aclumask

+--------

+

+ - Command: aclumask [[USERS]+BITS |[USERS]-BITS .... ]

+ - Command: umask [[USERS]+BITS |[USERS]-BITS .... ]

+ (none)

+ This specifies the access other users have to windows that will

+ be created by the caller of the command. USERS may be no, one

+ or a comma separated list of known usernames. If no users are

+ specified, a list of all currently known users is assumed. BITS

+ is any combination of access control bits allowed defined

+ with the `aclchg' command. The special username `?' predefines the

+ access that not yet known users will be granted to any

+ window initially. The special username `??' predefines the access

+ that not yet known users are granted to any command. Rights of

+ the special username nobody cannot be changed (see the `su'

+ command). `Umask' is a synonym to `aclumask'.

+

+

+File: screen.info, Node: Wall, Next: Writelock, Prev: Umask, Up: Multiuser Session

+

+Wall

+----

+

+ - Command: wall MESSAGE

+ (none)

+ Write a message to all displays. The message will appear in the

+ terminal's status line.

+

+

+File: screen.info, Node: Writelock, Next: Su, Prev: Wall, Up: Multiuser Session

+

+Writelock

+---------

+

+ - Command: writelock ON|OFF|AUTO

+ (none)

+ In addition to access control lists, not all users may be able to

+ write to the same window at once. Per default, writelock is in

+ `auto' mode and grants exclusive input permission to the user who

+ is the first to switch to the particular window. When he leaves

+ the window, other users may obtain the writelock (automatically).

+ The writelock of the current window is disabled by the command

+ `writelock off'. If the user issues the command `writelock on' he

+ keeps the exclusive write permission while switching to other

+ windows.

+

+ - Command: defwritelock ON|OFF|AUTO

+ (none)

+ Sets the default writelock behavior for new windows. Initially all

+ windows will be created with no writelocks.

+

+

+File: screen.info, Node: Su, Prev: Writelock, Up: Multiuser Session

+

+Su

+--

+

+ - Command: su [USERNAME [PASSWORD [PASSWORD2]]]

+ (none)

+ Substitute the user of a display. The command prompts for all

+ parameters that are omitted. If passwords are specified as

+ parameters, they have to be specified un-crypted. The first

+ password is matched against the systems passwd database, the

+ second password is matched against the `screen' password as

+ set with the commands `acladd' or `password'. `Su' may be useful

+ for the `screen' administrator to test multiuser setups. When

+ the identification fails, the user has access to the commands

+ available for user `nobody'. These are `detach', `license',

+ `version', `help' and `displays'.

+

+

+File: screen.info, Node: Session Name, Next: Suspend, Prev: Multiuser Session, Up: Session Management

+

+Session Name

+============

+

+ - Command: sessionname [NAME]

+ (none)

+ Rename the current session. Note that for `screen -list' the name

+ shows up with the process-id prepended. If the argument NAME is

+ omitted, the name of this session is displayed.

+ *Caution*: The `$STY' environment variable still reflects the old

+ name. This may result in confusion. The default is constructed

+ from the tty and host names.

+

+

+File: screen.info, Node: Suspend, Next: Quit, Prev: Session Name, Up: Session Management

+

+Suspend

+=======

+

+ - Command: suspend

+ (`C-a z', `C-a C-z')

+ Suspend `screen'. The windows are in the detached state while

+ `screen' is suspended. This feature relies on the parent shell

+ being able to do job control.

+

+

+File: screen.info, Node: Quit, Prev: Suspend, Up: Session Management

+

+Quit

+====

+

+ - Command: quit

+ (`C-a C-\')

+ Kill all windows and terminate `screen'. Note that on VT100-style

+ terminals the keys `C-4' and `C-\' are identical. So be careful

+ not to type `C-a C-4' when selecting window no. 4. Use the empty

+ bind command (as in `bind "^\"') to remove a key binding (*note

+ Key Binding::.).

+

+

+File: screen.info, Node: Regions, Next: Window Settings, Prev: Session Management, Up: Top

+

+Regions

+*******

+

+ Screen has the ability to display more than one window on the user's

+display. This is done by splitting the screen in regions, which can

+contain different windows.

+

+* Menu:

+

+* Split:: Split a region into two

+* Focus:: Change to the next region

+* Only:: Delete all other regions

+* Remove:: Delete the current region

+* Caption:: Control the window's caption

+

+

+File: screen.info, Node: Split, Next: Focus, Up: Regions

+

+Split

+=====

+

+ - Command: split

+ (`C-a S')

+ Split the current region into two new ones. All regions on the

+ display are resized to make room for the new region. The blank

+ window is displayed on the new region.

+

+

+File: screen.info, Node: Focus, Next: Only, Prev: Split, Up: Regions

+

+Focus

+=====

+

+ - Command: focus

+ (`C-a Tab')

+ Move the input focus to the next region. This is done in a cyclic

+ way so that the top region is selected after the bottom one.

+

+

+File: screen.info, Node: Only, Next: Remove, Prev: Focus, Up: Regions

+

+Only

+====

+

+ - Command: only

+ (`C-a Q')

+ Kill all regions but the current one.

+

+

+File: screen.info, Node: Remove, Next: Caption, Prev: Only, Up: Regions

+

+Remove

+======

+

+ - Command: remove

+ (`C-a X')

+ Kill the current region. This is a no-op if there is only one

+ region.

+

+

+File: screen.info, Node: Caption, Prev: Remove, Up: Regions

+

+Caption

+=======

+

+ - Command: caption `always'|`splitonly' [STRING]

+ - Command: caption `string' [STRING]

+ (none)

+ This command controls the display of the window captions. Normally

+ a caption is only used if more than one window is shown on the

+ display (split screen mode). But if the type is set to `always',

+ `screen' shows a caption even if only one window is displayed. The

+ default is `splitonly'.

+

+ The second form changes the text used for the caption. You can use

+ all string escapes (*Note String Escapes::). `Screen' uses a

+ default of `%3n %t'.

+

+ You can mix both forms by providing the string as an additional

+ argument.

+

+

+File: screen.info, Node: Window Settings, Next: Virtual Terminal, Prev: Regions, Up: Top

+

+Window Settings

+***************

+

+ These commands control the way `screen' treats individual windows in

+a session. *Note Virtual Terminal::, for commands to control the

+terminal emulation itself.

+

+* Menu:

+

+* Naming Windows:: Control the name of the window

+* Console:: See the host's console messages

+* Kill:: Destroy an unwanted window

+* Login:: Control `/etc/utmp' logging

+* Mode:: Control the file mode of the pty

+* Monitor:: Watch for activity in a window

+* Windows:: List the active windows

+* Hardstatus:: Set a window's hardstatus line

+

+

+ Grabs or un-grabs the machines console output to a window. When

+ the argument is omitted the current state is displayed. *Note*:

+ Only the owner of `/dev/console' can grab the console output. This

+ screen (your display) switches to another window. When the last

+ window is destroyed, `screen' exits. After a kill screen switches

+ to the previously displayed window.

+ specified for creation. *note Screen Command::.).

+ each occurrence of `^G' is replaced by the definition for bell in

+ 'Activity in window %n'

+ the window (or its title).

+

+ The current window is marked with a `*'; the previous window is

+ marked with a `-'; all the windows that are logged in are marked

+ with a `$' (*note Login::.); a background window that has received

+ a bell is marked with a `!'; a background window that is being

+ monitored and has had activity occur is marked with an `@' (*note

+ Monitor::.); a window which has output logging turned on is marked

+ with `(L)'; windows occupied by other users are marked with `&' or

+ `&&' if the window is shared by other users; windows in the zombie

+ state are marked with `Z'.

+

+ If this list is too long to fit on the terminal's status line only

+ the portion around the current window is displayed.

+window's hardstatus line. The hardstatus line can be changed with the

+ANSI Application Program Command (APC): `ESC_<string>ESC\'. As a

+convenience for xterm users the sequence `ESC]0..2;<string>^G' is also

+accepted.

+ - Command: defhstatus [STATUS]

+ This was done to make a misinterpretation of program generated

+ - Command: hstatus STATUS

+ (none)

+ Changes the current window's hardstatus line to STATUS.

+

+some extra functions added. The VT100 emulator is hard-coded, no other

+ ESC [ Pn ; Pn f same as above

+ ESC [ Pn E Cursor next line

+ ESC [ Pn F Cursor previous line

+ ESC [ Pn G Cursor horizontal position

+ ESC [ Pn ` same as above

+ ESC [ Pn d Cursor vertical position

+ ESC [ Pn ^ same as above

+ following characters (up to three) as an octal number instead.

+ The optional argument PRESET is treated as user input, thus one

+ can create an "umlaut" key. For example the command `bindkey ^K

+ message can be re-defined by this command. Each occurrence of `%'

+ in MESSAGE is replaced by the number of the window to which a bell

+ has been sent, and each occurrence of `^G' is replaced by the

+ definition for bell in your termcap (usually an audible bell).

+ The default message is

+ 'Bell in window %n'

+ suppress output of a message line (`bell_msg ""'). Without

+ parameter, the current message is shown.

+ scrollback buffer in lines, like in `(80,24)+50', the current

+ state of window XON/XOFF flow control is shown like this (see also

+ *Note Flow Control::):

+ +flow automatic flow control, currently on.

+ -flow automatic flow control, currently off.

+ +(+)flow flow control enabled. Agrees with automatic control.

+ -(+)flow flow control disabled. Disagrees with automatic control.

+ +(-)flow flow control enabled. Disagrees with automatic control.

+ -(-)flow flow control disabled. Agrees with automatic control.

+

+ The current line wrap setting (`+wrap' indicates enabled, `-wrap'

+ not) is also shown. The flags `ins', `org', `app', `log', `mon'

+ and `nored' are displayed when the window is in insert mode,

+ origin mode, application-keypad mode, has output logging, insert

+ mode, origin mode, application-keypad mode, output logging,

+ activity monitoring or partial redraw enabled.

+

+ The currently active character set (`G0', `G1', `G2', or `G3'),

+ and in square brackets the terminal character sets that are

+ currently designated as `G0' through `G3'. Additional modes

+ depending on the type of the window are displayed at the end of

+ the status line (*note Window Types::.).

+

+ If the state machine of the terminal emulator is in a non-default

+ state, the info line is started with a string identifying the

+ current state.

+

+ For system information use `time'.

+ `partial' settings. It does not change the default redraw behavior

+ of newly created windows.

+ - Command: fit

+ (`C-a F')

+ Change the window size to the size of the current region. This

+ command is needed because screen doesn't adapt the window size

+ automatically if the window is displayed more than once.

+

+ Turn GR charset switching on/off. Whenever screen sees an input

+ Copyright (c) 1993-1995 Free Software Foundation, Inc.

+File: screen.info, Node: Copy and Paste, Next: Subprocess Execution, Prev: Virtual Terminal, Up: Top

+

+Copy and Paste

+**************

+

+ For those confined to a hardware terminal, these commands provide a

+cut and paste facility more powerful than those provided by most

+windowing systems.

+

+* Menu:

+

+* Copy:: Copy from scrollback to buffer

+* Paste:: Paste from buffer into window

+* Registers:: Longer-term storage

+* Screen-Exchange:: Sharing data between screen users

+* History:: Recalling previous input

+

+

+File: screen.info, Node: Copy, Next: Paste, Up: Copy and Paste

+

+Copying

+=======

+

+ - Command: copy

+ (`C-a [', `C-a C-[', `C-a ESC')

+ Enter copy/scrollback mode. This allows you to copy text from the

+ current window and its history into the paste buffer. In this mode

+ a `vi'-like full screen editor is active, with controls as

+ outlined below.

+

+* Menu:

+

+* Line Termination:: End copied lines with CR/LF

+* Scrollback:: Set the size of the scrollback buffer

+* Copy Mode Keys:: Remap keys in copy mode

+* Movement:: Move around in the scrollback buffer

+* Marking:: Select the text you want

+* Repeat count:: Repeat a command

+* Searching:: Find the text you want

+* Specials:: Other random keys

+

+

+File: screen.info, Node: Line Termination, Next: Scrollback, Up: Copy

+

+CR/LF

+-----

+

+ - Command: crlf [STATE]

+ (none)

+ This affects the copying of text regions with the `C-a [' command.

+ If it is set to `on', lines will be separated by the two character

+ sequence `CR'/`LF'. Otherwise only `LF' is used. `crlf' is off

+ by default. When no parameter is given, the state is toggled.

+

+

+File: screen.info, Node: Scrollback, Next: Copy Mode Keys, Prev: Line Termination, Up: Copy

+

+Scrollback

+----------

+

+ - Command: defscrollback NUM

+ (none)

+ Same as the `scrollback' command except that the default setting

+ for new windows is changed. Defaults to 100.

+

+ - Command: scrollback NUM

+ (none)

+ Set the size of the scrollback buffer for the current window to

+ NUM lines. The default scrollback is 100 lines. Use `C-a i' to

+ view the current setting.

+

+ - Command: compacthist [STATE]

+ (none)

+ This tells screen weather to suppress trailing blank lines when

+ scrolling up text into the history buffer. Turn compacting `on' to

+ hold more useful lines in your scrollback buffer.

+

+

+File: screen.info, Node: Copy Mode Keys, Next: Movement, Prev: Scrollback, Up: Copy

+

+markkeys

+--------

+

+ - Command: markkeys STRING

+ (none)

+ This is a method of changing the keymap used for copy/history

+ mode. The string is made up of OLDCHAR=NEWCHAR pairs which are

+ separated by `:'. Example: The command `markkeys h=^B:l=^F:$=^E'

+ would set some keys to be more familiar to `emacs' users. If your

+ terminal sends characters, that cause you to abort copy mode, then

+ this command may help by binding these characters to do nothing.

+ The no-op character is `' and is used like this: `markkeys @=L=H'

+ if you do not want to use the `H' or `L' commands any longer. As

+ shown in this example, multiple keys can be assigned to one

+ function in a single statement.

+

+

+File: screen.info, Node: Movement, Next: Marking, Prev: Copy Mode Keys, Up: Copy

+

+Movement Keys

+-------------

+

+`h', `j', `k', `l' move the cursor line by line or column by column.

+

+`0', `^' and `$' move to the leftmost column or to the first or last

+non-whitespace character on the line.

+

+`H', `M' and `L' move the cursor to the leftmost column of the top,

+center or bottom line of the window.

+

+`+' and `-' move the cursor to the leftmost column of the next or

+previous line.

+

+`G' moves to the specified absolute line (default: end of buffer).

+

+`|' moves to the specified absolute column.

+

+`w', `b', `e' move the cursor word by word.

+

+`C-u' and `C-d' scroll the display up/down by the specified amount of

+lines while preserving the cursor position. (Default: half screenfull).

+

+`C-b' and `C-f' move the cursor up/down a full screen.

+

+`g' moves to the beginning of the buffer.

+

+`%' jumps to the specified percentage of the buffer.

+

+ Note that Emacs-style movement keys can be specified by a .screenrc

+command. (`markkeys "h=^B:l=^F:$=^E"') There is no simple method for a

+full emacs-style keymap, however, as this involves multi-character

+codes.

+

+

+File: screen.info, Node: Marking, Next: Repeat count, Prev: Movement, Up: Copy

+

+Marking

+-------

+

+ The copy range is specified by setting two marks. The text between

+these marks will be highlighted. Press `space' to set the first or

+second mark respectively.

+

+`Y' and `y' can be used to mark one whole line or to mark from start of

+line.

+

+`W' marks exactly one word.

+

+

+File: screen.info, Node: Repeat count, Next: Searching, Prev: Marking, Up: Copy

+

+Repeat Count

+------------

+

+ Any command in copy mode can be prefixed with a number (by pressing

+digits `0...9') which is taken as a repeat count. Example: `C-a C-[ H

+10 j 5 Y' will copy lines 11 to 15 into the paste buffer.

+

+

+File: screen.info, Node: Searching, Next: Specials, Prev: Repeat count, Up: Copy

+

+Searching

+---------

+

+`/' `vi'-like search forward.

+

+`?' `vi'-like search backward.

+

+`C-a s' `emacs' style incremental search forward.

+

+`C-r' `emacs' style reverse i-search.

+

+

+File: screen.info, Node: Specials, Prev: Searching, Up: Copy

+

+Specials

+--------

+

+ There are, however, some keys that act differently here from in

+`vi'. `Vi' does not allow to yank rectangular blocks of text, but

+`screen' does. Press

+

+`c' or `C' to set the left or right margin respectively. If no repeat

+count is given, both default to the current cursor position.

+Example: Try this on a rather full text screen: `C-a [ M 20 l SPACE c

+10 l 5 j C SPACE'.

+

+This moves one to the middle line of the screen, moves in 20 columns

+left, marks the beginning of the paste buffer, sets the left column,

+moves 5 columns down, sets the right column, and then marks the end of

+the paste buffer. Now try:

+`C-a [ M 20 l SPACE 10 l 5 j SPACE'

+

+and notice the difference in the amount of text copied.

+

+`J' joins lines. It toggles between 4 modes: lines separated by a

+newline character (012), lines glued seamless, lines separated by a

+single space or comma separated lines. Note that you can prepend the

+newline character with a carriage return character, by issuing a `set

+crlf on'.

+

+`v' is for all the `vi' users who use `:set numbers' - it toggles the

+left margin between column 9 and 1.

+

+`a' before the final space key turns on append mode. Thus the contents

+of the paste buffer will not be overwritten, but appended to.

+

+`A' turns on append mode and sets a (second) mark.

+

+`>' sets the (second) mark and writes the contents of the paste buffer

+to the screen-exchange file (`/tmp/screen-exchange' per default) once

+copy-mode is finished. *Note Screen-Exchange::.

+This example demonstrates how to dump the whole scrollback buffer to

+that file:

+`C-a [ g SPACE G $ >'.

+

+`C-g' gives information about the current line and column.

+

+`x' exchanges the first mark and the current cursor position. You can

+use this to adjust an already placed mark.

+

+`@' does nothing. Absolutely nothing. Does not even exit copy mode.

+

+All keys not described here exit copy mode.

+

+

+File: screen.info, Node: Paste, Next: Registers, Prev: Copy, Up: Copy and Paste

+

+Paste

+=====

+

+ - Command: paste [REGISTERS [DESTINATION]]

+ (`C-a ]', `C-a C-]')

+ Write the (concatenated) contents of the specified registers to

+ the stdin stream of the current window. The register `.' is

+ treated as the paste buffer. If no parameter is specified the user

+ is prompted to enter a single register. The paste buffer can be

+ filled with the `copy', `history' and `readbuf' commands. Other

+ registers can be filled with the `register', `readreg' and `paste'

+ commands. If `paste' is called with a second argument, the

+ contents of the specified registers is pasted into the named

+ destination register rather than the window. If `.' is used as the

+ second argument, the display's paste buffer is the destination.

+ Note, that `paste' uses a wide variety of resources: Usually both,

+ a current window and a current display are required. But whenever

+ a second argument is specified no current window is needed. When

+ the source specification only contains registers (not the paste

+ buffer) then there need not be a current display (terminal

+ attached), as the registers are a global resource. The paste

+ buffer exists once for every user.

+

+ - Command: pastefont [STATE]

+ Tell screen to include font information in the paste buffer. The

+ default is not to do so. This command is especially usefull for

+ multi character fonts like kanji.

+

+ - Command: slowpaste MSEC

+ - Command: defslowpaste MSEC

+ (none)

+ Define the speed text is inserted in the current window by the

+ `paste' command. If the slowpaste value is nonzero text is written

+ character by character. `screen' will pause for MSEC milliseconds

+ after each write to allow the application to process the input.

+ only use `slowpaste' if your underlying system exposes flow

+ control problems while pasting large amounts of text.

+ `defslowpaste' specifies the default for new windows.

+

+ - Command: readreg [REGISTER [FILENAME]]

+ (none)

+ Does one of two things, dependent on number of arguments: with

+ zero or one arguments it it duplicates the paste buffer contents

+ into the register specified or entered at the prompt. With two

+ arguments it reads the contents of the named file into the

+ register, just as `readbuf' reads the screen-exchange file into

+ the paste buffer. The following example will paste the system's

+ password file into the screen window (using register p, where a

+ copy remains):

+

+ C-a : readreg p /etc/passwd

+ C-a : paste p

+

+

+File: screen.info, Node: Registers, Next: Screen-Exchange, Prev: Paste, Up: Copy and Paste

+

+Registers

+=========

+

+ - Command: copy_reg [KEY]

+ (none)

+ Removed. Use `readreg' instead.

+

+ - Command: ins_reg [KEY]

+ (none)

+ Removed. Use `paste' instead.

+

+ - Command: process [KEY]

+ (none)

+ Stuff the contents of the specified register into the `screen'

+ input queue. If no argument is given you are prompted for a

+ register name. The text is parsed as if it had been typed in from

+ the user's keyboard. This command can be used to bind multiple

+ actions to a single key.

+

+ - Command: register KEY STRING

+ (none)

+ Save the specified STRING to the register KEY.

+

+ - Command: stuff STRING

+ (none)

+ Stuff the string STRING in the input buffer of the current window.

+ This is like the `paste' command, but with much less overhead.

+ You cannot paste large buffers with the `stuff' command. It is most

+ useful for key bindings. *Note Bindkey::

+

+

+

+File: screen.info, Node: Screen-Exchange, Next: History, Prev: Registers, Up: Copy and Paste

+

+Screen-Exchange

+===============

+

+ - Command: bufferfile [EXCHANGE-FILE]

+ (none)

+ Change the filename used for reading and writing with the paste

+ buffer. If the EXCHANGE-FILE parameter is omitted, `screen'

+ reverts to the default of `/tmp/screen-exchange'. The following

+ example will paste the system's password file into the screen

+ window (using the paste buffer, where a copy remains):

+

+ C-a : bufferfile /etc/passwd

+ C-a < C-a ]

+ C-a : bufferfile

+

+ - Command: readbuf

+ (`C-a <')

+ Reads the contents of the current screen-exchange file into the

+ paste buffer.

+

+ - Command: removebuf

+ (`C-a =')

+ Unlinks the screen-exchange file.

+

+ - Command: writebuf

+ (`C-a >')

+ Writes the contents of the paste buffer to a public accessible

+ screen-exchange file. This is thought of as a primitive means of

+ communication between `screen' users on the same host. See also

+ `C-a ESC' (*note Copy::.).

+

+

+File: screen.info, Node: History, Prev: Screen-Exchange, Up: Copy and Paste

+

+History

+=======

+

+ - Command: history

+ (`C-a {')

+ Usually users work with a shell that allows easy access to previous

+ commands. For example, `csh' has the command `!!' to repeat the

+ last command executed. `screen' provides a primitive way of

+ recalling "the command that started ...": You just type the first

+ letter of that command, then hit `C-a {' and `screen' tries to

+ find a previous line that matches with the prompt character to the

+ left of the cursor. This line is pasted into this window's input

+ queue. Thus you have a crude command history (made up by the

+ visible window and its scrollback buffer).

+

+

+File: screen.info, Node: Subprocess Execution, Next: Key Binding, Prev: Copy and Paste, Up: Top

+

+Subprocess Execution

+********************

+

+ Control Input or Output of a window by another filter process. Use

+with care!

+

+* Menu:

+

+* Exec:: The `exec' command syntax.

+* Using Exec:: Weird things that filters can do.

+

+

+File: screen.info, Node: Exec, Next: Using Exec, Up: Subprocess Execution

+

+Exec

+====

+

+ - Command: exec [[FDPAT] NEWCOMMAND [ARGS ... ]]

+ (none)

+ Run a unix subprocess (specified by an executable path NEWCOMMAND

+ and its optional arguments) in the current window. The flow of

+ data between newcommands stdin/stdout/stderr, the process

+ originally started (let us call it "application-process") and

+ screen itself (window) is controlled by the filedescriptor pattern

+ FDPAT. This pattern is basically a three character sequence

+ representing stdin, stdout and stderr of newcommand. A dot (`.')

+ connects the file descriptor to screen. An exclamation mark (`!')

+ causes the file descriptor to be connected to the

+ application-process. A colon (`:') combines both.

+ User input will go to newcommand unless newcommand receives the

+ application-process' output (FDPATs first character is `!' or `:')

+ or a pipe symbol (`|') is added to the end of FDPAT.

+ Invoking `exec' without arguments shows name and arguments of the

+ currently running subprocess in this window. Only one subprocess

+ can be running per window.

+ When a subprocess is running the `kill' command will affect it

+ instead of the windows process. Only one subprocess a time can be

+ running in each window.

+ Refer to the postscript file `doc/fdpat.ps' for a confusing

+ illustration of all 21 possible combinations. Each drawing shows

+ the digits 2, 1, 0 representing the three file descriptors of

+ newcommand. The box marked `W' is usual pty that has the

+ application-process on its slave side. The box marked `P' is the

+ secondary pty that now has screen at its master side.

+

+

+File: screen.info, Node: Using Exec, Prev: Exec, Up: Subprocess Execution

+

+Using Exec

+==========

+

+Abbreviations:

+

+ * Whitespace between the word `exec' and FDPAT and the command name

+ can be omitted.

+

+ * Trailing dots and a FDPAT consisting only of dots can be omitted.

+

+ * A simple `|' is synonymous for the `!..|' pattern.

+

+ * The word `exec' can be omitted when the `|' abbreviation is used.

+

+ * The word `exec' can always be replaced by leading `!'.

+

+Examples:

+

+`!/bin/sh'

+`exec /bin/sh'

+`exec ... /bin/sh'

+ All of the above are equivalent. Creates another shell in the

+ same window, while the original shell is still running. Output of

+ both shells is displayed and user input is sent to the new

+ `/bin/sh'.

+

+`!!stty 19200'

+`exec!stty 19200'

+`exec !.. stty 19200'

+ All of the above are equivalent. Set the speed of the window's

+ tty. If your stty command operates on stdout, then add another

+ `!'. This is a useful command, when a screen window is directly

+ connected to a serial line that needs to be configured.

+

+`|less'

+`exec !..| less'

+ Both are equivalent. This adds a pager to the window output. The

+ special character `|' is needed to give the user control over the

+ pager although it gets its input from the window's process. This

+ works, because `less' listens on stderr (a behavior that `screen'

+ would not expect without the `|') when its stdin is not a tty.

+ `Less' versions newer than 177 fail miserably here; good old `pg'

+ still works.

+

+`!:sed -n s/.*Error.*/\007/p'

+ Sends window output to both, the user and the sed command. The sed

+ inserts an additional bell character (oct. 007) to the window

+ output seen by screen. This will cause 'Bell in window x'

+ messages, whenever the string `Error' appears in the window.

+

+

+superuser shell and a scrollback buffer of 1000 lines.

+ literal command character (by triggering the `meta' command) to Y

+ (similar to the `-e' option). Each argument is either a single

+ character, a two-character sequence of the form `^x' (meaning

+ `C-x'), a backslash followed by an octal number (specifying the

+ ASCII code of the character), or a backslash followed by a second

+ character, such as `\^' or `\\'. The default is `^Aa', but ```'

+ is recommended by one of the authors.

+ The `-t' option tells screen not to do inter-character timing. One

+ cannot turn off the timing if a termcap capability is used.

+ `args'. If `cmd' is omitted the key-binding is removed from the

+Make `foo' an abbreviation of the word `barfoo'. Timeout is disabled so

+This key-binding makes `C-t' an escape character for key-bindings. If

+you did the above `stuff barfoo' binding, you can enter the word `foo'

+by typing `C-t foo'. If you want to insert a `C-t' you have to press

+the key twice (i.e. escape the escape binding).

+in the window. The `info' command displays a line starting with `PRIN'

+while the printer is active.

+ one of the screenrc startup files, as they are meaningless once

+ the terminal emulator is booted.

+ `screen' will understand the `terminfo' command, which has the

+ same effects as the `termcap' command. Two separate commands are

+ termcap names of the capabilities should also be used with the

+ Switch cursor-keys to application mode.

+ Switch cursor-keys to cursor mode.

+ Change character foreground color in an ANSI conform way. This

+`TF'

+ (bool)

+ Add missing capabilities to the termcap/info entry. (Set by

+ default).

+

+charset). Each occurrence of `%' in <TEMPLATE> gets substituted with the

+switch sequence and the character mappings normally haven't much in

+ - Command: hardstatus [`always']`lastline'|`message'|`ignore' [STRING]

+ - Command: hardstatus `string' [STRING]

+ This command configures the use and emulation of the terminal's

+ hardstatus line. The first form toggles whether `screen' will use

+ the hardware status line to display messages. If the flag is set

+ to `off', these messages are overlaid in reverse video mode at the

+ display line. The default setting is `on'.

+

+ The second form tells screen what to do if the terminal doesn't

+ have a hardstatus line (i.e. the termcap/terminfo capabilities

+ "hs", "ts", "fs" and "ds" are not set). If the type `lastline' is

+ used, screen will reserve the last line of the display for the

+ hardstatus. `message' uses `screen''s message mechanism and

+ `ignore' tells `screen' never to display the hardstatus. If you

+ prepend the word `always' to the type, `screen' will use the type

+ even if the terminal supports a hardstatus line.

+

+ The third form specifies the contents of the hardstatus line.

+ `%h' is used as default string, i.e. the stored hardstatus of the

+ current window (settable via `\E]0;^G' or `\E_\\') is displayed.

+ You can customize this to any string you like including string

+ escapes (*Note String Escapes::). If you leave out the argument

+ STRING, the current string is displayed.

+

+ You can mix the second and third form by providing the string as

+ additional argument.

+ Copyright (c) 1993-1995 Free Software Foundation, Inc.

+File: screen.info, Node: Last Message, Next: Message Wait, Prev: Hardware Status Line, Up: Message Line

+

+Display Last Message

+====================

+

+ - Command: lastmsg

+ (`C-a m', `C-a C-m')

+ Repeat the last message displayed in the message line. Useful if

+ you're typing when a message appears, because (unless your

+ terminal has a hardware status line) the message goes away when

+ you press a key.

+

+

+File: screen.info, Node: Message Wait, Prev: Last Message, Up: Message Line

+

+Message Wait

+============

+

+ - Command: msgminwait SEC

+ (none)

+ Defines the time `screen' delays a new message when another is

+ currently displayed. Defaults to 1 second.

+

+ - Command: msgwait SEC

+ (none)

+ Defines the time a message is displayed, if `screen' is not

+ disturbed by other activity. Defaults to 5 seconds.

+

+

+File: screen.info, Node: Logging, Next: Startup, Prev: Message Line, Up: Top

+

+Logging

+*******

+

+ This section describes the commands for keeping a record of your

+session.

+

+* Menu:

+

+* Hardcopy:: Dump the current screen to a file

+* Log:: Log the output of a window to a file

+

+

+File: screen.info, Node: Hardcopy, Next: Log, Up: Logging

+

+hardcopy

+========

+

+ - Command: hardcopy

+ (`C-a h', `C-a C-h')

+ Writes out the current display contents to the file `hardcopy.N'

+ in the window's default directory, where N is the number of the

+ current window. This either appends or overwrites the file if it

+ exists, as determined by the `hardcopy_append' command.

+

+ - Command: hardcopy_append STATE

+ (none)

+ If set to `on', `screen' will append to the `hardcopy.N' files

+ created by the command `hardcopy'; otherwise, these files are

+ overwritten each time.

+

+ - Command: hardcopydir DIRECTORY

+ (none)

+ Defines a directory where hardcopy files will be placed. If unset

+ hardcopys are dumped in screen's current working directory.

+

+

+File: screen.info, Node: Log, Prev: Hardcopy, Up: Logging

+

+log

+===

+

+ - Command: log [STATE]

+ (`C-a H')

+ Begins/ends logging of the current window to the file

+ `screenlog.N' in the window's default directory, where N is the

+ number of the current window. This filename can be changed with

+ the `logfile' command. If no parameter is given, the logging

+ state is toggled. The session log is appended to the previous

+ contents of the file if it already exists. The current contents

+ and the contents of the scrollback history are not included in the

+ session log. Default is `off'.

+

+ - Command: logfile FILENAME

+ - Command: logfile FLUSH SECS

+ (none)

+ Defines the name the logfiles will get. The default is

+ `screenlog.%n'. The second form changes the number of seconds

+ `screen' will wait before flushing the logfile buffer to the

+ file-system. The default value is 10 seconds.

+

+ - Command: logtstamp [STATE]

+ - Command: logtstamp `after' SECS

+ - Command: logtstamp `string' STRING

+ (none)

+ This command controls logfile time-stamp mechanism of screen. If

+ time-stamps are turned `on', screen adds a string containing the

+ current time to the logfile after two minutes of inactivity. When

+ output continues and more than another two minutes have passed, a

+ second time-stamp is added to document the restart of the output.

+ You can change this timeout with the second form of the command.

+ The third form is used for customizing the time-stamp string (`--

+ %n:%t -- time-stamp -- %M/%d/%y %c:%s --\n' by default).

+

+

+File: screen.info, Node: Startup, Next: Miscellaneous, Prev: Logging, Up: Top

+

+Startup

+*******

+

+ This section describes commands which are only useful in the

+`.screenrc' file, for use at startup.

+

+* Menu:

+

+* echo:: Display a message.

+* sleep:: Pause execution of the `.screenrc'.

+* Startup Message:: Control display of the copyright notice.

+

+

+File: screen.info, Node: echo, Next: sleep, Up: Startup

+

+echo

+====

+

+ - Command: echo [`-n'] MESSAGE

+ (none)

+ The echo command may be used to annoy `screen' users with a

+ 'message of the day'. Typically installed in a global screenrc.

+ The option `-n' may be used to suppress the line feed. See also

+ `sleep'. Echo is also useful for online checking of environment

+ variables.

+

+

+File: screen.info, Node: sleep, Next: Startup Message, Prev: echo, Up: Startup

+

+sleep

+=====

+

+ - Command: sleep NUM

+ (none)

+ This command will pause the execution of a .screenrc file for NUM

+ seconds. Keyboard activity will end the sleep. It may be used to

+ give users a chance to read the messages output by `echo'.

+

+

+File: screen.info, Node: Startup Message, Prev: sleep, Up: Startup

+

+Startup Message

+===============

+

+ - Command: startup_message STATE

+ (none)

+ Select whether you want to see the copyright notice during startup.

+ Default is `on', as you probably noticed.

+

+

+File: screen.info, Node: Miscellaneous, Next: String Escapes, Prev: Startup, Up: Top

+

+Miscellaneous commands

+**********************

+

+ The commands described here do not fit well under any of the other

+categories.

+

+* Menu:

+

+* At:: Execute a command at other displays or windows.

+* Break:: Send a break signal to the window.

+* Debug:: Suppress/allow debugging output.

+* License:: Display the disclaimer page.

+* Nethack:: Use `nethack'-like error messages.

+* Nonblock:: Disable flow-control to a display.

+* Number:: Change the current window's number.

+* Silence:: Notify on inactivity.

+* Time:: Display the time and load average.

+* Verbose:: Display window creation commands.

+* Version:: Display the version of `screen'.

+* Zombie:: Keep dead windows.

+* Printcmd:: Set command for VT100 printer port emulation.

+* Sorendition:: Change the text highlighting method.

+

+

+File: screen.info, Node: At, Next: Break, Up: Miscellaneous

+

+At

+==

+

+ - Command: at [IDENTIFIER][#|*|%] COMMAND [ARGS]

+ (none)

+ Execute a command at other displays or windows as if it had been

+ entered there. `At' changes the context (the `current window' or

+ `current display' setting) of the command. If the first parameter

+ describes a non-unique context, the command will be executed

+ multiple times. If the first parameter is of the form

+ `IDENTIFIER*' then identifier is matched against user names. The

+ command is executed once for each display of the selected user(s).

+ If the first parameter is of the form `IDENTIFIER%' identifier is

+ matched against displays. Displays are named after the ttys they

+ attach. The prefix `/dev/' or `/dev/tty' may be omitted from the

+ identifier. If IDENTIFIER has a `#' or nothing appended it is

+ matched against window numbers and titles. Omitting an identifier

+ in front of the `#', `*' or `%' character selects all users,

+ displays or windows because a prefix-match is performed. Note that

+ on the affected display(s) a short message will describe what

+ happened. Note that the `#' character works as a comment

+ introducer when it is preceded by whitespace. This can be escaped

+ by prefixing `#' with a `\'. Permission is checked for the

+ initiator of the `at' command, not for the owners of the affected

+ display(s). Caveat: When matching against windows, the command is

+ executed at least once per window. Commands that change the

+ internal arrangement of windows (like `other') may be called

+ again. In shared windows the command will be repeated for each

+ attached display. Beware, when issuing toggle commands like

+ `login'! Some commands (e.g. `stuff', `\*Qprocess' or `paste')

+ require that a display is associated with the target windows.

+ These commands may not work correctly under `at' looping over

+ windows.

+

+

+File: screen.info, Node: Break, Next: Debug, Prev: At, Up: Miscellaneous

+

+Break

+=====

+

+ - Command: break [DURATION]

+ (none)

+ Send a break signal for DURATION*0.25 seconds to this window. For

+ non-Posix systems the time interval is rounded up to full seconds.

+ Most useful if a character device is attached to the window rather

+ than a shell process (*note Window Types::.). The maximum duration

+ of a break signal is limited to 15 seconds.

+

+ - Command: pow_break

+ (none)

+ Reopen the window's terminal line and send a break condition.

+

+ - Command: breaktype [TCSENDBREAK|TIOCSBRK|TCSBRK]

+ (none)

+ Choose one of the available methods of generating a break signal

+ for terminal devices. This command should affect the current

+ window only. But it still behaves identical to `defbreaktype'.

+ This will be changed in the future. Calling `breaktype' with no

+ parameter displays the break setting for the current window.

+

+ - Command: defbreaktype [TCSENDBREAK|TIOCSBRK|TCSBRK]

+ (none)

+ Choose one of the available methods of generating a break signal

+ for terminal devices opened afterwards. The preferred methods are

+ `tcsendbreak' and `TIOCSBRK'. The third, `TCSBRK', blocks the

+ complete `screen' session for the duration of the break, but it

+ may be the only way to generate long breaks. `tcsendbreak' and

+ `TIOCSBRK' may or may not produce long breaks with spikes (e.g. 4

+ per second). This is not only system dependant, this also differs

+ between serial board drivers. Calling `defbreaktype' with no

+ parameter displays the current setting.

+

+

+File: screen.info, Node: Debug, Next: License, Prev: Break, Up: Miscellaneous

+

+Debug

+=====

+

+ - Command: debug [ON|OFF]

+ (none)

+ Turns runtime debugging on or off. If `screen' has been compiled

+ with option `-DDEBUG' debugging is available and is turned on per

+ default. Note that this command only affects debugging output

+ from the main `SCREEN' process correctly. Debug output from

+ attacher processes can only be turned off once and forever.

+

+

+File: screen.info, Node: License, Next: Nethack, Prev: Debug, Up: Miscellaneous

+

+License

+=======

+

+ - Command: license

+ (none)

+ Display the disclaimer page. This is done whenever `screen' is

+ started without options, which should be often enough.

+

+

+File: screen.info, Node: Nethack, Next: Nonblock, Prev: License, Up: Miscellaneous

+

+Nethack

+=======

+

+ - Command: nethack STATE

+ (none)

+ Changes the kind of error messages used by `screen'. When you are

+ familiar with the game `nethack', you may enjoy the nethack-style

+ messages which will often blur the facts a little, but are much

+ funnier to read. Anyway, standard messages often tend to be

+ unclear as well.

+

+ This option is only available if `screen' was compiled with the

+ NETHACK flag defined (*note Installation::.). The default setting

+ is then determined by the presence of the environment variable

+ `$NETHACKOPTIONS'.

+

+

+File: screen.info, Node: Nonblock, Next: Number, Prev: Nethack, Up: Miscellaneous

+

+Nonblock

+========

+

+ - Command: nonblock STATE

+ Enable or disable flow control for the current user interface

+ (display). It is used to prevent a slow display from slowing down

+ the processing of data output by a window. This command may be

+ helpful when multiple displays show the same window. `Nonblock'

+ is initially off for all displays.

+

+

+File: screen.info, Node: Number, Next: Silence, Prev: Nonblock, Up: Miscellaneous

+

+Number

+======

+

+ - Command: number [N]

+ (`C-a N')

+ Change the current window's number. If the given number N is

+ already used by another window, both windows exchange their

+ numbers. If no argument is specified, the current window number

+ (and title) is shown.

+

+

+File: screen.info, Node: Silence, Next: Time, Prev: Number, Up: Miscellaneous

+

+Silence

+=======

+

+ - Command: silence [STATE|SEC]

+ (none)

+ Toggles silence monitoring of windows. When silence is turned on

+ and an affected window is switched into the background, you will

+ receive the silence notification message in the status line after

+ a specified period of inactivity (silence). The default timeout

+ can be changed with the `silencewait' command or by specifying a

+ number of seconds instead of `on' or `off'. Silence is initially

+ off for all windows.

+

+ - Command: defsilence STATE

+ (none)

+ Same as the `silence' command except that the default setting for

+ new windows is changed. Initial setting is `off'.

+

+ - Command: silencewait SECONDS

+ (none)

+ Define the time that all windows monitored for silence should wait

+ before displaying a message. Default is 30 seconds.

+

+

+File: screen.info, Node: Time, Next: Verbose, Prev: Silence, Up: Miscellaneous

+

+Time

+====

+

+ - Command: time

+ (`C-a t', `C-a C-t')

+ Uses the message line to display the time of day, the host name,

+ and the load averages over 1, 5, and 15 minutes (if this is

+ available on your system). For window-specific information use

+ `info' (*note Info::.).

+

+

+File: screen.info, Node: Verbose, Next: Version, Prev: Time, Up: Miscellaneous

+

+Verbose

+=======

+

+ - Command: verbose [ON|OFF]

+ If verbose is switched on, the command name is echoed, whenever a

+ window is created (or resurrected from zombie state). Default is

+ off. Without parameter, the current setting is shown.

+

+

+File: screen.info, Node: Version, Next: Zombie, Prev: Verbose, Up: Miscellaneous

+

+Version

+=======

+

+ - Command: version

+ (`C-a v')

+ Display the version and modification date in the message line.

+

+

+File: screen.info, Node: Zombie, Next: Printcmd, Prev: Version, Up: Miscellaneous

+

+Zombie

+======

+

+ - Command: zombie [KEYS]

+ - Command: defzombie [KEYS]

+ (none)

+ Per default windows are removed from the window list as soon as the

+ windows process (e.g. shell) exits. When a string of two keys is

+ specified to the zombie command, `dead' windows will remain in the

+ list. The `kill' command may be used to remove the window.

+ Pressing the first key in the dead window has the same effect.

+ Pressing the second key, however, screen will attempt to resurrect

+ the window. The process that was initially running in the window

+ will be launched again. Calling `zombie' without parameters will

+ clear the zombie setting, thus making windows disappear when the

+ process terminates.

+

+ As the zombie setting is affected globally for all windows, this

+ command should only be called `defzombie'. Until we need this as a

+ per window setting, the commands `zombie' and `defzombie' are

+ synonymous.

+

+

+File: screen.info, Node: Printcmd, Next: Sorendition, Prev: Zombie, Up: Miscellaneous

+

+Printcmd

+========

+

+ - Command: printcmd [CMD]

+ (none)

+ If CMD is not an empty string, screen will not use the terminal

+ capabilities `po/pf' for printing if it detects an ansi print

+ sequence `ESC [ 5 i', but pipe the output into CMD. This should

+ normally be a command like `lpr' or `cat > /tmp/scrprint'.

+ `Printcmd' without an argument displays the current setting. The

+ ansi sequence `ESC \' ends printing and closes the pipe.

+

+ Warning: Be careful with this command! If other user have write

+ access to your terminal, they will be able to fire off print

+ commands.

+

+

+File: screen.info, Node: Sorendition, Prev: Printcmd, Up: Miscellaneous

+

+Sorendition

+===========

+

+ - Command: sorendition [ATTR [COLOR]]

+ (none)

+ Change the way screen does highlighting for text marking and

+ printing messages. ATTR is a hexadecimal number and describes the

+ attributes (inverse, underline, ...) the text will get. COLOR is

+ a 2 digit number and changes the foreground/background of the

+ highlighted text. Some knowledge of screen's internal character

+ representation is needed to make the characters appear in the

+ desired way. The default is currently `10 99' (standout, default

+ colors).

+

+

+File: screen.info, Node: String Escapes, Next: Environment, Prev: Miscellaneous, Up: Top

+

+String Escapes

+**************

+

+ Screen provides an escape mechanism to insert information like the

+current time into messages or file names. The escape character is `%'

+with one exception: inside of a window's hardstatus `^%' (`^E') is used

+instead.

+

+ Here is the full list of supported escapes:

+

+`%'

+ the escape character itself

+

+`a'

+ either `am' or `pm'

+

+`A'

+ either `AM' or `PM'

+

+`c'

+ current time `HH:MM' in 24h format

+

+`C'

+ current time `HH:MM' in 12h format

+

+`d'

+ day number

+

+`D'

+ weekday name

+

+`h'

+ hardstatus of the window

+

+`l'

+ current load of the system

+

+`m'

+ month number

+

+`M'

+ month name

+

+`n'

+ window number

+

+`s'

+ seconds

+

+`t'

+ window title

+

+`u'

+ all other users on this window

+

+`w'

+ all window numbers and names

+

+`W'

+ all window numbers and names except the current one

+

+`y'

+ last two digits of the year number

+

+`Y'

+ full year number

+

+`?'

+ the part to the next `%?' is displayed only if an escape expands

+ to an nonempty string

+

+`:'

+ else part of `%?' The `c' and `C' escape may be qualified with a

+`0' to make screen use zero instead of space as fill character. The `n'

+escape understands a length qualifier (e.g. `%3n').

+

+

+File: screen.info, Node: Environment, Next: Files, Prev: String Escapes, Up: Top

+

+Environment Variables

+*********************

+

+`COLUMNS'

+ Number of columns on the terminal (overrides termcap entry).

+

+`HOME'

+ Directory in which to look for .screenrc.

+

+`LINES'

+ Number of lines on the terminal (overrides termcap entry).

+

+`LOCKPRG'

+ Screen lock program.

+

+`NETHACKOPTIONS'

+ Turns on `nethack' option.

+

+`PATH'

+ Used for locating programs to run.

+

+`SCREENCAP'

+ For customizing a terminal's `TERMCAP' value.

+

+`SCREENDIR'

+ Alternate socket directory.

+

+`SCREENRC'

+ Alternate user screenrc file.

+

+`SHELL'

+ Default shell program for opening windows (default `/bin/sh').

+

+`STY'

+ Alternate socket name. If `screen' is invoked, and the environment

+ variable `STY' is set, then it creates only a window in the

+ running `screen' session rather than starting a new session.

+

+`SYSSCREENRC'

+ Alternate system screenrc file.

+

+`TERM'

+ Terminal name.

+

+`TERMCAP'

+ Terminal description.

+

+

+File: screen.info, Node: Files, Next: Credits, Prev: Environment, Up: Top

+

+Files Referenced

+****************

+

+`.../screen-3.?.??/etc/screenrc'

+`.../screen-3.?.??/etc/etcscreenrc'

+ Examples in the `screen' distribution package for private and

+ global initialization files.

+

+``$SYSSCREENRC''

+`/local/etc/screenrc'

+ `screen' initialization commands

+

+``$SCREENRC''

+``$HOME'/.iscreenrc'

+``$HOME'/.screenrc'

+ Read in after /local/etc/screenrc

+

+``$SCREENDIR'/S-LOGIN'

+`/local/screens/S-LOGIN'

+ Socket directories (default)

+

+`/usr/tmp/screens/S-LOGIN'

+ Alternate socket directories.

+

+`SOCKET DIRECTORY/.termcap'

+ Written by the `dumptermcap' command

+

+`/usr/tmp/screens/screen-exchange or'

+`/tmp/screen-exchange'

+ `screen' interprocess communication buffer

+

+`hardcopy.[0-9]'

+ Screen images created by the hardcopy command

+

+`screenlog.[0-9]'

+ Output log files created by the log command

+

+`/usr/lib/terminfo/?/* or'

+`/etc/termcap'

+ Terminal capability databases

+

+`/etc/utmp'

+ Login records

+

+``$LOCKPRG''

+ Program for locking the terminal.

+

+

+File: screen.info, Node: Credits, Next: Bugs, Prev: Files, Up: Top

+

+Credits

+*******

+

+Authors

+=======

+

+ Originally created by Oliver Laumann, this latest version was

+produced by Wayne Davison, Juergen Weigert and Michael Schroeder.

+

+Contributors

+============

+

+ Ken Beal (kbeal@amber.ssd.csd.harris.com),

+ Rudolf Koenig (rfkoenig@informatik.uni-erlangen.de),

+ Toerless Eckert (eckert@informatik.uni-erlangen.de),

+ Wayne Davison (davison@borland.com),

+ Patrick Wolfe (pat@kai.com, kailand!pat),

+ Bart Schaefer (schaefer@cse.ogi.edu),

+ Nathan Glasser (nathan@brokaw.lcs.mit.edu),

+ Larry W. Virden (lvirden@cas.org),

+ Howard Chu (hyc@hanauma.jpl.nasa.gov),

+ Tim MacKenzie (tym@dibbler.cs.monash.edu.au),

+ Markku Jarvinen (mta@{cc,cs,ee}.tut.fi),

+ Marc Boucher (marc@CAM.ORG),

+ Doug Siebert (dsiebert@isca.uiowa.edu),

+ Ken Stillson (stillson@tsfsrv.mitre.org),

+ Ian Frechett (frechett@spot.Colorado.EDU),

+ Brian Koehmstedt (bpk@gnu.ai.mit.edu),

+ Don Smith (djs6015@ultb.isc.rit.edu),

+ Frank van der Linden (vdlinden@fwi.uva.nl),

+ Martin Schweikert (schweik@cpp.ob.open.de),

+ David Vrona (dave@sashimi.lcu.com),

+ E. Tye McQueen (tye%spillman.UUCP@uunet.uu.net),

+ Matthew Green (mrg@mame.mu.oz.au),

+ Christopher Williams (cgw@unt.edu),

+ Matt Mosley (mattm@access.digex.net),

+ Gregory Neil Shapiro (gshapiro@wpi.WPI.EDU),

+ Jason Merrill (jason@jarthur.Claremont.EDU).

+

+Version

+=======

+

+ This manual describes version 3.9.0 of the `screen' program. Its

+roots are a merge of a custom version 2.3PR7 by Wayne Davison and

+several enhancements to Oliver Laumann's version 2.0. Note that all

+versions numbered 2.x are copyright by Oliver Laumann.

+

+ See also *Note Availability::.

+

+

+File: screen.info, Node: Bugs, Next: Installation, Prev: Credits, Up: Top

+

+Bugs

+****

+

+ Just like any other significant piece of software, `screen' has a

+few bugs and missing features. Please send in a bug report if you have

+found a bug not mentioned here.

+

+* Menu:

+

+* Known Bugs:: Problems we know about.

+* Reporting Bugs:: How to contact the maintainers.

+* Availability:: Where to find the lastest screen version.

+

+

+File: screen.info, Node: Known Bugs, Next: Reporting Bugs, Up: Bugs

+

+Known Bugs

+==========

+

+ * `dm' (delete mode) and `xs' are not handled correctly (they are

+ ignored). `xn' is treated as a magic-margin indicator.

+

+ * `screen' has no clue about double-high or double-wide characters.

+ But this is the only area where `vttest' is allowed to fail.

+

+ * It is not possible to change the environment variable `$TERMCAP'

+ when reattaching under a different terminal type.

+

+ * The support of terminfo based systems is very limited. Adding extra

+ capabilities to `$TERMCAP' may not have any effects.

+

+ * `screen' does not make use of hardware tabs.

+

+ * `screen' must be installed setuid root on most systems in order to

+ be able to correctly change the owner of the tty device file for

+ each window. Special permission may also be required to write the

+ file `/etc/utmp'.

+

+ * Entries in `/etc/utmp' are not removed when `screen' is killed

+ with SIGKILL. This will cause some programs (like "w" or "rwho")

+ to advertise that a user is logged on who really isn't.

+

+ * `screen' may give a strange warning when your tty has no utmp

+ entry.

+

+ * When the modem line was hung up, `screen' may not automatically

+ detach (or quit) unless the device driver sends a HANGUP signal.

+ To detach such a `screen' session use the -D or -d command line

+ option.

+

+ * If a password is set, the command line options -d and -D still

+ detach a session without asking.

+

+ * Both `breaktype' and `defbreaktype' change the break generating

+ method used by all terminal devices. The first should change a

+ window specific setting, where the latter should change only the

+ default for new windows.

+

+ * When attaching to a multiuser session, the user's `.screenrc' file

+ is not sourced. Each users personal settings have to be included

+ in the `.screenrc' file from which the session is booted, or have

+ to be changed manually.

+

+ * A weird imagination is most useful to gain full advantage of all

+ the features.

+

+

+that triggered the bug. Please recompile `screen' with the `-DDEBUG'

+options enabled, reproduce the bug, and have a look at the debug output

+written to the directory `/tmp/debug'. If necessary quote suspect

+passages from the debug output and show the contents of your `config.h'

+if it matters.

+site. The home site of `screen' is `ftp.uni-erlangen.de

+(131.188.3.71)', in the directory `pub/utilities/screen'. The

+subdirectory `private' contains the latest beta testing release. If

+you want to help, send a note to screen@uni-erlangen.de.

+any mode 700 directory in the environment variable `$SCREENDIR'.

+* command character: Command Character.

+* escape character: Command Character.

+* regions: Regions.

+* string escapes: String Escapes.

+* window types: Window Types.

+* aclgrp: Aclgrp.

+* aclumask: Umask.

+* addacl: Acladd.