Strict Standards: Declaration of action_plugin_loglog::register() should be compatible with DokuWiki_Action_Plugin::register($controller) in /home/public/screen/lib/plugins/loglog/action.php on line 15

Strict Standards: Declaration of action_plugin_captcha::register() should be compatible with DokuWiki_Action_Plugin::register($controller) in /home/public/screen/lib/plugins/captcha/action.php on line 0terminal

screen is flexible about flow control. Traditionally, some terminals
do flow control in-band, using ^S when they want to stop the flow data
and ^Q when they want it to resume. On the other hand, some programs
(such as emacs) use those keys for other purposes. If flow control is
turned on in screen, ^S will stop screen from sending anything
more to your terminal and ^Q will resume. Turning flow control off
allows those characters to pass through to your programs. The default
setting is “auto”, which attempts to determine if flow control is needed
or not. screen is generally pretty good at figuring this out.

screen can deal with multiple character sets and character encodings. The
encoding and defencoding commands can be used to set window
encodings or override the detected terminal encoding. If the display's
and window's encodings differ, screen will translate between the two.
Characters not in the display's charset are represented by question marks.
screen does its own encoding and only supports a handful of encodings. As
of version 4.0.2, those are: C, eucJP, SJIS, eucKR, eucCN, Big5, KOI8-R,
CP1251, UTF-8, ISO8859-2, ISO8859-3, ISO8859-4, ISO8859-5, ISO8859-6,
ISO8859-7, ISO8859-8, ISO8859-9, ISO8859-10, ISO8859-15, jis, and GBK.
[This somehow ties in with the charset setting, but I don't
understand that one. <PMG>]

You can alter various aspects of screen's use of termcap and terminfo, via
the termcap, terminfo, and
termcapinfo commands. All three have the same syntax.
Using termcapinfo is recommended, since that affects both
termcap and terminfo settings. Note that all three require the use of
termcap names; terminfo-style long names are not supported. The most
common use of these commands is to change how screen treats display
terminals. If you want to change a termcap setting for, say, xterms, you
can use the termcapinfo command to change the termcap
definition that screen uses for that terminal type. This affects only
screen, and can be used to effect changes when you don't want to or
can't change the system terminal definitions. There are also several
special terminal capabilities that are screen-specific. See
the “Examples” section below for specific examples. The other use is to change
the terminal capabilities of screen's virtual terminal. This can be
useful to alter how other programs interact with screen, without
having to edit screen's source code and recompile. [This is ugly.
I need to rewrite it to make it clearer. <PMG>]

Some programs use ANSI escape sequences to print data; this was originally used in the days when serial terminals were common, and a terminal might have a printer directly attached to it. Any sequence starting with <esc>[5i and ending with <esc>\ would cause the data between the two escape sequences to be printed. screen supports this behavior in two ways: if the display terminal has the po and pf termcap entries (indicating that it understands printing escapes), screen will pass any print requests through to the display terminal. Alternately, you can use the printcmd command to define a program to which screen will send any print jobs.

Abuse screen's hardstatus support to put things in xterm titlebars.
This tells screen that xterms (and related terminals) have a
hardstatus line (hs) and sets the escape sequences for entering
(ts) and leaving (fs) the hardstatus to the sequences for entering
and leaving the titlebar. To go with that, uses
defhstatus to set a default message and
hardstatus off to tell screen not to use the
hardstatus line for screen messages: