<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
	>

<channel>
	<title>Man Page A Day</title>
	<atom:link href="https://manpageaday.wordpress.com/feed/" rel="self" type="application/rss+xml" />
	<link>https://manpageaday.wordpress.com</link>
	<description>One Manpage every day, so you can Linux better</description>
	<lastBuildDate>Fri, 13 May 2011 06:15:00 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
<site xmlns="com-wordpress:feed-additions:1">20524413</site><cloud domain='manpageaday.wordpress.com' port='80' path='/?rsscloud=notify' registerProcedure='' protocol='http-post' />
<image>
		<url>https://s2.wp.com/i/webclip.png</url>
		<title>Man Page A Day</title>
		<link>https://manpageaday.wordpress.com</link>
	</image>
	<atom:link rel="search" type="application/opensearchdescription+xml" href="https://manpageaday.wordpress.com/osd.xml" title="Man Page A Day" />
	<atom:link rel='hub' href='https://manpageaday.wordpress.com/?pushpress=hub'/>
	<item>
		<title>git-whatchanged</title>
		<link>https://manpageaday.wordpress.com/2011/05/13/git-whatchanged/</link>
					<comments>https://manpageaday.wordpress.com/2011/05/13/git-whatchanged/#respond</comments>
		
		<dc:creator><![CDATA[Ryan Gooler]]></dc:creator>
		<pubDate>Fri, 13 May 2011 06:14:59 +0000</pubDate>
				<category><![CDATA[Uncategorized]]></category>
		<guid isPermaLink="false">http://manpageaday.wordpress.com/?p=197</guid>

					<description><![CDATA[SYNOPSIS git-whatchanged &#60;option&#62;&#8230; DESCRIPTION Shows commit logs and diff output each commit introduces. The command internally invokes git-rev-list piped to git-diff-tree, and takes command line options for both of these commands. This manual page describes only the most frequently used options. OPTIONS -p Show textual diffs, instead of the git internal diff output format that [&#8230;]]]></description>
										<content:encoded><![CDATA[<p><PRE><br />
<!-- Manpage converted by man2html 3.0.1 --><br />
SYNOPSIS<br />
       git-whatchanged &lt;option&gt;&#8230;</p>
<p>DESCRIPTION<br />
       Shows commit logs and diff output each commit introduces. The command<br />
       internally invokes git-rev-list piped to git-diff-tree, and takes<br />
       command line options for both of these commands.</p>
<p>       This manual page describes only the most frequently used options.</p>
<p>OPTIONS<br />
       -p<br />
           Show textual diffs, instead of the git internal diff output format<br />
           that is useful only to tell the changed paths and their nature of<br />
           changes.</p>
<p>       -&lt;n&gt;<br />
           Limit output to &lt;n&gt; commits.</p>
<p>       &lt;since&gt;..&lt;until&gt;<br />
           Limit output to between the two named commits (bottom exclusive,<br />
           top inclusive).</p>
<p>       -r<br />
           Show git internal diff output, but for the whole tree, not just the<br />
           top level.</p>
<p>       -m<br />
           By default, differences for merge commits are not shown. With this<br />
           flag, show differences to that commit from all of its parents.</p>
<p>           However, it is not very useful in general, although it is useful on<br />
           a file-by-file basis.</p>
<p>       &#8211;pretty[=&lt;format&gt;]<br />
           Pretty-print the contents of the commit logs in a given format,<br />
           where &lt;format&gt; can be one of oneline, short, medium, full, fuller,<br />
           email, raw and format:&lt;string&gt;. When omitted, the format defaults<br />
           to medium.</p>
<p>           Note: you can specify the default pretty format in the repository<br />
           configuration (see <B>git-config(1)</B>).</p>
<p>       &#8211;abbrev-commit<br />
           Instead of showing the full 40-byte hexadecimal commit object name,<br />
           show only handful hexdigits prefix. Non default number of digits<br />
           can be specified with &#8220;&#8211;abbrev=&lt;n&gt;&#8221; (which also modifies diff<br />
           output, if it is displayed).</p>
<p>           This should make &#8220;&#8211;pretty=oneline&#8221; a whole lot more readable for</p>
<p>       limited your view of history: for example, if you are only interested<br />
       in changes related to a certain directory or file.</p>
<p>       Here are some additional details for each format:</p>
<p>       o    oneline</p>
<p>               &lt;sha1&gt; &lt;title line&gt;<br />
           This is designed to be as compact as possible.</p>
<p>       o    short</p>
<p>               commit &lt;sha1&gt;<br />
               Author: &lt;author&gt;</p>
<p>               &lt;title line&gt;</p>
<p>       o    medium</p>
<p>               commit &lt;sha1&gt;<br />
               Author: &lt;author&gt;<br />
               Date: &lt;author date&gt;</p>
<p>               &lt;title line&gt;</p>
<p>               &lt;full commit message&gt;</p>
<p>       o    full</p>
<p>               commit &lt;sha1&gt;<br />
               Author: &lt;author&gt;<br />
               Commit: &lt;committer&gt;</p>
<p>               &lt;title line&gt;</p>
<p>               &lt;full commit message&gt;</p>
<p>       o    fuller</p>
<p>               commit &lt;sha1&gt;<br />
               Author: &lt;author&gt;<br />
               AuthorDate: &lt;author date&gt;<br />
               Commit: &lt;committer&gt;<br />
               CommitDate: &lt;committer date&gt;</p>
<p>               &lt;title line&gt;</p>
<p>               &lt;full commit message&gt;</p>
<p>       o    email</p>
<p>       o    format:</p>
<p>           The format: format allows you to specify which information you want<br />
           to show. It works a little bit like printf format, with the notable<br />
           exception that you get a newline with %n instead of \n.</p>
<p>           E.g, format:&#8221;The author of %h was %an, %ar%nThe title was &gt;&gt;%s&lt;&lt;%n&#8221;<br />
           would show something like this:</p>
<p>               The author of fe6e0ee was Junio C Hamano, 23 hours ago<br />
               The title was &gt;&gt;t4119: test autocomputing -p&lt;n&gt; for traditional diff input.&lt;&lt;<br />
           The placeholders are:</p>
<p>           o    %H: commit hash</p>
<p>           o    %h: abbreviated commit hash</p>
<p>           o    %T: tree hash</p>
<p>           o    %t: abbreviated tree hash</p>
<p>           o    %P: parent hashes</p>
<p>           o    %p: abbreviated parent hashes</p>
<p>           o    %an: author name</p>
<p>           o    %aN: author name (respecting .mailmap)</p>
<p>           o    %ae: author email</p>
<p>           o    %ad: author date</p>
<p>           o    %aD: author date, RFC2822 style</p>
<p>           o    %ar: author date, relative</p>
<p>           o    %at: author date, UNIX timestamp</p>
<p>           o    %ai: author date, ISO 8601 format</p>
<p>           o    %cn: committer name</p>
<p>           o    %cN: committer name (respecting .mailmap)</p>
<p>           o    %ce: committer email</p>
<p>           o    %cd: committer date</p>
<p>           o    %cD: committer date, RFC2822 style</p>
<p>           o    %Cgreen: switch color to green</p>
<p>           o    %Cblue: switch color to blue</p>
<p>           o    %Creset: reset color</p>
<p>           o    %m: left, right or boundary mark</p>
<p>           o    %n: newline</p>
<p>           o    %x00: print a byte from a hex code</p>
<p>       o    tformat:</p>
<p>           The tformat: format works exactly like format:, except that it<br />
           provides &#8220;terminator&#8221; semantics instead of &#8220;separator&#8221; semantics.<br />
           In other words, each commit has the message terminator character<br />
           (usually a newline) appended, rather than a separator placed<br />
           between entries. This means that the final entry of a single-line<br />
           format will be properly terminated with a new line, just as the<br />
           &#8220;oneline&#8221; format does. For example:</p>
<p>               $ git log -2 &#8211;pretty=format:%h 4da45bef \<br />
                 | perl -pe &#8216;$_ .= &#8221; &#8212; NO NEWLINE\n&#8221; unless /\n/&#8217;<br />
               4da45be<br />
               7134973 &#8212; NO NEWLINE</p>
<p>               $ git log -2 &#8211;pretty=tformat:%h 4da45bef \<br />
                 | perl -pe &#8216;$_ .= &#8221; &#8212; NO NEWLINE\n&#8221; unless /\n/&#8217;<br />
               4da45be<br />
               7134973</p>
<p>EXAMPLES<br />
       git-whatchanged -p v2.6.12.. include/scsi drivers/scsi<br />
           Show as patches the commits since version v2.6.12 that changed any<br />
           file in the include/scsi or drivers/scsi subdirectories</p>
<p>       git-whatchanged &#8211;since=&#8221;2 weeks ago&#8221; &#8212; gitk<br />
           Show the changes during the last two weeks to the file gitk. The<br />
           &#8220;&#8211;&#8221; is necessary to avoid confusion with the branch named gitk</p>
<p>AUTHOR<br />
       Written by Linus Torvalds &lt;torvalds@osdl.org[1]&gt; and Junio C Hamano<br />
       &lt;gitster@pobox.com[2]&gt;</p>
<p>DOCUMENTATION<br />
       Documentation by David Greaves, Junio C Hamano and the git-list<br />
       &lt;git@vger.kernel.org[3]&gt;.</p>
<p>GIT</p>
<p>Git 1.5.6.5                       09/24/2010                <B>GIT-WHATCHANGED(1)</B><br />
</PRE></p>
]]></content:encoded>
					
					<wfw:commentRss>https://manpageaday.wordpress.com/2011/05/13/git-whatchanged/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">197</post-id>
		<media:content url="https://1.gravatar.com/avatar/7e5a914fa78c2f8cff1b5a3a1e56626bd1af981cea33e799a05a752770013ffc?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">manpageaday</media:title>
		</media:content>
	</item>
		<item>
		<title>run-mailcap</title>
		<link>https://manpageaday.wordpress.com/2011/05/12/run-mailcap/</link>
					<comments>https://manpageaday.wordpress.com/2011/05/12/run-mailcap/#respond</comments>
		
		<dc:creator><![CDATA[Ryan Gooler]]></dc:creator>
		<pubDate>Thu, 12 May 2011 06:14:56 +0000</pubDate>
				<category><![CDATA[Uncategorized]]></category>
		<guid isPermaLink="false">http://manpageaday.wordpress.com/?p=195</guid>

					<description><![CDATA[SYNOPSIS run-mailcap &#8211;action=ACTION [&#8211;debug] [MIME-TYPE:[ENCODING:]]FILE [&#8230;] The see, edit, compose and print versions are just aliases that default to the view, edit, compose, and print actions (respectively). DESCRIPTION run-mailcap (or any of its aliases) will use the given action to pro- cess each mime-type/file in turn. Each file is specified as its mime- type, its [&#8230;]]]></description>
										<content:encoded><![CDATA[<p><PRE><br />
<!-- Manpage converted by man2html 3.0.1 --></p>
<p>SYNOPSIS<br />
       run-mailcap &#8211;action=ACTION [&#8211;debug] [MIME-TYPE:[ENCODING:]]FILE [&#8230;]</p>
<p>       The see, edit, compose and print versions are just aliases that default<br />
       to the view, edit, compose, and print actions (respectively).</p>
<p>DESCRIPTION<br />
       run-mailcap (or any of its aliases) will use the given action  to  pro-<br />
       cess  each mime-type/file in turn.  Each file is specified as its mime-<br />
       type, its encoding (e.g. compression), and filename together, separated<br />
       by  colons.   If  the mime-type is omitted, an attempt to determine the<br />
       type is made by trying to match the file&#8217;s extension with those in  the<br />
       mime.types  files.   If the encoding is omitted, it will also be deter-<br />
       mined from the file&#8217;s extensions.  Currently  supported  encodings  are<br />
       gzip (.gz), bzip (.bz), bzip2 (.bz2), and compress (.Z).  A filename of<br />
       &#8220;-&#8221; can be used to mean &#8220;standard input&#8221;, but then a mime-type must  be<br />
       specified.</p>
<p>       Both  the user&#8217;s files (~/.mailcap; ~/.mime.types) and the system files<br />
       (/etc/mailcap; /etc/mime.types) are searched in turn for information.</p>
<p>   EXAMPLES<br />
         see picture.jpg<br />
         print output.ps.gz<br />
         compose text/html:index.htm<br />
         extract-mail-attachment msg.txt | see image/tiff:gzip:-</p>
<p>   OPTIONS<br />
       All options are in the form &#8211;&lt;opt&gt;=&lt;value&gt;.</p>
<p>       &#8211;action=&lt;action&gt;<br />
              Performs the specified action on the files.  Valid  actions  are<br />
              view,  compose,  composetyped,  edit and print.  If no action is<br />
              specified, the action will be determined by how the program  was<br />
              called.</p>
<p>       &#8211;debug=&lt;value&gt;<br />
              Turns  on  extra information to find out what is happening.  Any<br />
              value other than zero (0) will turn on debugging output.</p>
<p>SEE ALSO<br />
       <B>update-mime(8)</B></p>
<p>AUTHOR<br />
       run-mailcap  (and   its   aliases)   was   written   by   Brian   White<br />
       &lt;bcwhite@pobox.com&gt;.</p>
<p>COPYRIGHT<br />
       run-mailcap  (and  its  aliases) is in the public domain (the only true<br />
       &#8220;free&#8221;).<br />
</PRE></p>
]]></content:encoded>
					
					<wfw:commentRss>https://manpageaday.wordpress.com/2011/05/12/run-mailcap/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">195</post-id>
		<media:content url="https://1.gravatar.com/avatar/7e5a914fa78c2f8cff1b5a3a1e56626bd1af981cea33e799a05a752770013ffc?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">manpageaday</media:title>
		</media:content>
	</item>
		<item>
		<title>yuvsplittoppm</title>
		<link>https://manpageaday.wordpress.com/2011/05/11/yuvsplittoppm/</link>
					<comments>https://manpageaday.wordpress.com/2011/05/11/yuvsplittoppm/#respond</comments>
		
		<dc:creator><![CDATA[Ryan Gooler]]></dc:creator>
		<pubDate>Wed, 11 May 2011 06:14:54 +0000</pubDate>
				<category><![CDATA[Uncategorized]]></category>
		<guid isPermaLink="false">http://manpageaday.wordpress.com/?p=193</guid>

					<description><![CDATA[SYNOPSIS yuvsplittoppm basename width height [-ccir601] DESCRIPTION Reads three files, containing the YUV components, as input. These files are basename.Y, basename.U, and basename.V. Produces a portable pixmap on stdout. Since the YUV files are raw files, the dimensions width and height must be specified on the command line. OPTIONS -ccir601 Assumes that the YUV triplets [&#8230;]]]></description>
										<content:encoded><![CDATA[<p><PRE><br />
<!-- Manpage converted by man2html 3.0.1 --></p>
<p>SYNOPSIS<br />
       yuvsplittoppm basename width height [-ccir601]</p>
<p>DESCRIPTION<br />
       Reads three files, containing the  YUV  components,  as  input.   These<br />
       files  are basename.Y, basename.U, and basename.V.  Produces a portable<br />
       pixmap on stdout.</p>
<p>       Since the YUV files are raw files, the dimensions width and height must<br />
       be specified on the command line.</p>
<p>OPTIONS<br />
       -ccir601<br />
              Assumes  that the YUV triplets are scaled into the smaller range<br />
              of the CCIR 601 (MPEG) standard. Else, the JFIF (JPEG)  standard<br />
              is assumed.</p>
<p>SEE ALSO<br />
       <B>ppmtoyuvsplit(1)</B>, <B>yuvtoppm(1)</B>, <B>ppm(5)</B></p>
<p>AUTHOR<br />
       Marcel Wijkstra &lt;wijkstra@fwi.uva.nl&gt;, based on ppmtoyuvsplit.</p>
<p>                                 26 August 93                 <B>yuvsplittoppm(1)</B><br />
</PRE></p>
]]></content:encoded>
					
					<wfw:commentRss>https://manpageaday.wordpress.com/2011/05/11/yuvsplittoppm/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">193</post-id>
		<media:content url="https://1.gravatar.com/avatar/7e5a914fa78c2f8cff1b5a3a1e56626bd1af981cea33e799a05a752770013ffc?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">manpageaday</media:title>
		</media:content>
	</item>
		<item>
		<title>ipcrm</title>
		<link>https://manpageaday.wordpress.com/2011/05/10/ipcrm-2/</link>
					<comments>https://manpageaday.wordpress.com/2011/05/10/ipcrm-2/#respond</comments>
		
		<dc:creator><![CDATA[Ryan Gooler]]></dc:creator>
		<pubDate>Tue, 10 May 2011 06:14:52 +0000</pubDate>
				<category><![CDATA[Uncategorized]]></category>
		<guid isPermaLink="false">http://manpageaday.wordpress.com/?p=191</guid>

					<description><![CDATA[SYNOPSIS ipcrm [ -M key &#124; -m id &#124; -Q key &#124; -q id &#124; -S key &#124; -s id ] &#8230; deprecated usage ipcrm [ shm &#124; msg &#124; sem ] id &#8230; DESCRIPTION ipcrm removes System V interprocess communication (IPC) objects and associated data structures from the system. In order to delete such [&#8230;]]]></description>
										<content:encoded><![CDATA[<p><PRE><br />
<!-- Manpage converted by man2html 3.0.1 --><br />
SYNOPSIS<br />
       ipcrm [ -M key | -m id | -Q key | -q id | -S key | -s id ] &#8230;</p>
<p>       deprecated usage</p>
<p>       ipcrm [ shm | msg | sem ] id &#8230;</p>
<p>DESCRIPTION<br />
       ipcrm  removes  System  V  interprocess communication (IPC) objects and<br />
       associated data structures from the system.  In order  to  delete  such<br />
       objects,  you must be superuser, or the creator or owner of the object.</p>
<p>       System V IPC objects are of three types: shared memory, message queues,<br />
       and  semaphores.   Deletion  of  a message queue or semaphore object is<br />
       immediate (regardless of whether any process still holds an IPC identi-<br />
       fier for the object).  A shared memory object is only removed after all<br />
       currently attached processes have detached (<B>shmdt(2)</B>) the  object  from<br />
       their virtual address space.</p>
<p>       Two syntax styles are supported.  The old Linux historical syntax spec-<br />
       ifies a three letter keyword indicating which class of object is to  be<br />
       deleted,  followed  by  one or more IPC identifiers for objects of this<br />
       type.</p>
<p>       The SUS-compliant syntax allows  the  specification  of  zero  or  more<br />
       objects of all three types in a single command line, with objects spec-<br />
       ified either by key or by identifier. (See below.)  Both keys and iden-<br />
       tifiers  may  be  specified  in decimal, hexadecimal (specified with an<br />
       initial &#8216;0x&#8217; or &#8216;0X&#8217;), or octal (specified with an initial &#8216;0&#8217;).</p>
<p>OPTIONS<br />
       -M shmkey<br />
              removes the shared memory segment created with shmkey after  the<br />
              last detach is performed.</p>
<p>       -m shmid<br />
              removes  the shared memory segment identified by shmid after the<br />
              last detach is performed.</p>
<p>       -Q msgkey<br />
              removes the message queue created with msgkey.</p>
<p>       -q msgid<br />
              removes the message queue identified by msgid.</p>
<p>       -S semkey<br />
              removes the semaphore created with semkey.</p>
<p>       -s semid<br />
              removes the semaphore identified by semid.</p>
<p>AVAILABILITY<br />
       The ipcrm command is part of the util-linux-ng package and is available<br />
       from ftp://ftp.kernel.org/pub/linux/utils/util-linux-ng/.</p>
<p>ipcrm                     last change: 19 March 2002                  <B>IPCRM(1)</B><br />
</PRE></p>
]]></content:encoded>
					
					<wfw:commentRss>https://manpageaday.wordpress.com/2011/05/10/ipcrm-2/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">191</post-id>
		<media:content url="https://1.gravatar.com/avatar/7e5a914fa78c2f8cff1b5a3a1e56626bd1af981cea33e799a05a752770013ffc?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">manpageaday</media:title>
		</media:content>
	</item>
		<item>
		<title>wc</title>
		<link>https://manpageaday.wordpress.com/2011/05/09/wc/</link>
					<comments>https://manpageaday.wordpress.com/2011/05/09/wc/#respond</comments>
		
		<dc:creator><![CDATA[Ryan Gooler]]></dc:creator>
		<pubDate>Mon, 09 May 2011 06:14:47 +0000</pubDate>
				<category><![CDATA[Uncategorized]]></category>
		<guid isPermaLink="false">http://manpageaday.wordpress.com/?p=189</guid>

					<description><![CDATA[SYNOPSIS wc [OPTION]&#8230; [FILE]&#8230; wc [OPTION]&#8230; &#8211;files0-from=F DESCRIPTION Print newline, word, and byte counts for each FILE, and a total line if more than one FILE is specified. With no FILE, or when FILE is -, read standard input. -c, &#8211;bytes print the byte counts -m, &#8211;chars print the character counts -l, &#8211;lines print the [&#8230;]]]></description>
										<content:encoded><![CDATA[<p><PRE><br />
<!-- Manpage converted by man2html 3.0.1 --><br />
SYNOPSIS<br />
       wc [OPTION]&#8230; [FILE]&#8230;<br />
       wc [OPTION]&#8230; &#8211;files0-from=F</p>
<p>DESCRIPTION<br />
       Print newline, word, and byte counts for each FILE, and a total line if<br />
       more than one FILE is specified.  With no FILE, or when FILE is -, read<br />
       standard input.</p>
<p>       -c, &#8211;bytes<br />
              print the byte counts</p>
<p>       -m, &#8211;chars<br />
              print the character counts</p>
<p>       -l, &#8211;lines<br />
              print the newline counts</p>
<p>       &#8211;files0-from=F<br />
              read  input  from the files specified by NUL-terminated names in<br />
              file F</p>
<p>       -L, &#8211;max-line-length<br />
              print the length of the longest line</p>
<p>       -w, &#8211;words<br />
              print the word counts</p>
<p>       &#8211;help display this help and exit</p>
<p>       &#8211;version<br />
              output version information and exit</p>
<p>AUTHOR<br />
       Written by Paul Rubin and David MacKenzie.</p>
<p>REPORTING BUGS<br />
       Report bugs to &lt;bug-coreutils@gnu.org&gt;.</p>
<p>COPYRIGHT<br />
       Copyright (C) 2008 Free Software Foundation, Inc.  License GPLv3+:  GNU<br />
       GPL version 3 or later &lt;http://gnu.org/licenses/gpl.html&gt;<br />
       This  is  free  software:  you  are free to change and redistribute it.<br />
       There is NO WARRANTY, to the extent permitted by law.</p>
<p>SEE ALSO<br />
       The full documentation for wc is maintained as a  Texinfo  manual.   If<br />
       the  info and wc programs are properly installed at your site, the com-<br />
       mand</p>
<p>              info wc</p>
<p></PRE></p>
]]></content:encoded>
					
					<wfw:commentRss>https://manpageaday.wordpress.com/2011/05/09/wc/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">189</post-id>
		<media:content url="https://1.gravatar.com/avatar/7e5a914fa78c2f8cff1b5a3a1e56626bd1af981cea33e799a05a752770013ffc?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">manpageaday</media:title>
		</media:content>
	</item>
		<item>
		<title>mcookie</title>
		<link>https://manpageaday.wordpress.com/2011/05/08/mcookie-2/</link>
					<comments>https://manpageaday.wordpress.com/2011/05/08/mcookie-2/#respond</comments>
		
		<dc:creator><![CDATA[Ryan Gooler]]></dc:creator>
		<pubDate>Sun, 08 May 2011 06:14:44 +0000</pubDate>
				<category><![CDATA[Uncategorized]]></category>
		<guid isPermaLink="false">http://manpageaday.wordpress.com/?p=187</guid>

					<description><![CDATA[SYNOPSIS mcookie [-v] [-f filename ] DESCRIPTION mcookie generates a 128-bit random hexadecimal number for use with the X authority system. Typical usage: xauth add :0 . `mcookie` The &#8220;random&#8221; number generated is actually the output of the MD5 message digest fed with various piece of random information: the current time, the process id, the [&#8230;]]]></description>
										<content:encoded><![CDATA[<p><PRE><br />
<!-- Manpage converted by man2html 3.0.1 --><br />
SYNOPSIS<br />
       mcookie [-v] [-f filename ]</p>
<p>DESCRIPTION<br />
       mcookie  generates a 128-bit random hexadecimal number for use with the<br />
       X authority system.  Typical usage:<br />
              xauth add :0 . `mcookie`</p>
<p>       The &#8220;random&#8221; number generated is actually the output of the MD5 message<br />
       digest  fed with various piece of random information: the current time,<br />
       the process id, the parent process id, the contents of  an  input  file<br />
       (if  -f  is specified), and several bytes of information from the first<br />
       of the following devices which is present:  /dev/random,  /dev/urandom,<br />
       files in /proc, /dev/audio.</p>
<p>BUGS<br />
       The  entropy  in  the  generated  128-bit is probably quite small (and,<br />
       therefore, vulnerable to attack) unless a non-pseudorandom number  gen-<br />
       erator is used (e.g., /dev/random under Linux).</p>
<p>       It is assumed that none of the devices opened will block.</p>
<p>FILES<br />
       /dev/random<br />
       /dev/urandom<br />
       /dev/audio<br />
       /proc/stat<br />
       /proc/loadavg</p>
<p>SEE ALSO<br />
       <B>X(1)</B>, <B>xauth(1)</B>, <B>md5sum(1)</B></p>
<p>AVAILABILITY<br />
       The  mcookie command is part of the util-linux-ng package and is avail-<br />
       able from ftp://ftp.kernel.org/pub/linux/utils/util-linux-ng/.</p>
<p>                               25 September 1995                    <B>MCOOKIE(1)</B><br />
</PRE></p>
]]></content:encoded>
					
					<wfw:commentRss>https://manpageaday.wordpress.com/2011/05/08/mcookie-2/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">187</post-id>
		<media:content url="https://1.gravatar.com/avatar/7e5a914fa78c2f8cff1b5a3a1e56626bd1af981cea33e799a05a752770013ffc?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">manpageaday</media:title>
		</media:content>
	</item>
		<item>
		<title>grn</title>
		<link>https://manpageaday.wordpress.com/2011/05/07/grn/</link>
					<comments>https://manpageaday.wordpress.com/2011/05/07/grn/#respond</comments>
		
		<dc:creator><![CDATA[Ryan Gooler]]></dc:creator>
		<pubDate>Sat, 07 May 2011 06:14:42 +0000</pubDate>
				<category><![CDATA[Uncategorized]]></category>
		<guid isPermaLink="false">http://manpageaday.wordpress.com/?p=185</guid>

					<description><![CDATA[SYNOPSIS grn [ -Cv ] [ -Tdev ] [ -Mdir ] [ -Fdir ] [ file&#8230; ] It is possible to have whitespace between a command line option and its parameter. DESCRIPTION grn is a preprocessor for including gremlin pictures in groff input. grn writes to standard output, processing only input lines between two that [&#8230;]]]></description>
										<content:encoded><![CDATA[<p><PRE><br />
<!-- Manpage converted by man2html 3.0.1 --><br />
SYNOPSIS<br />
       grn [ -Cv ] [ -Tdev ] [ -Mdir ] [ -Fdir ] [ file&#8230; ]</p>
<p>       It is possible to have whitespace between a command line option and its<br />
       parameter.</p>
<p>DESCRIPTION<br />
       grn is a preprocessor for including gremlin pictures  in  groff  input.<br />
       grn  writes to standard output, processing only input lines between two<br />
       that start with .GS and .GE.  Those lines  must  contain  grn  commands<br />
       (see below).  These commands request a gremlin file, and the picture in<br />
       that file is converted and placed in the troff input stream.   The  .GS<br />
       request  may be followed by a C, L, or R to center, left, or right jus-<br />
       tify the whole gremlin picture (default justification is  center).   If<br />
       no  file  is  mentioned, the standard input is read.  At the end of the<br />
       picture, the position on the page is the bottom of the gremlin picture.<br />
       If the grn entry is ended with .GF instead of .GE, the position is left<br />
       at the top of the picture.</p>
<p>       Please note that currently only the -me macro package has  support  for<br />
       .GS, .GE, and .GF.</p>
<p>       The following command-line options are understood:</p>
<p>       -Tdev  Prepare  output for printer dev.  The default device is ps.  See<br />
              <B>groff(1)</B> for acceptable devices.</p>
<p>       -Mdir  Prepend dir to the default search path for gremlin  files.   The<br />
              default  path is (in that order) the current directory, the home<br />
              directory, /usr/lib/groff/site-tmac, /usr/share/groff/site-tmac,<br />
              and /usr/share/groff/1.18.1/tmac.</p>
<p>       -Fdir  Search  dir  for subdirectories devname (name is the name of the<br />
              device) for the DESC file before the  default  font  directories<br />
              /usr/share/groff/site-font,   /usr/share/groff/1.18.1/font,  and<br />
              /usr/lib/font.</p>
<p>       -C     Recognize .GS and .GE (resp.  .GF) even when followed by a char-<br />
              acter other than space or newline.</p>
<p>       -v     Print the version number.</p>
<p>GRN COMMANDS<br />
       Each input line between .GS and .GE may have one grn command.  Commands<br />
       consist of one or two strings  separated  by  white  space,  the  first<br />
       string  being  the command and the second its operand.  Commands may be<br />
       upper or lower case and abbreviated down to one character.</p>
<p>       Commands that affect  a  picture&#8217;s  environment  (those  listed  before<br />
       default,  see  below)  are  only in effect for the current picture: The<br />
       environment is reinitialized to the defaults at the start of  the  next<br />
       picture.  The commands are as follows:</p>
<p>       l f<br />
       stipple f<br />
              Set the stipple font to troff&#8217;s stipple font f (name or number).<br />
              The  command  stipple may be abbreviated down as far as `st&#8217; (to<br />
              avoid confusion with special).  There is no default for stipples<br />
              (unless one is set by the default command), and it is invalid to<br />
              include a gremlin picture with  polygons  without  specifying  a<br />
              stipple font.</p>
<p>       x N<br />
       scale N<br />
              Magnify  the  picture (in addition to any default magnification)<br />
              by N, a floating point number larger  than  zero.   The  command<br />
              scale may be abbreviated down to `sc&#8217;.</p>
<p>       narrow N<br />
       medium N<br />
       thick N<br />
              Set  the  thickness of gremlin&#8217;s narrow (resp. medium and thick)<br />
              lines to N times 0.15pt (this value can be  changed  at  compile<br />
              time).   The  default  is  1.0 (resp. 3.0 and 5.0), which corre-<br />
              sponds to 0.15pt (resp. 0.45pt and 0.75pt).  A  thickness  value<br />
              of zero selects the smallest available line thickness.  Negative<br />
              values cause the line thickness to be proportional to  the  cur-<br />
              rent point size.</p>
<p>       pointscale &lt;off/on&gt;<br />
              Scale  text  to  match  the  picture.   Gremlin  text is usually<br />
              printed  in  the  point  size  specified   with   the   commands<br />
              1, 2, 3, or 4  regardless of any scaling factors in the picture.<br />
              Setting pointscale will cause the point sizes to scale with  the<br />
              picture  (within troff&#8217;s limitations, of course).  An operand of<br />
              anything but off will turn text scaling on.</p>
<p>       default<br />
              Reset the picture environment defaults to the  settings  in  the<br />
              current picture.  This is meant to be used as a global parameter<br />
              setting mechanism at the beginning of the troff input file,  but<br />
              can be used at any time to reset the default settings.</p>
<p>       width N<br />
              Forces  the  picture  to  be  N inches wide.  This overrides any<br />
              scaling factors present in  the  same  picture.   `width  0&#8242;  is<br />
              ignored.</p>
<p>       height N<br />
              Forces  picture  to  be  N inches high, overriding other scaling<br />
              factors.  If both `width&#8217; and `height&#8217; are specified the tighter<br />
              constraint  will determine the scale of the picture.  Height and<br />
              width commands are not saved with a default command.  They will,<br />
              however, affect point size scaling if that option is set.</p>
<p>       at the beginning of a line).  Thus, it is possible  to  have  equations<br />
       within  a  gremlin  figure by including in the gremlin file eqn expres-<br />
       sions enclosed by previously defined delimiters (e.g.  $$).</p>
<p>       When using grn along with other preprocessors, it is best  to  run  tbl<br />
       before  grn,  pic,  and/or  ideal to avoid overworking tbl.  Eqn should<br />
       always be run last.</p>
<p>       A picture is considered an entity, but that  doesn&#8217;t  stop  troff  from<br />
       trying  to  break it up if it falls off the end of a page.  Placing the<br />
       picture between `keeps&#8217; in -me macros will ensure proper placement.</p>
<p>       grn uses troff&#8217;s number registers g1 through g9 and sets  registers  g1<br />
       and  g2 to the width and height of the gremlin figure (in device units)<br />
       before entering the .GS request (this is for those who want to  rewrite<br />
       these macros).</p>
<p>GREMLIN FILE FORMAT<br />
       There exist two distinct gremlin file formats, the original format from<br />
       the AED graphic terminal version, and  the  SUN  or  X11  version.   An<br />
       extension  to  the SUN/X11 version allowing reference points with nega-<br />
       tive coordinates is not compatible with the AED version.  As long as  a<br />
       gremlin  file does not contain negative coordinates, either format will<br />
       be read correctly by either version of gremlin or grn.  The other  dif-<br />
       ference  to  the SUN/X11 format is the use of names for picture objects<br />
       (e.g., POLYGON, CURVE) instead of numbers.  Files representing the same<br />
       picture are shown in Table 1 in each format.</p>
<p>                        sungremlinfile        gremlinfile<br />
                        0 240.00 128.00       0 240.00 128.00<br />
                        CENTCENT              2<br />
                        240.00 128.00         240.00 128.00<br />
                        185.00 120.00         185.00 120.00<br />
                        240.00 120.00         240.00 120.00<br />
                        296.00 120.00         296.00 120.00<br />
                        *                     -1.00 -1.00<br />
                        2 3                   2 3<br />
                        10 A Triangle         10 A Triangle<br />
                        POLYGON               6<br />
                        224.00 416.00         224.00 416.00<br />
                        96.00 160.00          96.00 160.00<br />
                        384.00 160.00         384.00 160.00<br />
                        *                     -1.00 -1.00<br />
                        5 1                   5 1<br />
                        0                     0<br />
                        -1                    -1</p>
<p>                               Table 1. File examples</p>
<p>       o      The  first  line of each gremlin file contains either the string<br />
       o      The rest of the file consists of zero or more element specifica-<br />
              tions.   After the last element specification is a line contain-<br />
              ing the string &#8220;-1&#8221;.</p>
<p>       o      Lines longer than 127 characters are chopped to this limit.</p>
<p>ELEMENT SPECIFICATIONS<br />
       o      The first line of each element contains a single decimal  number<br />
              giving  the  type of the element (AED version) or its ASCII name<br />
              (SUN/X11 version).  See Table 2.</p>
<p>                      gremlin File Format &#8211; Object Type Specification</p>
<p>                  AED Number   SUN/X11 Name           Description<br />
                       0       BOTLEFT        bottom-left-justified text<br />
                       1       BOTRIGHT       bottom-right-justified text<br />
                       2       CENTCENT       center-justified text<br />
                       3       VECTOR         vector<br />
                       4       ARC            arc<br />
                       5       CURVE          curve<br />
                       6       POLYGON        polygon<br />
                       7       BSPLINE        b-spline<br />
                       8       BEZIER         Bezier<br />
                      10       TOPLEFT        top-left-justified text<br />
                      11       TOPCENT        top-center-justified text<br />
                      12       TOPRIGHT       top-right-justified text<br />
                      13       CENTLEFT       left-center-justified text<br />
                      14       CENTRIGHT      right-center-justified text<br />
                      15       BOTCENT        bottom-center-justified text</p>
<p>                                          Table 2.<br />
                            Type Specifications in gremlin Files</p>
<p>       o      After the object type comes a variable  number  of  lines,  each<br />
              specifying  a point used to display the element.  Each line con-<br />
              tains an x-coordinate and a y-coordinate in floating point  for-<br />
              mat, separated by spaces.  The list of points is terminated by a<br />
              line containing the string &#8220;-1.0 -1.0&#8221; (AED version) or a sin-<br />
              gle asterisk, &#8220;*&#8221; (SUN/X11 version).</p>
<p>       o      After  the  points  comes  a line containing two decimal values,<br />
              giving the brush and size for the element.  The brush determines<br />
              the  style  in  which  things are drawn.  For vectors, arcs, and<br />
              curves there are six legal brush values:</p>
<p>                              1 &#8211;       thin dotted lines<br />
                              2 &#8211;       thin dot-dashed lines<br />
                              3 &#8211;       thick solid lines<br />
                              4 &#8211;       thin dashed lines</p>
<p>              is really just a starting font: The text string can contain for-<br />
              matting sequences like &#8220;\fI&#8221; or &#8220;\d&#8221; which  may  change  the<br />
              font  (as  well  as  do  many other things).  For text, the size<br />
              field is a decimal value between 1 and 4.  It selects  the  size<br />
              of the font in which the text will be drawn.  For polygons, this<br />
              size field is interpreted as a stipple number to fill the  poly-<br />
              gon  with.   The  number is used to index into a stipple font at<br />
              print time.</p>
<p>       o      The last line of each element contains a decimal  number  and  a<br />
              string  of  characters, separated by a single space.  The number<br />
              is a count of the number of  characters  in  the  string.   This<br />
              information  is  only  used  for text elements, and contains the<br />
              text string.  There can be spaces inside the  text.   For  arcs,<br />
              curves,  and  vectors,  this  line  of  the element contains the<br />
              string &#8220;0&#8221;.</p>
<p>NOTES ON COORDINATES<br />
       gremlin was designed for AEDs, and  its  coordinates  reflect  the  AED<br />
       coordinate  space.   For  vertical pictures, x-values range 116 to 511,<br />
       and y-values from 0 to 483.  For horizontal  pictures,  x-values  range<br />
       from  0  to 511 and y-values range from 0 to 367.  Although you needn&#8217;t<br />
       absolutely stick to this range, you&#8217;ll get best results if you at least<br />
       stay  in this vicinity.  Also, point lists are terminated by a point of<br />
       (-1, -1), so you shouldn&#8217;t  ever  use  negative  coordinates.   gremlin<br />
       writes  out  coordinates  using  format &#8220;%f1.2&#8221;; it&#8217;s probably a good<br />
       idea to use the same format if you want to modify the grn code.</p>
<p>NOTES ON SUN/X11 COORDINATES<br />
       There is no longer a restriction on the range of  coordinates  used  to<br />
       create  objects in the SUN/X11 version of gremlin.  However, files with<br />
       negative coordinates will cause problems if displayed on the AED.</p>
<p>FILES<br />
       /usr/share/groff/1.18.1/font/devname/DESC<br />
              Device description file for device name.</p>
<p>SEE ALSO<br />
       <B>gremlin(1)</B>, <B>groff(1)</B>, <B>pic(1)</B>, <B>ideal(1)</B></p>
<p>HISTORY<br />
       David Slattengren and Barry Roitblat wrote the original Berkeley grn.</p>
<p>       Daniel Senderowicz and Werner Lemberg modified it for groff.</p>
<p>Groff Version 1.18.1             05 March 2005                          <B>GRN(1)</B><br />
</PRE></p>
]]></content:encoded>
					
					<wfw:commentRss>https://manpageaday.wordpress.com/2011/05/07/grn/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">185</post-id>
		<media:content url="https://1.gravatar.com/avatar/7e5a914fa78c2f8cff1b5a3a1e56626bd1af981cea33e799a05a752770013ffc?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">manpageaday</media:title>
		</media:content>
	</item>
		<item>
		<title>git-reset</title>
		<link>https://manpageaday.wordpress.com/2011/05/06/git-reset/</link>
					<comments>https://manpageaday.wordpress.com/2011/05/06/git-reset/#respond</comments>
		
		<dc:creator><![CDATA[Ryan Gooler]]></dc:creator>
		<pubDate>Fri, 06 May 2011 06:14:40 +0000</pubDate>
				<category><![CDATA[Uncategorized]]></category>
		<guid isPermaLink="false">http://manpageaday.wordpress.com/?p=183</guid>

					<description><![CDATA[SYNOPSIS git reset [&#8211;mixed &#124; &#8211;soft &#124; &#8211;hard] [-q] [&#60;commit&#62;] git reset [-q] [&#60;commit&#62;] [&#8211;] &#60;paths&#62;&#8230; DESCRIPTION Sets the current head to the specified commit and optionally resets the index and working tree to match. This command is useful if you notice some small error in a recent commit (or set of commits) and want [&#8230;]]]></description>
										<content:encoded><![CDATA[<p><PRE><br />
<!-- Manpage converted by man2html 3.0.1 --><br />
SYNOPSIS<br />
           git reset [&#8211;mixed | &#8211;soft | &#8211;hard] [-q] [&lt;commit&gt;]<br />
           git reset [-q] [&lt;commit&gt;] [&#8211;] &lt;paths&gt;&#8230;</p>
<p>DESCRIPTION<br />
       Sets the current head to the specified commit and optionally resets the<br />
       index and working tree to match.</p>
<p>       This command is useful if you notice some small error in a recent<br />
       commit (or set of commits) and want to redo that part without showing<br />
       the undo in the history.</p>
<p>       If you want to undo a commit other than the latest on a branch, git-<br />
       <B>revert(1)</B> is your friend.</p>
<p>       The second form with paths is used to revert selected paths in the<br />
       index from a given commit, without moving HEAD.</p>
<p>OPTIONS<br />
       &#8211;mixed<br />
           Resets the index but not the working tree (i.e., the changed files<br />
           are preserved but not marked for commit) and reports what has not<br />
           been updated. This is the default action.</p>
<p>       &#8211;soft<br />
           Does not touch the index file nor the working tree at all, but<br />
           requires them to be in a good order. This leaves all your changed<br />
           files &#8220;Changes to be committed&#8221;, as <B>git-status(1)</B> would put it.</p>
<p>       &#8211;hard<br />
           Matches the working tree and index to that of the tree being<br />
           switched to. Any changes to tracked files in the working tree since<br />
           &lt;commit&gt; are lost.</p>
<p>       -q<br />
           Be quiet, only report errors.</p>
<p>       &lt;commit&gt;<br />
           Commit to make the current HEAD. If not given defaults to HEAD.</p>
<p>EXAMPLES<br />
       Undo a commit and redo</p>
<p>               $ git commit &#8230;<br />
               $ git reset &#8211;soft HEAD^      <B>fB(1)</B>fR<br />
               $ edit                        <B>fB(2)</B>fR<br />
               $ git commit -a -c ORIG_HEAD  <B>fB(3)</B>fR<br />
           sp fB1. fRThis is most often done when you remembered what you just<br />
           committed is incomplete, or you misspelled your commit message, or<br />
           both. Leaves working tree as it was before &#8220;reset&#8221;.  br fB2. fRMake<br />
           corrections to working tree files.  br fB3. fR&#8221;reset&#8221; copies the</p>
<p>       Undo a commit, making it a topic branch</p>
<p>               $ git branch topic/wip     <B>fB(1)</B>fR<br />
               $ git reset &#8211;hard HEAD~3  <B>fB(2)</B>fR<br />
               $ git checkout topic/wip   <B>fB(3)</B>fR<br />
           sp fB1. fRYou have made some commits, but realize they were<br />
           premature to be in the &#8220;master&#8221; branch. You want to continue<br />
           polishing them in a topic branch, so create &#8220;topic/wip&#8221; branch off<br />
           of the current HEAD.  br fB2. fRRewind the master branch to get rid<br />
           of those three commits.  br fB3. fRSwitch to &#8220;topic/wip&#8221; branch and<br />
           keep working.  br</p>
<p>       Undo add</p>
<p>               $ edit                                     <B>fB(1)</B>fR<br />
               $ git add frotz.c filfre.c<br />
               $ mailx                                    <B>fB(2)</B>fR<br />
               $ git reset                                <B>fB(3)</B>fR<br />
               $ git pull git://info.example.com/ nitfol  <B>fB(4)</B>fR<br />
           sp fB1. fRYou are happily working on something, and find the<br />
           changes in these files are in good order. You do not want to see<br />
           them when you run &#8220;git diff&#8221;, because you plan to work on other<br />
           files and changes with these files are distracting.  br fB2.<br />
           fRSomebody asks you to pull, and the changes sounds worthy of<br />
           merging.  br fB3. fRHowever, you already dirtied the index (i.e.<br />
           your index does not match the HEAD commit). But you know the pull<br />
           you are going to make does not affect frotz.c nor filfre.c, so you<br />
           revert the index changes for these two files. Your changes in<br />
           working tree remain there.  br fB4. fRThen you can pull and merge,<br />
           leaving frotz.c and filfre.c changes still in the working tree.  br</p>
<p>       Undo a merge or pull</p>
<p>               $ git pull                         <B>fB(1)</B>fR<br />
               Auto-merging nitfol<br />
               CONFLICT (content): Merge conflict in nitfol<br />
               Automatic merge failed/prevented; fix up by hand<br />
               $ git reset &#8211;hard                 <B>fB(2)</B>fR<br />
               $ git pull . topic/branch          <B>fB(3)</B>fR<br />
               Updating from 41223&#8230; to 13134&#8230;<br />
               Fast forward<br />
               $ git reset &#8211;hard ORIG_HEAD       <B>fB(4)</B>fR<br />
           sp fB1. fRTry to update from the upstream resulted in a lot of<br />
           conflicts; you were not ready to spend a lot of time merging right<br />
           now, so you decide to do that later.  br fB2. fR&#8221;pull&#8221; has not made<br />
           merge commit, so &#8220;git reset &#8211;hard&#8221; which is a synonym for &#8220;git<br />
           reset &#8211;hard HEAD&#8221; clears the mess from the index file and the<br />
           working tree.  br fB3. fRMerge a topic branch into the current<br />
           branch, which resulted in a fast forward.  br fB4. fRBut you<br />
           decided that the topic branch is not ready for public consumption<br />
           yet. &#8220;pull&#8221; or &#8220;merge&#8221; always leaves the original tip of the<br />
           current branch in ORIG_HEAD, so resetting hard to it brings your<br />
               $ git commit ;# commit with real log<br />
               $ git checkout feature<br />
               $ git reset &#8211;soft HEAD^ ;# go back to WIP state  <B>fB(2)</B>fR<br />
               $ git reset                                       <B>fB(3)</B>fR<br />
           sp fB1. fRThis commit will get blown away so a throw-away log<br />
           message is OK.  br fB2. fRThis removes the WIP commit from the<br />
           commit history, and sets your working tree to the state just before<br />
           you made that snapshot.  br fB3. fRAt this point the index file<br />
           still has all the WIP changes you committed as snapshot WIP. This<br />
           updates the index to show your WIP files as uncommitted.  br</p>
<p>       Reset a single file in the index<br />
           Suppose you have added a file to your index, but later decide you<br />
           do not want to add it to your commit. You can remove the file from<br />
           the index while keeping your changes with git reset.</p>
<p>               $ git reset &#8212; frotz.c                      <B>fB(1)</B>fR<br />
               $ git commit -m &#8220;Commit files in index&#8221;     <B>fB(2)</B>fR<br />
               $ git add frotz.c                           <B>fB(3)</B>fR<br />
           sp fB1. fRThis removes the file from the index while keeping it in<br />
           the working directory.  br fB2. fRThis commits all other changes in<br />
           the index.  br fB3. fRAdds the file to the index again.  br</p>
<p>AUTHOR<br />
       Written by Junio C Hamano &lt;gitster@pobox.com[1]&gt; and Linus Torvalds<br />
       &lt;torvalds@osdl.org[2]&gt;</p>
<p>DOCUMENTATION<br />
       Documentation by Junio C Hamano and the git-list<br />
       &lt;git@vger.kernel.org[3]&gt;.</p>
<p>GIT<br />
       Part of the <B>git(1)</B> suite</p>
<p>NOTES<br />
        1. gitster@pobox.com<br />
           mailto:gitster@pobox.com</p>
<p>        2. torvalds@osdl.org<br />
           mailto:torvalds@osdl.org</p>
<p>        3. git@vger.kernel.org<br />
           mailto:git@vger.kernel.org</p>
<p>Git 1.5.6.5                       09/24/2010                      <B>GIT-RESET(1)</B><br />
</PRE></p>
]]></content:encoded>
					
					<wfw:commentRss>https://manpageaday.wordpress.com/2011/05/06/git-reset/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">183</post-id>
		<media:content url="https://1.gravatar.com/avatar/7e5a914fa78c2f8cff1b5a3a1e56626bd1af981cea33e799a05a752770013ffc?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">manpageaday</media:title>
		</media:content>
	</item>
		<item>
		<title>volname</title>
		<link>https://manpageaday.wordpress.com/2011/05/05/volname/</link>
					<comments>https://manpageaday.wordpress.com/2011/05/05/volname/#respond</comments>
		
		<dc:creator><![CDATA[Ryan Gooler]]></dc:creator>
		<pubDate>Thu, 05 May 2011 06:14:36 +0000</pubDate>
				<category><![CDATA[Uncategorized]]></category>
		<guid isPermaLink="false">http://manpageaday.wordpress.com/?p=181</guid>

					<description><![CDATA[SYNOPSIS volname [&#60;device-file&#62;] DESCRIPTION Volname returns the volume name for a device formatted with an ISO-9660 file system, typically a CD-ROM. It also works with normal files that contain a ISO-9660 file system. The file name can be specified on the command line. If omitted, it defaults to /dev/cdrom. AUTHOR Volname was written by Jeff [&#8230;]]]></description>
										<content:encoded><![CDATA[<p><PRE><br />
<!-- Manpage converted by man2html 3.0.1 --><br />
SYNOPSIS<br />
       volname [&lt;device-file&gt;]</p>
<p>DESCRIPTION<br />
       Volname returns the volume name for a device formatted with an ISO-9660<br />
       file system, typically a CD-ROM. It also works with normal  files  that<br />
       contain a ISO-9660 file system.</p>
<p>       The  file  name  can  be specified on the command line.  If omitted, it<br />
       defaults to /dev/cdrom.</p>
<p>AUTHOR<br />
       Volname was written by Jeff Tranter (tranter@pobox.com) and is released<br />
       under  the  conditions  of the GNU General Public License. See the file<br />
       COPYING and notes in the source code for details.</p>
<p>SEE ALSO<br />
       <B>eject(1)</B></p>
<p>Linux                             13 Nov 2004                       <B>VOLNAME(1)</B><br />
</PRE></p>
]]></content:encoded>
					
					<wfw:commentRss>https://manpageaday.wordpress.com/2011/05/05/volname/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">181</post-id>
		<media:content url="https://1.gravatar.com/avatar/7e5a914fa78c2f8cff1b5a3a1e56626bd1af981cea33e799a05a752770013ffc?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">manpageaday</media:title>
		</media:content>
	</item>
		<item>
		<title>screen</title>
		<link>https://manpageaday.wordpress.com/2011/05/04/screen/</link>
					<comments>https://manpageaday.wordpress.com/2011/05/04/screen/#respond</comments>
		
		<dc:creator><![CDATA[Ryan Gooler]]></dc:creator>
		<pubDate>Wed, 04 May 2011 06:14:37 +0000</pubDate>
				<category><![CDATA[Uncategorized]]></category>
		<guid isPermaLink="false">http://manpageaday.wordpress.com/?p=179</guid>

					<description><![CDATA[SYNOPSIS screen [ -options ] [ cmd [ args ] ] screen -r [[pid.]tty[.host]] screen -r sessionowner/[[pid.]tty[.host]] DESCRIPTION Screen is a full-screen window manager that multiplexes a physical ter- minal between several processes (typically interactive shells). Each virtual terminal provides the functions of a DEC VT100 terminal and, in addition, several control functions from the [&#8230;]]]></description>
										<content:encoded><![CDATA[<p><PRE><br />
<!-- Manpage converted by man2html 3.0.1 --></p>
<p>SYNOPSIS<br />
       screen [ -options ] [ cmd [ args ] ]<br />
       screen -r [[pid.]tty[.host]]<br />
       screen -r sessionowner/[[pid.]tty[.host]]</p>
<p>DESCRIPTION<br />
       Screen is a full-screen window manager that multiplexes a physical ter-<br />
       minal between several processes (typically interactive  shells).   Each<br />
       virtual terminal provides the functions of a DEC VT100 terminal and, in<br />
       addition, several control functions from the ISO 6429  (ECMA  48,  ANSI<br />
       X3.64)  and ISO 2022 standards (e.g. insert/delete line and support for<br />
       multiple character sets).  There is a  scrollback  history  buffer  for<br />
       each virtual terminal and a copy-and-paste mechanism that allows moving<br />
       text regions between windows.</p>
<p>       When screen is called, it creates a single window with a  shell  in  it<br />
       (or  the  specified  command) and then gets out of your way so that you<br />
       can use the program as you normally would.  Then, at any time, you  can<br />
       create new (full-screen) windows with other programs in them (including<br />
       more shells), kill existing windows, view a list of windows, turn  out-<br />
       put  logging  on and off, copy-and-paste text between windows, view the<br />
       scrollback history, switch between windows in whatever manner you wish,<br />
       etc.  All  windows  run  their  programs completely independent of each<br />
       other. Programs continue to run when their window is currently not vis-<br />
       ible and even when the whole screen session is detached from the user&#8217;s<br />
       terminal.  When a program terminates, screen (per  default)  kills  the<br />
       window  that  contained  it.  If this window was in the foreground, the<br />
       display switches to the previous  window;  if  none  are  left,  screen<br />
       exits.</p>
<p>       Everything  you type is sent to the program running in the current win-<br />
       dow.  The only exception to this is the one keystroke that is  used  to<br />
       initiate  a  command  to  the window manager.  By default, each command<br />
       begins with a control-a (abbreviated C-a from now on), and is  followed<br />
       by one other keystroke.  The command character and all the key bindings<br />
       can be fully customized to be anything you like, though they are always<br />
       two characters in length.</p>
<p>       Screen does not understand the prefix &#8220;C-&#8221; to mean control.  Please use<br />
       the caret notation (&#8220;^A&#8221; instead of &#8220;C-a&#8221;) as  arguments  to  e.g.  the<br />
       escape  command  or  the -e option.  Screen will also print out control<br />
       characters in caret notation.</p>
<p>       The standard way to create a new window is to type &#8220;C-a c&#8221;.  This  cre-<br />
       ates  a  new window running a shell and switches to that window immedi-<br />
       ately, regardless of the state of the process running  in  the  current<br />
       window.   Similarly,  you can create a new window with a custom command<br />
       in it by first binding the command to a keystroke  (in  your  .screenrc</p>
<p>       If &#8220;/var/run/utmp&#8221; is writable by screen, an appropriate record will be<br />
       written  to  this  file for each window, and removed when the window is<br />
       terminated.  This is useful for working with &#8220;talk&#8221;,  &#8220;script&#8221;,  &#8220;shut-<br />
       down&#8221;,  &#8220;rsend&#8221;,  &#8220;sccs&#8221;  and  other similar programs that use the utmp<br />
       file to determine who you are. As long as screen is active on your ter-<br />
       minal,  the  terminal&#8217;s  own  record is removed from the utmp file. See<br />
       also &#8220;C-a L&#8221;.</p>
<p>GETTING STARTED<br />
       Before you begin to use screen you&#8217;ll need to make sure you  have  cor-<br />
       rectly  selected  your  terminal  type, just as you would for any other<br />
       termcap/terminfo program.  (You can do this by using tset for example.)</p>
<p>       If  you&#8217;re  impatient  and want to get started without doing a lot more<br />
       reading, you should remember this one command:  &#8220;C-a ?&#8221;.  Typing  these<br />
       two characters will display a list of the available screen commands and<br />
       their bindings. Each keystroke is discussed in the section &#8220;DEFAULT KEY<br />
       BINDINGS&#8221;.  The  manual section &#8220;CUSTOMIZATION&#8221; deals with the contents<br />
       of your .screenrc.</p>
<p>       If your terminal is a &#8220;true&#8221; auto-margin terminal (it doesn&#8217;t allow the<br />
       last position on the screen to be updated without scrolling the screen)<br />
       consider using a version of your terminal&#8217;s termcap that has  automatic<br />
       margins  turned off. This will ensure an accurate and optimal update of<br />
       the screen in all circumstances. Most terminals nowadays  have  &#8220;magic&#8221;<br />
       margins  (automatic margins plus usable last column). This is the VT100<br />
       style type and perfectly suited for screen.  If all  you&#8217;ve  got  is  a<br />
       &#8220;true&#8221;  auto-margin  terminal  screen  will  be  content to use it, but<br />
       updating a character put into the last position on the screen  may  not<br />
       be  possible  until the screen scrolls or the character is moved into a<br />
       safe position in some other way. This delay can be shortened by using a<br />
       terminal with insert-character capability.</p>
<p>COMMAND-LINE OPTIONS<br />
       Screen has the following command-line options:</p>
<p>       -a   include all capabilities (with some minor exceptions) in each win-<br />
            dow&#8217;s termcap, even if screen must redraw parts of the display  in<br />
            order to implement a function.</p>
<p>       -A   Adapt  the  sizes of all windows to the size of the current termi-<br />
            nal.  By default, screen tries to restore  its  old  window  sizes<br />
            when  attaching  to  resizable  terminals  (those with &#8220;WS&#8221; in its<br />
            description, e.g. suncmd or some xterm).</p>
<p>       -c file<br />
            override the default configuration file from &#8220;$HOME/.screenrc&#8221;  to</p>
<p>       -d -RR  Reattach  a  session  and if necessary detach or create it. Use<br />
               the first session if more than one session is available.</p>
<p>       -D -r   Reattach a session. If necessary  detach  and  logout  remotely<br />
               first.</p>
<p>       -D -R   Attach here and now. In detail this means: If a session is run-<br />
               ning, then reattach. If necessary detach  and  logout  remotely<br />
               first.   If  it  was not running create it and notify the user.<br />
               This is the author&#8217;s favorite.</p>
<p>       -D -RR  Attach here and now. Whatever that means, just do it.</p>
<p>            Note: It is always a good idea to check the status  of  your  ses-<br />
            sions by means of &#8220;screen -list&#8221;.</p>
<p>       -e xy<br />
            specifies the command character to be x and the character generat-<br />
            ing a literal command character to y (when typed after the command<br />
            character).   The default is &#8220;C-a&#8221; and `a&#8217;, which can be specified<br />
            as &#8220;-e^Aa&#8221;.  When creating a screen session, this option sets  the<br />
            default  command character. In a multiuser session all users added<br />
            will start off with this command character. But when attaching  to<br />
            an  already  running session, this option changes only the command<br />
            character of the attaching user.  This  option  is  equivalent  to<br />
            either the commands &#8220;defescape&#8221; or &#8220;escape&#8221; respectively.</p>
<p>       -f, -fn, and -fa<br />
            turns  flow-control  on, off, or &#8220;automatic switching mode&#8221;.  This<br />
            can also be defined through the &#8220;defflow&#8221; .screenrc command.</p>
<p>       -h num<br />
            Specifies the history scrollback buffer to be num lines high.</p>
<p>       -i   will cause the interrupt key (usually C-c) to interrupt  the  dis-<br />
            play  immediately  when  flow-control  is  on.   See the &#8220;defflow&#8221;<br />
            .screenrc command for details.  The use of this option is discour-<br />
            aged.</p>
<p>       -l and -ln<br />
            turns login mode on or off (for /var/run/utmp updating).  This can<br />
            also be defined through the &#8220;deflogin&#8221; .screenrc command.</p>
<p>       -ls and -list<br />
            does not start screen, but prints a list of  pid.tty.host  strings<br />
            and  creation  timestamps  identifying your screen sessions.  Ses-<br />
            sions marked `detached&#8217; can be resumed  with  &#8220;screen  -r&#8221;.  Those<br />
            marked  `attached&#8217; are running and have a controlling terminal. If<br />
            the session runs in multiuser mode, it is marked `multi&#8217;. Sessions<br />
            marked  as  `unreachable&#8217;  either  live on a different host or are<br />
            `dead&#8217;.  An unreachable session is considered dead, when its  name</p>
<p>       -d -m   Start screen in &#8220;detached&#8221; mode. This creates a new session but<br />
               doesn&#8217;t  attach  to  it.  This  is  useful  for  system startup<br />
               scripts.</p>
<p>       -D -m   This also starts screen in &#8220;detached&#8221; mode, but doesn&#8217;t fork  a<br />
               new process. The command exits if the session terminates.</p>
<p>       -O   selects  a  more optimal output mode for your terminal rather than<br />
            true VT100 emulation (only affects auto-margin  terminals  without<br />
            `LP&#8217;).   This can also be set in your .screenrc by specifying `OP&#8217;<br />
            in a &#8220;termcap&#8221; command.</p>
<p>       -p number_or_name<br />
            Preselect a window. This is useful when you want to reattach to  a<br />
            specific  window or you want to send a command via the &#8220;-X&#8221; option<br />
            to a specific window. As with screen&#8217;s select command, &#8220;-&#8221; selects<br />
            the  blank  window.  As a special case for reattach, &#8220;=&#8221; brings up<br />
            the windowlist on the blank window.</p>
<p>       -q   Suppress printing of error messages. In combination with &#8220;-ls&#8221; the<br />
            exit  value  is  as  follows: 9 indicates a directory without ses-<br />
            sions. 10 indicates a directory with running  but  not  attachable<br />
            sessions.  11 (or more) indicates 1 (or more) usable sessions.  In<br />
            combination with &#8220;-r&#8221; the exit value is as follows:  10  indicates<br />
            that  there  is  no session to resume. 12 (or more) indicates that<br />
            there are 2 (or more) sessions to resume and  you  should  specify<br />
            which one to choose.  In all other cases &#8220;-q&#8221; has no effect.</p>
<p>       -r [pid.tty.host]<br />
       -r sessionowner/[pid.tty.host]<br />
            resumes  a detached screen session.  No other options (except com-<br />
            binations with -d/-D) may be specified, though an optional  prefix<br />
            of  [pid.]tty.host  may  be needed to distinguish between multiple<br />
            detached screen sessions.  The second form is used to  connect  to<br />
            another  user&#8217;s  screen session which runs in multiuser mode. This<br />
            indicates that screen should look for sessions in  another  user&#8217;s<br />
            directory. This requires setuid-root.</p>
<p>       -R   attempts  to  resume  the  youngest  (in  terms  of creation time)<br />
            detached screen session it finds.  If successful, all  other  com-<br />
            mand-line  options  are  ignored.   If no detached session exists,<br />
            starts a new session using the specified options, just  as  if  -R<br />
            had  not been specified. The option is set by default if screen is<br />
            run as a login-shell (actually screen uses &#8220;-xRR&#8221; in  that  case).<br />
            For  combinations  with  the  -d/-D option see there.  Note: Time-<br />
            based session selection is a Debian addition.</p>
<p>       -s   sets the default shell to the program specified,  instead  of  the<br />
            value  in  the  environment  variable  $SHELL (or &#8220;/bin/sh&#8221; if not<br />
            defined).  This can also be defined through the &#8220;shell&#8221;  .screenrc<br />
            command.</p>
<p>       -v   Print version number.</p>
<p>       -wipe [match]<br />
            does  the  same  as  &#8220;screen  -ls&#8221;, but removes destroyed sessions<br />
            instead of marking them as `dead&#8217;.  An unreachable session is con-<br />
            sidered  dead,  when its name matches either the name of the local<br />
            host, or the explicitly given parameter, if any.  See the -r  flag<br />
            for a description how to construct matches.</p>
<p>       -x   Attach  to  a  not  detached screen session. (Multi display mode).<br />
            Screen refuses to attach from within itself.  But  when  cascading<br />
            multiple screens, loops are not detected; take care.</p>
<p>       -X   Send  the  specified  command to a running screen session. You can<br />
            use the -d or -r option to tell screen to look only  for  attached<br />
            or  detached  screen sessions. Note that this command doesn&#8217;t work<br />
            if the session is password protected.</p>
<p>DEFAULT KEY BINDINGS<br />
       As mentioned, each screen command consists of a &#8220;C-a&#8221; followed  by  one<br />
       other  character.  For your convenience, all commands that are bound to<br />
       lower-case letters are also bound to their control  character  counter-<br />
       parts (with the exception of &#8220;C-a a&#8221;; see below), thus, &#8220;C-a c&#8221; as well<br />
       as &#8220;C-a C-c&#8221; can be used to create a window.  See  section  &#8220;CUSTOMIZA-<br />
       TION&#8221; for a description of the command.</p>
<p>       The following table shows the default key bindings:</p>
<p>       C-a &#8216;       (select)      Prompt  for a window name or number to switch<br />
                                 to.</p>
<p>       C-a &#8221;       (windowlist -b)<br />
                                 Present a list of all windows for  selection.</p>
<p>       C-a 0       (select 0)<br />
        &#8230;           &#8230;<br />
       C-a 9       (select 9)<br />
       C-a &#8211;       (select -)    Switch  to  window  number  0  &#8211; 9, or to the<br />
                                 blank window.</p>
<p>       C-a tab     (focus)       Switch the input focus to  the  next  region.<br />
                                 See also split, remove, only.</p>
<p>       C-a C-a     (other)       Toggle  to  the  window displayed previously.<br />
                                 Note that this binding defaults to  the  com-<br />
                                 mand  character  typed twice, unless overrid-<br />
                                 den.  For instance, if  you  use  the  option<br />
                                 &#8220;-e]x&#8221;, this command becomes &#8220;]]&#8221;.</p>
<p>       C-a C       (clear)       Clear the screen.</p>
<p>       C-a d<br />
       C-a C-d     (detach)      Detach screen from this terminal.</p>
<p>       C-a D D     (pow_detach)  Detach and logout.</p>
<p>       C-a f<br />
       C-a C-f     (flow)        Toggle flow on, off or auto.</p>
<p>       C-a F       (fit)         Resize the window to the current region size.</p>
<p>       C-a C-g     (vbell)       Toggles screen&#8217;s visual bell mode.</p>
<p>       C-a h       (hardcopy)    Write a hardcopy of the current window to the<br />
                                 file &#8220;hardcopy.n&#8221;.</p>
<p>       C-a H       (log)         Begins/ends logging of the current window  to<br />
                                 the file &#8220;screenlog.n&#8221;.</p>
<p>       C-a i<br />
       C-a C-i     (info)        Show info about this window.</p>
<p>       C-a k<br />
       C-a C-k     (kill)        Destroy current window.</p>
<p>       C-a l<br />
       C-a C-l     (redisplay)   Fully refresh current window.</p>
<p>       C-a L       (login)       Toggle  this  windows  login  slot. Available<br />
                                 only if screen is configured  to  update  the<br />
                                 utmp database.</p>
<p>       C-a m<br />
       C-a C-m     (lastmsg)     Repeat the last message displayed in the mes-<br />
                                 sage line.</p>
<p>       C-a M       (monitor)     Toggles monitoring of the current window.</p>
<p>       C-a space<br />
       C-a n<br />
       C-a C-n     (next)        Switch to the next window.</p>
<p>       C-a N       (number)      Show the number (and title)  of  the  current<br />
                                 window.</p>
<p>       C-a backspace<br />
       C-a h<br />
       C-a p<br />
       C-a C-p     (prev)        Switch to the previous window (opposite of C-<br />
                                 a n).</p>
<p>       C-a S       (split)       Split  the  current region into two new ones.<br />
                                 See also only, remove, focus.</p>
<p>       C-a t<br />
       C-a C-t     (time)        Show system information.</p>
<p>       C-a v       (version)     Display the version and compilation date.</p>
<p>       C-a C-v     (digraph)     Enter digraph.</p>
<p>       C-a w<br />
       C-a C-w     (windows)     Show a list of window.</p>
<p>       C-a W       (width)       Toggle 80/132 columns.</p>
<p>       C-a x<br />
       C-a C-x     (lockscreen)  Lock this terminal.</p>
<p>       C-a X       (remove)      Kill the current  region.   See  also  split,<br />
                                 only, focus.</p>
<p>       C-a z<br />
       C-a C-z     (suspend)     Suspend  screen.   Your  system  must support<br />
                                 BSD-style job-control.</p>
<p>       C-a Z       (reset)       Reset the virtual terminal to its  &#8220;power-on&#8221;<br />
                                 values.</p>
<p>       C-a .       (dumptermcap) Write out a &#8220;.termcap&#8221; file.</p>
<p>       C-a ?       (help)        Show key bindings.</p>
<p>       C-a C-\     (quit)        Kill all windows and terminate screen.</p>
<p>       C-a :       (colon)       Enter command line mode.</p>
<p>       C-a [<br />
       C-a C-[<br />
       C-a esc     (copy)        Enter copy/scrollback mode.</p>
<p>       C-a ]       (paste .)     Write the contents of the paste buffer to the<br />
                                 stdin queue of the current window.</p>
<p>       C-a {<br />
       C-a }       (history)     Copy and paste a previous (command) line.</p>
<p>       C-a &gt;       (writebuf)    Write paste buffer to a file.</p>
<p>       C-a &lt;       (readbuf)     Reads the screen-exchange file into the paste<br />
                                 buffer.</p>
<p>       The &#8220;socket directory&#8221; defaults either to $HOME/.screen  or  simply  to<br />
       /tmp/screens  or  preferably to /var/run/screen chosen at compile-time.<br />
       If screen is installed setuid-root, then the administrator should  com-<br />
       pile  screen  with  an  adequate (not NFS mounted) socket directory. If<br />
       screen is not running setuid-root, the user can specify  any  mode  700<br />
       directory in the environment variable $SCREENDIR.</p>
<p>       When  screen  is  invoked, it executes initialization commands from the<br />
       files &#8220;/etc/screenrc&#8221; and &#8220;.screenrc&#8221; in  the  user&#8217;s  home  directory.<br />
       These  are  the  &#8220;programmer&#8217;s  defaults&#8221; that can be overridden in the<br />
       following ways: for the global screenrc file screen  searches  for  the<br />
       environment  variable  $SYSSCREENRC  (this override feature may be dis-<br />
       abled at compile-time). The user specific screenrc file is searched  in<br />
       $SCREENRC,  then  $HOME/.screenrc.   The  command  line option -c takes<br />
       precedence over the above user screenrc files.</p>
<p>       Commands in these files are used to  set  options,  bind  functions  to<br />
       keys,  and to automatically establish one or more windows at the begin-<br />
       ning of your screen session.  Commands are listed one  per  line,  with<br />
       empty lines being ignored.  A command&#8217;s arguments are separated by tabs<br />
       or spaces, and may be surrounded by single or  double  quotes.   A  `#&#8217;<br />
       turns  the rest of the line into a comment, except in quotes.  Unintel-<br />
       ligible lines are warned about and ignored.  Commands may contain  ref-<br />
       erences  to environment variables. The syntax is the shell-like &#8220;$VAR &#8221;<br />
       or &#8220;${VAR}&#8221;. Note that this causes incompatibility with previous screen<br />
       versions,  as  now the &#8216;$&#8217;-character has to be protected with &#8216;\&#8217; if no<br />
       variable substitution shall be performed. A string in single-quotes  is<br />
       also protected from variable substitution.</p>
<p>       Two  configuration  files are shipped as examples with your screen dis-<br />
       tribution: &#8220;etc/screenrc&#8221; and &#8220;etc/etcscreenrc&#8221;. They contain a  number<br />
       of useful examples for various commands.</p>
<p>       Customization  can  also  be  done &#8216;on-line&#8217;. To enter the command mode<br />
       type `C-a :&#8217;. Note that commands starting  with  &#8220;def&#8221;  change  default<br />
       values, while others change current settings.</p>
<p>       The following commands are available:</p>
<p>       acladd usernames [crypted-pw]<br />
       addacl usernames</p>
<p>       Enable  users to fully access this screen session. Usernames can be one<br />
       user or a comma separated list of users. This command enables to attach<br />
       to  the screen session and performs the equivalent of `aclchg usernames<br />
       +rwx &#8220;#?&#8221;&#8216;.  executed. To add a user with restricted  access,  use  the<br />
       `aclchg&#8217;  command  below.  If an optional second parameter is supplied,<br />
       it should be a crypted password for the named user(s).  `Addacl&#8217;  is  a<br />
       synonym to `acladd&#8217;.  Multi user mode only.</p>
<p>       aclchg usernames permbits list<br />
       chacl usernames permbits list<br />
       dows. Execution permission for the acl commands, `at&#8217; and others should<br />
       also  be  removed  or  the user may be able to regain write permission.<br />
       Rights of the special username nobody cannot be changed (see  the  &#8220;su&#8221;<br />
       command).  `Chacl&#8217; is a synonym to `aclchg&#8217;.  Multi user mode only.</p>
<p>       acldel username</p>
<p>       Remove a user from screen&#8217;s access control list. If currently attached,<br />
       all the user&#8217;s displays are detached from the session. He cannot attach<br />
       again.  Multi user mode only.</p>
<p>       aclgrp username [groupname]</p>
<p>       Creates  groups  of  users that share common access rights. The name of<br />
       the group is the username of the group leader. Each member of the group<br />
       inherits  the  permissions  that  are granted to the group leader. That<br />
       means, if a user fails an access check, another check is made  for  the<br />
       group  leader.   A  user  is  removed from all groups the special value<br />
       &#8220;none&#8221; is used for groupname.  If the second parameter is  omitted  all<br />
       groups the user is in are listed.</p>
<p>       aclumask [[users]+bits |[users]-bits &#8230;. ]<br />
       umask [[users]+bits |[users]-bits &#8230;. ]</p>
<p>       This specifies the access other users have to windows that will be cre-<br />
       ated by the caller of the command.  Users may be no,  one  or  a  comma<br />
       separated list of known usernames. If no users are specified, a list of<br />
       all currently known users is  assumed.   Bits  is  any  combination  of<br />
       access control bits allowed defined with the &#8220;aclchg&#8221; command. The spe-<br />
       cial username &#8220;?&#8221; predefines the access that not yet known  users  will<br />
       be  granted  to any window initially.  The special username &#8220;??&#8221; prede-<br />
       fines the access that not yet known users are granted to  any  command.<br />
       Rights  of  the special username nobody cannot be changed (see the &#8220;su&#8221;<br />
       command).  `Umask&#8217; is a synonym to `aclumask&#8217;.</p>
<p>       activity message</p>
<p>       When any activity occurs in a background window  that  is  being  moni-<br />
       tored, screen displays a notification in the message line.  The notifi-<br />
       cation message can be re-defined by means of  the  &#8220;activity&#8221;  command.<br />
       Each occurrence of `%&#8217; in message is replaced by the number of the win-<br />
       dow in which activity has occurred, and  each  occurrence  of  `^G&#8217;  is<br />
       replaced by the definition for bell in your termcap (usually an audible<br />
       bell).  The default message is</p>
<p>                   &#8216;Activity in window %n&#8217;</p>
<p>       Note that monitoring is off for all windows  by  default,  but  can  be<br />
       altered by use of the &#8220;monitor&#8221; command (C-a M).</p>
<p>       allpartial on|off</p>
<p>       Execute  a  command  at  other  displays  or  windows as if it had been<br />
       entered there.  &#8220;At&#8221; changes the context (the `current window&#8217; or `cur-<br />
       rent display&#8217; setting) of the command. If the first parameter describes<br />
       a non-unique context, the command will be executed multiple  times.  If<br />
       the  first  parameter  is  of the form `identifier*&#8217; then identifier is<br />
       matched against user names.  The command is executed once for each dis-<br />
       play  of  the  selected  user(s). If the first parameter is of the form<br />
       `identifier%&#8217; identifier is  matched  against  displays.  Displays  are<br />
       named  after the ttys they attach. The prefix `/dev/&#8217; or `/dev/tty&#8217; may<br />
       be omitted from the identifier.  If identifier has  a  `#&#8217;  or  nothing<br />
       appended  it  is matched against window numbers and titles. Omitting an<br />
       identifier in front of the `#&#8217;, `*&#8217; or `%&#8217;-character selects all users,<br />
       displays  or  windows because a prefix-match is performed. Note that on<br />
       the affected display(s) a short message will  describe  what  happened.<br />
       Permission  is  checked  for initiator of the &#8220;at&#8221; command, not for the<br />
       owners of the affected display(s).  Note that the &#8216;#&#8217;  character  works<br />
       as  a comment introducer when it is preceded by whitespace. This can be<br />
       escaped by prefixing a &#8216;\&#8217;.  Permission is checked for the initiator of<br />
       the &#8220;at&#8221; command, not for the owners of the affected display(s).<br />
       Caveat: When matching against windows, the command is executed at least<br />
       once per window. Commands that change the internal arrangement of  win-<br />
       dows  (like &#8220;other&#8221;) may be called again. In shared windows the command<br />
       will be repeated for each attached display. Beware, when issuing toggle<br />
       commands  like  &#8220;login&#8221;!  Some commands (e.g. &#8220;process&#8221;) require that a<br />
       display is associated with the target windows.  These commands may  not<br />
       work correctly under &#8220;at&#8221; looping over windows.</p>
<p>       attrcolor attrib [attribute/color-modifier]</p>
<p>       This  command can be used to highlight attributes by changing the color<br />
       of the  text.  If  the  attribute  attrib  is  in  use,  the  specified<br />
       attribute/color  modifier is also applied. If no modifier is given, the<br />
       current one is deleted. See the &#8220;STRING ESCAPES&#8221; chapter for the syntax<br />
       of  the  modifier. Screen understands two pseudo-attributes, &#8220;i&#8221; stands<br />
       for high-intensity foreground color and &#8220;I&#8221;  for  high-intensity  back-<br />
       ground color.</p>
<p>       Examples:</p>
<p>              attrcolor b &#8220;R&#8221;</p>
<p>       Change the color to bright red if bold text is to be printed.</p>
<p>              attrcolor u &#8220;-u b&#8221;</p>
<p>       Use blue text instead of underline.</p>
<p>              attrcolor b &#8220;.I&#8221;</p>
<p>       Use  bright  colors  for  bold  text.  Most  terminal emulators do this<br />
       already.</p>
<p>       has not been written to the terminal. See also &#8220;obuflimit&#8221;.</p>
<p>       backtick id lifespan autorefresh cmd args&#8230;<br />
       backtick id</p>
<p>       Program the backtick command with the numerical id id.  The  output  of<br />
       such  a command is used for substitution of the &#8220;%`&#8221; string escape. The<br />
       specified lifespan is the number of seconds the  output  is  considered<br />
       valid.  After  this  time,  the command is run again if a corresponding<br />
       string escape is encountered.  The autorefresh  parameter  triggers  an<br />
       automatic  refresh  for caption and hardstatus strings after the speci-<br />
       fied number of seconds. Only the last line of output is used  for  sub-<br />
       stitution.<br />
       If both the lifespan and the autorefresh parameters are zero, the back-<br />
       tick program is expected to stay in the background and generate  output<br />
       once  in a while.  In this case, the command is executed right away and<br />
       screen stores the last line of output.  If  a  new  line  gets  printed<br />
       screen will automatically refresh the hardstatus or the captions.<br />
       The  second  form  of the command deletes the backtick command with the<br />
       numerical id id.</p>
<p>       bce [on|off]</p>
<p>       Change background-color-erase setting. If &#8220;bce&#8221; is set to on, all char-<br />
       acters  cleared  by an erase/insert/scroll/clear operation will be dis-<br />
       played in the current background color.  Otherwise  the  default  back-<br />
       ground color is used.</p>
<p>       bell_msg [message]</p>
<p>       When a bell character is sent to a background window, screen displays a<br />
       notification in the message line.  The notification message can be  re-<br />
       defined by this command.  Each occurrence of `%&#8217; in message is replaced<br />
       by the number of the window to which a bell has  been  sent,  and  each<br />
       occurrence of `^G&#8217; is replaced by the definition for bell in your term-<br />
       cap (usually an audible bell).  The default message is</p>
<p>                   &#8216;Bell in window %n&#8217;</p>
<p>       An empty message can be supplied to the &#8220;bell_msg&#8221; command to  suppress<br />
       output of a message line (bell_msg &#8220;&#8221;).  Without parameter, the current<br />
       message is shown.</p>
<p>       bind [-c class] key [command [args]]</p>
<p>       Bind a command to a key.  By default, most of the commands provided  by<br />
       screen  are  bound to one or more keys as indicated in the &#8220;DEFAULT KEY<br />
       BINDINGS&#8221; section, e.g. the command to create a new window is bound  to<br />
       &#8220;C-c&#8221;  and  &#8220;c&#8221;.   The  &#8220;bind&#8221;  command can be used to redefine the key<br />
       bindings and to define new bindings.  The key argument is either a sin-<br />
       gle  character,  a two-character sequence of the form &#8220;^x&#8221; (meaning &#8220;C-<br />
       x&#8221;), a backslash followed by an octal number (specifying the ASCII code<br />
                   bind ^k<br />
                   bind k<br />
                   bind K kill<br />
                   bind ^f screen telnet foobar<br />
                   bind 33 screen -ln -t root -h 1000 9 su</p>
<p>       would bind the space key to the command that displays a list of windows<br />
       (so  that the command usually invoked by &#8220;C-a C-w&#8221; would also be avail-<br />
       able as &#8220;C-a space&#8221;). The next three  lines  remove  the  default  kill<br />
       binding  from &#8220;C-a C-k&#8221; and &#8220;C-a k&#8221;.  &#8220;C-a K&#8221; is then bound to the kill<br />
       command. Then it binds &#8220;C-f&#8221; to the command &#8220;create  a  window  with  a<br />
       TELNET  connection  to  foobar&#8221;,  and bind &#8220;escape&#8221; to the command that<br />
       creates an non-login window with a.k.a. &#8220;root&#8221; in slot #9, with a supe-<br />
       ruser shell and a scrollback buffer of 1000 lines.</p>
<p>                   bind -c demo1 0 select 10<br />
                   bind -c demo1 1 select 11<br />
                   bind -c demo1 2 select 12<br />
                   bindkey &#8220;^B&#8221; command -c demo1</p>
<p>       makes &#8220;C-b 0&#8221; select window 10, &#8220;C-b 1&#8221; window 11, etc.</p>
<p>                   bind -c demo2 0 select 10<br />
                   bind -c demo2 1 select 11<br />
                   bind -c demo2 2 select 12<br />
                   bind &#8211; command -c demo2</p>
<p>       makes &#8220;C-a &#8211; 0&#8221; select window 10, &#8220;C-a &#8211; 1&#8221; window 11, etc.</p>
<p>       bindkey [-d] [-m] [-a] [[-k|-t] string [cmd args]]</p>
<p>       This  command manages screen&#8217;s input translation tables. Every entry in<br />
       one of the tables tells screen how to react if a  certain  sequence  of<br />
       characters is encountered. There are three tables: one that should con-<br />
       tain actions programmed by the user, one for the default  actions  used<br />
       for  terminal  emulation  and  one  for screen&#8217;s copy mode to do cursor<br />
       movement. See section &#8220;INPUT TRANSLATION&#8221; for a  list  of  default  key<br />
       bindings.<br />
       If  the  -d  option  is  given,  bindkey modifies the default table, -m<br />
       changes the copy mode table and with neither option the user  table  is<br />
       selected.   The  argument string is the sequence of characters to which<br />
       an action is bound. This can either be a fixed string or a termcap key-<br />
       board capability name (selectable with the -k option).<br />
       Some  keys  on a VT100 terminal can send a different string if applica-<br />
       tion mode is turned on (e.g the  cursor  keys).   Such  keys  have  two<br />
       entries  in  the translation table. You can select the application mode<br />
       entry by specifying the -a option.<br />
       The -t option tells screen not to do inter-character timing. One cannot<br />
       turn off the timing if a termcap capability is used.<br />
       Cmd  can  be any of screen&#8217;s commands with an arbitrary number of args.<br />
       If cmd is omitted the key-binding is removed from the table.<br />
       Here are some examples of keyboard bindings:<br />
       you  did the above &#8220;stuff barfoo&#8221; binding, you can enter the word &#8220;foo&#8221;<br />
       by typing &#8220;^Tfoo&#8221;. If you want to insert a &#8220;^T&#8221; you have to  press  the<br />
       key twice (i.e., escape the escape binding).</p>
<p>               bindkey -k F1 command<br />
       Make the F11 (not F1!) key an alternative screen escape (besides ^A).</p>
<p>       break [duration]</p>
<p>       Send a break signal for duration*0.25 seconds to this window.  For non-<br />
       Posix systems the time interval may be  rounded  up  to  full  seconds.<br />
       Most useful if a character device is attached to the window rather than<br />
       a shell process (See also chapter &#8220;WINDOW TYPES&#8221;). The maximum duration<br />
       of a break signal is limited to 15 seconds.</p>
<p>       blanker</p>
<p>       Activate the screen blanker. First the screen is cleared. If no blanker<br />
       program is defined, the cursor is turned off, otherwise, the program is<br />
       started  and  it&#8217;s output is written to the screen.  The screen blanker<br />
       is killed with the first keypress, the read key is discarded.<br />
       This command is normally used together with the &#8220;idle&#8221; command.</p>
<p>       blankerprg [program args]</p>
<p>       Defines a blanker program. Disables the blanker program if no arguments<br />
       are given.</p>
<p>       breaktype [tcsendbreak|TIOCSBRK |TCSBRK]</p>
<p>       Choose  one  of  the available methods of generating a break signal for<br />
       terminal devices. This command should affect the current  window  only.<br />
       But  it still behaves identical to &#8220;defbreaktype&#8221;. This will be changed<br />
       in the future.  Calling &#8220;breaktype&#8221;  with  no  parameter  displays  the<br />
       break method for the current window.</p>
<p>       bufferfile [exchange-file]</p>
<p>       Change the filename used for reading and writing with the paste buffer.<br />
       If the optional argument to the &#8220;bufferfile&#8221; command  is  omitted,  the<br />
       default setting (&#8220;/tmp/screen-exchange&#8221;) is reactivated.  The following<br />
       example will paste the system&#8217;s password file into  the  screen  window<br />
       (using the paste buffer, where a copy remains):</p>
<p>                   C-a : bufferfile /etc/passwd<br />
                   C-a &lt; C-a ]<br />
                   C-a : bufferfile</p>
<p>       c1 [on|off]</p>
<p>       Change  c1  code  processing.  &#8220;C1  on&#8221; tells screen to treat the input<br />
       characters between 128 and 159 as control  functions.   Such  an  8-bit<br />
       escapes  from  the  &#8220;STRING  ESCAPES&#8221; chapter. Screen uses a default of<br />
       `%3n %t&#8217;.</p>
<p>       You can mix both forms by providing a string as an additional argument.</p>
<p>       charset set</p>
<p>       Change  the current character set slot designation and charset mapping.<br />
       The first four character of set  are  treated  as  charset  designators<br />
       while the fifth and sixth character must be in range &#8216;0&#8217; to &#8216;3&#8217; and set<br />
       the GL/GR charset mapping. On every position a &#8216;.&#8217; may be used to indi-<br />
       cate  that the corresponding charset/mapping should not be changed (set<br />
       is padded to six characters internally by appending  &#8216;.&#8217;   chars).  New<br />
       windows  have  &#8220;BBBB02&#8221; as default charset, unless a &#8220;encoding&#8221; command<br />
       is active.<br />
       The current setting can be viewed with the &#8220;info&#8221; command.</p>
<p>       chdir [directory]</p>
<p>       Change the current directory of screen to the specified  directory  or,<br />
       if called without an argument, to your home directory (the value of the<br />
       environment variable $HOME).  All windows that are created by means  of<br />
       the  &#8220;screen&#8221;  command  from  within  &#8220;.screenrc&#8221; or by means of &#8220;C-a :<br />
       screen &#8230;&#8221; or &#8220;C-a c&#8221; use this as their default directory.  Without  a<br />
       chdir  command,  this  would  be  the  directory  from which screen was<br />
       invoked.  Hardcopy and log files are always  written  to  the  window&#8217;s<br />
       default  directory, not the current directory of the process running in<br />
       the window.  You can use this command multiple times in your  .screenrc<br />
       to start various windows in different default directories, but the last<br />
       chdir value will affect all the windows you create interactively.</p>
<p>       clear</p>
<p>       Clears the current window and saves its image to the scrollback buffer.</p>
<p>       colon [prefix]</p>
<p>       Allows  you  to  enter &#8220;.screenrc&#8221; command lines. Useful for on-the-fly<br />
       modification of key bindings, specific  window  creation  and  changing<br />
       settings.  Note  that  the &#8220;set&#8221; keyword no longer exists! Usually com-<br />
       mands affect the current window rather than default settings for future<br />
       windows. Change defaults with commands starting with &#8216;def&#8230;&#8217;.</p>
<p>       If you consider this as the `Ex command mode&#8217; of screen, you may regard<br />
       &#8220;C-a esc&#8221; (copy mode) as its `Vi command mode&#8217;.</p>
<p>       command [-c class]</p>
<p>       This command has the same effect as typing the screen escape  character<br />
       (^A).  It is probably only useful for key bindings.  If the &#8220;-c&#8221; option<br />
       is given, select the specified command  class.   See  also  &#8220;bind&#8221;  and<br />
       &#8220;bindkey&#8221;.<br />
       Enter copy/scrollback mode. This allows you to copy text from the  cur-<br />
       rent  window  and its history into the paste buffer. In this mode a vi-<br />
       like `full screen editor&#8217; is active:<br />
       Movement keys:<br />
         h, j, k, l move the cursor line by line or column by column.<br />
         0, ^ and $ move to the leftmost column, to the  first  or  last  non-<br />
           whitespace character on the line.<br />
         H,  M and L move the cursor to the leftmost column of the top, center<br />
           or bottom line of the window.<br />
         + and &#8211; positions one line up and down.<br />
         G moves to the specified absolute line (default: end of buffer).<br />
         | moves to the specified absolute column.<br />
         w, b, e move the cursor word by word.<br />
         B, E move the cursor WORD by WORD (as in vi).<br />
         C-u and C-d scroll the display up/down by  the  specified  amount  of<br />
           lines  while preserving the cursor position. (Default: half screen-<br />
           full).<br />
         C-b and C-f scroll the display up/down a full screen.<br />
         g moves to the beginning of the buffer.<br />
         % jumps to the specified percentage of the buffer.</p>
<p>       Note:<br />
           Emacs style movement keys can be customized by a .screenrc command.<br />
           (E.g.  markkeys  &#8220;h=^B:l=^F:$=^E&#8221;)  There is no simple method for a<br />
           full emacs-style keymap, as this involves multi-character codes.</p>
<p>       Marking:<br />
           The copy range is specified by setting two marks. The text  between<br />
           these marks will be highlighted. Press<br />
         space to set the first or second mark respectively.<br />
         Y and y used to mark one whole line or to mark from start of line.<br />
         W marks exactly one word.<br />
       Repeat count:<br />
           Any of these commands can be prefixed with a repeat count number by<br />
           pressing digits<br />
         0..9 which is taken as a repeat count.<br />
           Example: &#8220;C-a C-[ H 10 j 5 Y&#8221; will copy lines 11  to  15  into  the<br />
           paste buffer.<br />
       Searching:<br />
         / Vi-like search forward.<br />
         ? Vi-like search backward.<br />
         C-a s Emacs style incremental search forward.<br />
         C-r Emacs style reverse i-search.<br />
       Specials:<br />
           There  are  however  some keys that act differently than in vi.  Vi<br />
           does not allow one to yank rectangular blocks of text,  but  screen<br />
           does. Press<br />
         c  or  C  to  set the left or right margin respectively. If no repeat<br />
           count is given, both default to the current cursor position.<br />
           Example: Try this on a rather full text screen: &#8220;C-a [ M 20 l SPACE<br />
           c 10 l 5 j C SPACE&#8221;.</p>
<p>         a  before the final space key to toggle in append mode. Thus the con-<br />
           tents of the paste buffer will not be overwritten, but is  appended<br />
           to.<br />
         A toggles in append mode and sets a (second) mark.<br />
         &gt;  sets the (second) mark and writes the contents of the paste buffer<br />
           to the screen-exchange file (/tmp/screen-exchange per default) once<br />
           copy-mode is finished.<br />
           This  example  demonstrates how to dump the whole scrollback buffer<br />
           to that file: &#8220;C-A [ g SPACE G $ &gt;&#8221;.<br />
         C-g gives information about the current line and column.<br />
         x exchanges the first mark and the current cursor position.  You  can<br />
           use this to adjust an already placed mark.<br />
         @ does nothing. Does not even exit copy mode.<br />
         All keys not described here exit copy mode.</p>
<p>       copy_reg [key]</p>
<p>       No longer exists, use &#8220;readreg&#8221; instead.</p>
<p>       crlf [on|off]</p>
<p>       This  affects  the copying of text regions with the `C-a [&#8216; command. If<br />
       it is set to `on&#8217;,  lines  will  be  separated  by  the  two  character<br />
       sequence  `CR&#8217; &#8211; `LF&#8217;.  Otherwise (default) only `LF&#8217; is used.  When no<br />
       parameter is given, the state is toggled.</p>
<p>       debug on|off</p>
<p>       Turns runtime debugging on or off. If screen  has  been  compiled  with<br />
       option  -DDEBUG  debugging available and is turned on per default. Note<br />
       that this command only affects debugging output from the main  &#8220;SCREEN&#8221;<br />
       process  correctly.  Debug  output  from attacher processes can only be<br />
       turned off once and forever.</p>
<p>       defc1 on|off</p>
<p>       Same as the c1 command except that the default setting for new  windows<br />
       is changed. Initial setting is `on&#8217;.</p>
<p>       defautonuke on|off</p>
<p>       Same  as  the  autonuke command except that the default setting for new<br />
       displays is changed. Initial setting is `off&#8217;.  Note that you  can  use<br />
       the  special  `AN&#8217; terminal capability if you want to have a dependency<br />
       on the terminal type.</p>
<p>       defbce on|off</p>
<p>       Same as the bce command except that the default setting for new windows<br />
       is changed. Initial setting is `off&#8217;.</p>
<p>       defbreaktype [tcsendbreak|TIOCSBRK |TCSBRK]</p>
<p>       defescape xy</p>
<p>       Set  the default command characters. This is equivalent to the &#8220;escape&#8221;<br />
       except that it is useful multiuser sessions only. In a  multiuser  ses-<br />
       sion  &#8220;escape&#8221; changes the command character of the calling user, where<br />
       &#8220;defescape&#8221; changes the default command characters for users that  will<br />
       be added later.</p>
<p>       defflow on|off|auto [interrupt]</p>
<p>       Same  as  the flow command except that the default setting for new win-<br />
       dows is changed. Initial setting is `auto&#8217;.  Specifying  &#8220;defflow  auto<br />
       interrupt&#8221; is the same as the command-line options -fa and -i.</p>
<p>       defgr on|off</p>
<p>       Same  as the gr command except that the default setting for new windows<br />
       is changed. Initial setting is `off&#8217;.</p>
<p>       defhstatus [status]</p>
<p>       The hardstatus line that all new windows will get  is  set  to  status.<br />
       This  command  is useful to make the hardstatus of every window display<br />
       the window number or title or the like.  Status may  contain  the  same<br />
       directives  as in the window messages, but the directive escape charac-<br />
       ter is &#8216;^E&#8217; (octal 005) instead of &#8216;%&#8217;.  This was done to make a misin-<br />
       terpretation  of program generated hardstatus lines impossible.  If the<br />
       parameter status is omitted, the current default string  is  displayed.<br />
       Per default the hardstatus line of new windows is empty.</p>
<p>       defencoding enc</p>
<p>       Same  as  the  encoding command except that the default setting for new<br />
       windows is changed. Initial setting is the encoding taken from the ter-<br />
       minal.</p>
<p>       deflog on|off</p>
<p>       Same as the log command except that the default setting for new windows<br />
       is changed. Initial setting is `off&#8217;.</p>
<p>       deflogin on|off</p>
<p>       Same as the login command except that the default setting for new  win-<br />
       dows is changed. This is initialized with `on&#8217; as distributed (see con-<br />
       fig.h.in).</p>
<p>       defmode mode</p>
<p>       The mode of each newly allocated pseudo-tty is set to mode.  Mode is an<br />
       octal number.  When no &#8220;defmode&#8221; command is given, mode 0622 is used.<br />
       displays is changed. Initial setting is 256 bytes.  Note that  you  can<br />
       use  the  special &#8216;OL&#8217; terminal capability if you want to have a depen-<br />
       dency on the terminal type.</p>
<p>       defscrollback num</p>
<p>       Same as the scrollback command except that the default setting for  new<br />
       windows is changed. Initial setting is 100.</p>
<p>       defshell command</p>
<p>       Synonym to the shell command. See there.</p>
<p>       defsilence on|off</p>
<p>       Same  as  the  silence  command except that the default setting for new<br />
       windows is changed. Initial setting is `off&#8217;.</p>
<p>       defslowpaste msec&#8221;</p>
<p>       Same as the slowpaste command except that the default setting  for  new<br />
       windows is changed. Initial setting is 0 milliseconds, meaning `off&#8217;.</p>
<p>       defutf8 on|off</p>
<p>       Same  as  the utf8 command except that the default setting for new win-<br />
       dows is changed. Initial setting is `on&#8217; if  screen  was  started  with<br />
       &#8220;-U&#8221;, otherwise `off&#8217;.</p>
<p>       defwrap on|off</p>
<p>       Same  as  the wrap command except that the default setting for new win-<br />
       dows is changed. Initially line-wrap is on and can be toggled with  the<br />
       &#8220;wrap&#8221; command (&#8220;C-a r&#8221;) or by means of &#8220;C-a : wrap on|off&#8221;.</p>
<p>       defwritelock on|off|auto</p>
<p>       Same  as  the writelock command except that the default setting for new<br />
       windows is changed. Initially writelocks will off.</p>
<p>       defzombie [keys]</p>
<p>       Synonym to the zombie command. Both currently change the default.   See<br />
       there.</p>
<p>       detach [-h]</p>
<p>       Detach  the  screen session (disconnect it from the terminal and put it<br />
       into the background).  This returns you to the shell where you  invoked<br />
       screen.   A  detached screen can be resumed by invoking screen with the<br />
       -r option (see also section  &#8220;COMMAND-LINE  OPTIONS&#8221;).  The  -h  option<br />
       tells  screen  to  immediately  close  the  connection  to the terminal<br />
       This command prompts the user for a  digraph  sequence.  The  next  two<br />
       characters  typed  are  looked  up in a builtin table and the resulting<br />
       character is inserted in the input stream. For  example,  if  the  user<br />
       enters  &#8216;a&#8221;&#8216;,  an  a-umlaut  will  be  inserted. If the first character<br />
       entered is a 0 (zero), screen will treat the following  characters  (up<br />
       to  three) as an octal number instead.  The optional argument preset is<br />
       treated as user input, thus one can create an &#8220;umlaut&#8221; key.  For  exam-<br />
       ple  the  command &#8220;bindkey ^K digraph &#8216;&#8221;&#8216;&#8221; enables the user to generate<br />
       an a-umlaut by typing CTRL-K a.</p>
<p>       dumptermcap</p>
<p>       Write the termcap entry for the virtual terminal optimized for the cur-<br />
       rently   active   window   to   the   file  &#8220;.termcap&#8221;  in  the  user&#8217;s<br />
       &#8220;$HOME/.screen&#8221; directory (or wherever screen stores its  sockets.  See<br />
       the  &#8220;FILES&#8221;  section  below).   This termcap entry is identical to the<br />
       value of the environment variable $TERMCAP that is set up by screen for<br />
       each  window.  For  terminfo  based systems you will need to run a con-<br />
       verter like captoinfo and then compile the entry with tic.</p>
<p>       echo [-n] message</p>
<p>       The echo command may be used to annoy screen users with a  &#8216;message  of<br />
       the  day&#8217;.  Typically  installed in a global /etc/screenrc.  The option<br />
       &#8220;-n&#8221; may be used to suppress the line feed.  See also &#8220;sleep&#8221;.  Echo is<br />
       also useful for online checking of environment variables.</p>
<p>       encoding enc [enc]</p>
<p>       Tell  screen how to interpret the input/output. The first argument sets<br />
       the encoding of the current window. Each window can emulate a different<br />
       encoding.  The optional second parameter overwrites the encoding of the<br />
       connected terminal. It should never be needed as screen uses the locale<br />
       setting to detect the encoding.  There is also a way to select a termi-<br />
       nal encoding depending on the terminal type by using the  &#8220;KJ&#8221;  termcap<br />
       entry.</p>
<p>       Supported  encodings  are eucJP, SJIS, eucKR, eucCN, Big5, GBK, KOI8-R,<br />
       CP1251, UTF-8, ISO8859-2, ISO8859-3, ISO8859-4,  ISO8859-5,  ISO8859-6,<br />
       ISO8859-7, ISO8859-8, ISO8859-9, ISO8859-10, ISO8859-15, jis.</p>
<p>       See also &#8220;defencoding&#8221;, which changes the default setting of a new win-<br />
       dow.</p>
<p>       escape xy</p>
<p>       Set the command character to x and the character generating  a  literal<br />
       command  character  (by triggering the &#8220;meta&#8221; command) to y (similar to<br />
       the -e option).  Each argument is either a  single  character,  a  two-<br />
       character  sequence  of the form &#8220;^x&#8221; (meaning &#8220;C-x&#8221;), a backslash fol-<br />
       lowed by an octal number (specifying the ASCII code of the  character),<br />
       or  a  backslash  followed by a second character, such as &#8220;\^&#8221; or &#8220;\\&#8221;.<br />
       stderr of newcommand. A dot (.) connects the file descriptor to screen.<br />
       An  exclamation  mark (!) causes the file descriptor to be connected to<br />
       the application-process. A colon (:) combines both.  User input will go<br />
       to  newcommand unless newcommand receives the application-process&#8217; out-<br />
       put (fdpats first character is `!&#8217; or `:&#8217;) or  a  pipe  symbol  (|)  is<br />
       added (as a fourth character) to the end of fdpat.<br />
       Invoking  `exec&#8217; without arguments shows name and arguments of the cur-<br />
       rently running subprocess in this window. Only one  subprocess  a  time<br />
       can be running in each window.<br />
       When  a subprocess is running the `kill&#8217; command will affect it instead<br />
       of the windows process.<br />
       Refer to the postscript file `doc/fdpat.ps&#8217; for a  confusing  illustra-<br />
       tion  of  all  21  possible combinations. Each drawing shows the digits<br />
       2,1,0 representing the three file descriptors of  newcommand.  The  box<br />
       marked  `W&#8217;  is  the  usual pty that has the application-process on its<br />
       slave side.  The box marked `P&#8217; is  the  secondary  pty  that  now  has<br />
       screen at its master side.</p>
<p>       Abbreviations:<br />
       Whitespace  between  the  word  `exec&#8217; and fdpat and the command can be<br />
       omitted. Trailing dots and a fdpat consisting only of dots can be omit-<br />
       ted.  A  simple `|&#8217; is synonymous for the pattern `!..|&#8217;; the word exec<br />
       can be omitted here and can always be replaced by `!&#8217;.</p>
<p>       Examples:</p>
<p>              exec &#8230; /bin/sh<br />
              exec /bin/sh<br />
              !/bin/sh</p>
<p>       Creates another shell in the same window, while the original  shell  is<br />
       still  running.  Output  of  both shells is displayed and user input is<br />
       sent to the new /bin/sh.</p>
<p>              exec !.. stty 19200<br />
              exec ! stty 19200<br />
              !!stty 19200</p>
<p>       Set the speed of the window&#8217;s tty. If your  stty  command  operates  on<br />
       stdout, then add another `!&#8217;.</p>
<p>              exec !..| less<br />
              |less</p>
<p>       This  adds  a  pager to the window output. The special character `|&#8217; is<br />
       needed to give the user control over the pager  although  it  gets  its<br />
       input  from  the  window&#8217;s process. This works, because less listens on<br />
       stderr (a behavior that screen would not expect without the  `|&#8217;)  when<br />
       its  stdin  is  not a tty.  Less versions newer than 177 fail miserably<br />
       here; good old pg still works.</p>
<p>              !:sed -n s/.*Error.*/07/p</p>
<p>       Sets  the  flow-control  mode  for  this window.  Without parameters it<br />
       cycles the current window&#8217;s flow-control setting  from  &#8220;automatic&#8221;  to<br />
       &#8220;on&#8221;  to  &#8220;off&#8221;.  See the discussion on &#8220;FLOW-CONTROL&#8221; later on in this<br />
       document for full details and note, that this is subject to  change  in<br />
       future releases.  Default is set by `defflow&#8217;.</p>
<p>       focus [up|down|top|bottom]</p>
<p>       Move  the  input focus to the next region. This is done in a cyclic way<br />
       so that the top region is selected after the bottom one. If no  subcom-<br />
       mand is given it defaults to `down&#8217;. `up&#8217; cycles in the opposite order,<br />
       `top&#8217; and `bottom&#8217; go to the top and bottom region respectively. Useful<br />
       bindings are (j and k as in vi)<br />
           bind j focus down<br />
           bind k focus up<br />
           bind t focus top<br />
           bind b focus bottom<br />
       Note that k is traditionally bound to the kill command.</p>
<p>       gr [on|off]</p>
<p>       Turn GR charset switching on/off. Whenever screen sees an input charac-<br />
       ter with the 8th bit set, it will use the charset stored in the GR slot<br />
       and  print  the  character  with the 8th bit stripped. The default (see<br />
       also &#8220;defgr&#8221;) is not to process  GR  switching  because  otherwise  the<br />
       ISO88591 charset would not work.</p>
<p>       hardcopy [-h] [file]</p>
<p>       Writes  out  the  currently displayed image to the file file, or, if no<br />
       filename is specified, to hardcopy.n in the default directory, where  n<br />
       is the number of the current window.  This either appends or overwrites<br />
       the file if it exists. See below.  If the option -h is specified,  dump<br />
       also the contents of the scrollback buffer.</p>
<p>       hardcopy_append on|off</p>
<p>       If set to &#8220;on&#8221;, screen will append to the &#8220;hardcopy.n&#8221; files created by<br />
       the command &#8220;C-a h&#8221;, otherwise these files are overwritten  each  time.<br />
       Default is `off&#8217;.</p>
<p>       hardcopydir directory</p>
<p>       Defines  a  directory  where  hardcopy  files will be placed. If unset,<br />
       hardcopys are dumped in screen&#8217;s current working directory.</p>
<p>       hardstatus [on|off]<br />
       hardstatus [always]lastline|message|ignore [string]<br />
       hardstatus string [string]</p>
<p>       This command configures the use and emulation of the  terminal&#8217;s  hard-<br />
       status  line.  The first form toggles whether screen will use the hard-<br />
       used as default string, i.e., the stored hardstatus of the current win-<br />
       dow  (settable  via  &#8220;ESC]0;&lt;string&gt;^G&#8221;  or &#8220;ESC_&lt;string&gt;ESC\&#8221;) is dis-<br />
       played.  You can customize this to any string you  like  including  the<br />
       escapes  from  the &#8220;STRING ESCAPES&#8221; chapter. If you leave out the argu-<br />
       ment string, the current string is displayed.</p>
<p>       You can mix the second and third form by providing the string as  addi-<br />
       tional argument.</p>
<p>       height [-w|-d] [lines [cols]]</p>
<p>       Set the display height to a specified number of lines. When no argument<br />
       is given it toggles between 24 and 42 lines display. You can also spec-<br />
       ify  a  width  if  you want to change both values.  The -w option tells<br />
       screen to leave the display size unchanged  and  just  set  the  window<br />
       size, -d vice versa.</p>
<p>       help [-c class]</p>
<p>       Not  really  a  online help, but displays a help screen showing you all<br />
       the key bindings.  The first pages list all the internal commands  fol-<br />
       lowed  by  their  current  bindings.  Subsequent pages will display the<br />
       custom commands, one command per key.  Press  space  when  you&#8217;re  done<br />
       reading  each  page, or return to exit early.  All other characters are<br />
       ignored. If the &#8220;-c&#8221; option is given, display all  bound  commands  for<br />
       the  specified command class.  See also &#8220;DEFAULT KEY BINDINGS&#8221; section.</p>
<p>       history</p>
<p>       Usually users work with a shell that allows  easy  access  to  previous<br />
       commands.  For example csh has the command &#8220;!!&#8221; to repeat the last com-<br />
       mand executed.  Screen allows you to have a primitive way of re-calling<br />
       &#8220;the  command that started &#8230;&#8221;: You just type the first letter of that<br />
       command, then hit `C-a {&#8216; and screen tries to find a previous line that<br />
       matches  with  the  `prompt  character&#8217; to the left of the cursor. This<br />
       line is pasted into this window&#8217;s input queue.  Thus you have  a  crude<br />
       command  history  (made  up  by  the  visible window and its scrollback<br />
       buffer).</p>
<p>       hstatus status</p>
<p>       Change the window&#8217;s hardstatus line to the string status.</p>
<p>       idle [timeout [cmd args]]</p>
<p>       Sets a command that is run after the specified number of seconds  inac-<br />
       tivity  is reached. This command will normally be the &#8220;blanker&#8221; command<br />
       to create a screen blanker, but it can be any screen  command.   If  no<br />
       command  is  specified,  only the timeout is set. A timeout of zero (ot<br />
       the special timeout off) disables  the  timer.   If  no  arguments  are<br />
       given, the current settings are displayed.</p>
<p>         +flow     automatic flow control, currently on.<br />
         -flow     automatic flow control, currently off.<br />
         +(+)flow  flow control enabled. Agrees with automatic control.<br />
         -(+)flow  flow control disabled. Disagrees with automatic control.<br />
         +(-)flow  flow control enabled. Disagrees with automatic control.<br />
         -(-)flow  flow control disabled. Agrees with automatic control.</p>
<p>       The  current line wrap setting (`+wrap&#8217; indicates enabled, `-wrap&#8217; not)<br />
       is also shown. The flags `ins&#8217;, `org&#8217;, `app&#8217;, `log&#8217;, `mon&#8217;  or  `nored&#8217;<br />
       are  displayed when the window is in insert mode, origin mode, applica-<br />
       tion-keypad mode, has output logging, activity  monitoring  or  partial<br />
       redraw enabled.</p>
<p>       The  currently  active  character set (G0, G1, G2, or G3) and in square<br />
       brackets the terminal character sets that are currently  designated  as<br />
       G0  through  G3  is  shown.  If the window is in UTF-8 mode, the string<br />
       &#8220;UTF-8&#8221; is shown instead.</p>
<p>       Additional modes depending on the type of the window are  displayed  at<br />
       the end of the status line (See also chapter &#8220;WINDOW TYPES&#8221;).<br />
       If  the  state  machine  of  the  terminal emulator is in a non-default<br />
       state, the info line is started with a string identifying  the  current<br />
       state.<br />
       For system information use the &#8220;time&#8221; command.</p>
<p>       ins_reg [key]</p>
<p>       No longer exists, use &#8220;paste&#8221; instead.</p>
<p>       kill</p>
<p>       Kill current window.<br />
       If  there is an `exec&#8217; command running then it is killed. Otherwise the<br />
       process (shell) running in the window receives a HANGUP condition,  the<br />
       window  structure  is  removed  and  screen  (your display) switches to<br />
       another window.  When the  last  window  is  destroyed,  screen  exits.<br />
       After a kill screen switches to the previously displayed window.<br />
       Note:  Emacs  users  should  keep  this command in mind, when killing a<br />
       line.  It is recommended not to use &#8220;C-a&#8221; as the screen escape  key  or<br />
       to rebind kill to &#8220;C-a K&#8221;.</p>
<p>       lastmsg</p>
<p>       Redisplay  the  last  contents  of  the message/status line.  Useful if<br />
       you&#8217;re typing when a message appears, because  the  message  goes  away<br />
       when you press a key (unless your terminal has a hardware status line).<br />
       Refer to the commands &#8220;msgwait&#8221; and &#8220;msgminwait&#8221; for fine tuning.</p>
<p>       license</p>
<p>       Display the disclaimer page. This is done whenever  screen  is  started<br />
       without   options,   which   should  be  often  enough.  See  also  the</p>
<p>       log [on|off]</p>
<p>       Start/stop writing output of the current window to a file &#8220;screenlog.n&#8221;<br />
       in the window&#8217;s default directory, where n is the number of the current<br />
       window. This filename can be changed with the `logfile&#8217; command. If  no<br />
       parameter is given, the state of logging is toggled. The session log is<br />
       appended to the previous contents of the file if it already exists. The<br />
       current  contents  and  the  contents of the scrollback history are not<br />
       included in the session log.  Default is `off&#8217;.</p>
<p>       logfile filename<br />
       logfile flush secs</p>
<p>       Defines the name the log files will get. The default is &#8220;screenlog.%n&#8221;.<br />
       The  second  form changes the number of seconds screen will wait before<br />
       flushing the logfile buffer to the file-system. The default value is 10<br />
       seconds.</p>
<p>       login [on|off]</p>
<p>       Adds  or  removes  the  entry in the utmp database file for the current<br />
       window.  This controls if the window is `logged in&#8217;.  When no parameter<br />
       is  given,  the  login state of the window is toggled.  Additionally to<br />
       that toggle, it is convenient having a `log in&#8217; and a  `log  out&#8217;  key.<br />
       E.g. `bind I login on&#8217; and `bind O login off&#8217; will map these keys to be<br />
       C-a I and C-a O.  The default setting (in config.h.in) should  be  &#8220;on&#8221;<br />
       for  a screen that runs under suid-root.  Use the &#8220;deflogin&#8221; command to<br />
       change the default login state for new windows. Both commands are  only<br />
       present when screen has been compiled with utmp support.</p>
<p>       logtstamp [on|off]<br />
       logtstamp after [secs]<br />
       logtstamp string [string]</p>
<p>       This command controls logfile time-stamp mechanism of screen.  If time-<br />
       stamps are turned &#8220;on&#8221;, screen adds a  string  containing  the  current<br />
       time  to the logfile after two minutes of inactivity.  When output con-<br />
       tinues and more than another two minutes have passed,  a  second  time-<br />
       stamp  is  added  to document the restart of the output. You can change<br />
       this timeout with the second form of the command.  The  third  form  is<br />
       used  for customizing the time-stamp string (`&#8211; %n:%t &#8212; time-stamp &#8212;<br />
       %M/%d/%y %c:%s &#8211;\n&#8217; by default).</p>
<p>       mapdefault</p>
<p>       Tell screen that the next input character should only be looked  up  in<br />
       the default bindkey table. See also &#8220;bindkey&#8221;.</p>
<p>       mapnotnext</p>
<p>       Like mapdefault, but don&#8217;t even look in the default bindkey table.<br />
       h=^B:l=^F:$=^E&#8221; would set the mode for an emacs-style binding.  If your<br />
       terminal sends characters, that cause you to abort copy mode, then this<br />
       command may help by binding these characters to do nothing.  The  no-op<br />
       character  is `@&#8217; and is used like this: &#8220;markkeys @=L=H&#8221; if you do not<br />
       want to use the `H&#8217; or `L&#8217; commands any longer.  As shown in this exam-<br />
       ple,  multiple  keys can be assigned to one function in a single state-<br />
       ment.</p>
<p>       maxwin num</p>
<p>       Set the maximum  window  number  screen  will  create.  Doesn&#8217;t  affect<br />
       already existing windows. The number may only be decreased.</p>
<p>       meta</p>
<p>       Insert  the  command  character  (C-a)  in  the  current window&#8217;s input<br />
       stream.</p>
<p>       monitor [on|off]</p>
<p>       Toggles activity monitoring of windows.  When monitoring is  turned  on<br />
       and  an  affected  window  is  switched  into  the background, you will<br />
       receive the activity notification message in the  status  line  at  the<br />
       first  sign of output and the window will also be marked with an `@&#8217; in<br />
       the window-status display.  Monitoring is initially off  for  all  win-<br />
       dows.</p>
<p>       msgminwait sec</p>
<p>       Defines  the  time screen delays a new message when one message is cur-<br />
       rently displayed.  The default is 1 second.</p>
<p>       msgwait sec</p>
<p>       Defines the time a message is displayed if screen is not  disturbed  by<br />
       other activity. The default is 5 seconds.</p>
<p>       multiuser on|off</p>
<p>       Switch between singleuser and multiuser mode. Standard screen operation<br />
       is singleuser. In  multiuser  mode  the  commands  `acladd&#8217;,  `aclchg&#8217;,<br />
       `aclgrp&#8217;  and  `acldel&#8217; can be used to enable (and disable) other users<br />
       accessing this screen session.</p>
<p>       nethack on|off</p>
<p>       Changes the kind of error messages used by screen.  When you are famil-<br />
       iar  with  the game &#8220;nethack&#8221;, you may enjoy the nethack-style messages<br />
       which will often blur the facts a little, but are much funnier to read.<br />
       Anyway, standard messages often tend to be unclear as well.<br />
       This  option  is only available if screen was compiled with the NETHACK<br />
       flag defined. The default setting is then determined by the presence of<br />
       put.  If  nonblock is on, screen waits until the timeout is reached (on<br />
       is treated as 1s). If the display  still  doesn&#8217;t  receive  characters,<br />
       screen will consider it &#8220;blocked&#8221; and stop sending characters to it. If<br />
       at some time it restarts to accept characters, screen will unblock  the<br />
       display and redisplay the updated window contents.</p>
<p>       number [n]</p>
<p>       Change  the  current  windows  number. If the given number n is already<br />
       used by another window, both windows  exchange  their  numbers.  If  no<br />
       argument  is specified, the current window number (and title) is shown.</p>
<p>       obuflimit [limit]</p>
<p>       If the output buffer contains more bytes than the specified  limit,  no<br />
       more  data  will be read from the windows. The default value is 256. If<br />
       you have a fast display (like xterm), you can set  it  to  some  higher<br />
       value. If no argument is specified, the current setting is displayed.</p>
<p>       only</p>
<p>       Kill all regions but the current one.</p>
<p>       other</p>
<p>       Switch  to  the  window  displayed  previously.  If this window does no<br />
       longer exist, other has the same effect as next.</p>
<p>       partial on|off</p>
<p>       Defines whether the display should be  refreshed  (as  with  redisplay)<br />
       after  switching  to  the current window. This command only affects the<br />
       current window.  To immediately affect all windows use  the  allpartial<br />
       command.  Default is `off&#8217;, of course.  This default is fixed, as there<br />
       is currently no defpartial command.</p>
<p>       password [crypted_pw]</p>
<p>       Present a crypted password in your &#8220;.screenrc&#8221; file and screen will ask<br />
       for  it, whenever someone attempts to resume a detached. This is useful<br />
       if you have privileged programs running under screen and  you  want  to<br />
       protect  your session from reattach attempts by another user masquerad-<br />
       ing as your uid (i.e. any superuser.)  If no crypted password is speci-<br />
       fied, screen prompts twice for typing a password and places its encryp-<br />
       tion in the paste buffer.  Default is `none&#8217;,  this  disables  password<br />
       checking.</p>
<p>       paste [registers [dest_reg]]</p>
<p>       Write  the  (concatenated)  contents  of the specified registers to the<br />
       stdin queue of the current window. The register &#8216;.&#8217; is treated  as  the<br />
       paste  buffer. If no parameter is given the user is prompted for a sin-<br />
       Tell screen to include  font  information  in  the  paste  buffer.  The<br />
       default  is  not  to do so. This command is especially useful for multi<br />
       character fonts like kanji.</p>
<p>       pow_break</p>
<p>       Reopen the window&#8217;s terminal line  and  send  a  break  condition.  See<br />
       `break&#8217;.</p>
<p>       pow_detach</p>
<p>       Power  detach.  Mainly the same as detach, but also sends a HANGUP sig-<br />
       nal to the parent process of screen.  CAUTION: This will  result  in  a<br />
       logout, when screen was started from your login shell.</p>
<p>       pow_detach_msg [message]</p>
<p>       The message specified here is output whenever a `Power detach&#8217; was per-<br />
       formed. It may be used as a replacement for  a  logout  message  or  to<br />
       reset baud rate, etc.  Without parameter, the current message is shown.</p>
<p>       prev</p>
<p>       Switch to the window with the next lower number.  This command  can  be<br />
       used repeatedly to cycle through the list of windows.</p>
<p>       printcmd [cmd]</p>
<p>       If  cmd  is not an empty string, screen will not use the terminal capa-<br />
       bilities &#8220;po/pf&#8221; if it detects an ansi print sequence ESC [  5  i,  but<br />
       pipe the output into cmd.  This should normally be a command like &#8220;lpr&#8221;<br />
       or &#8220;&#8216;cat &gt; /tmp/scrprint'&#8221;.  printcmd without a  command  displays  the<br />
       current  setting.  The ansi sequence ESC \ ends printing and closes the<br />
       pipe.<br />
       Warning: Be careful with this command! If other user have write  access<br />
       to your terminal, they will be able to fire off print commands.</p>
<p>       process [key]</p>
<p>       Stuff the contents of the specified register into screen&#8217;s input queue.<br />
       If no argument is given you are prompted for a register name. The  text<br />
       is  parsed  as  if  it had been typed in from the user&#8217;s keyboard. This<br />
       command can be used to bind multiple actions to a single key.</p>
<p>       quit</p>
<p>       Kill all windows and terminate screen.  Note that on VT100-style termi-<br />
       nals  the keys C-4 and C-\ are identical.  This makes the default bind-<br />
       ings dangerous: Be careful not to type C-a C-4  when  selecting  window<br />
       no.  4.  Use the empty bind command (as in &#8220;bind &#8216;^\'&#8221;) to remove a key<br />
       binding.</p>
<p>       the encoding of the file via the -e option.  The following example will<br />
       paste the system&#8217;s password file into the screen window (using register<br />
       p, where a copy remains):</p>
<p>                   C-a : readreg p /etc/passwd<br />
                   C-a : paste p</p>
<p>       redisplay</p>
<p>       Redisplay the current window. Needed to get a full  redisplay  when  in<br />
       partial redraw mode.</p>
<p>       register [-e encoding] key string</p>
<p>       Save  the  specified  string  to the register key.  The encoding of the<br />
       string can be specified via the -e option.  See also the  &#8220;paste&#8221;  com-<br />
       mand.</p>
<p>       remove</p>
<p>       Kill the current region. This is a no-op if there is only one region.</p>
<p>       removebuf</p>
<p>       Unlinks  the  screen-exchange  file used by the commands &#8220;writebuf&#8221; and<br />
       &#8220;readbuf&#8221;.</p>
<p>       reset</p>
<p>       Reset the virtual  terminal  to  its  &#8220;power-on&#8221;  values.  Useful  when<br />
       strange  settings  (like  scroll regions or graphics character set) are<br />
       left over from an application.</p>
<p>       resize</p>
<p>       Resize the current region. The space will be removed from or  added  to<br />
       the  region below or if there&#8217;s not enough space from the region above.</p>
<p>              resize +N   increase current region height by N</p>
<p>              resize -N   decrease current region height by N</p>
<p>              resize  N   set current region height to N</p>
<p>              resize  =   make all windows equally high</p>
<p>              resize  max maximize current region height</p>
<p>              resize  min minimize current region height</p>
<p>       screen [-opts] [n] [cmd [args]]<br />
                   screen 1<br />
                   screen -fn -t foobar -L 2 telnet foobar</p>
<p>       screen creates a shell window (in window #1) and a window with a TELNET<br />
       connection  to the machine foobar (with no flow-control using the title<br />
       &#8220;foobar&#8221; in window #2) and will write a logfile (&#8220;screenlog.2&#8221;) of  the<br />
       telnet session.  Note, that unlike previous versions of screen no addi-<br />
       tional default window is created when &#8220;screen&#8221; commands are included in<br />
       your  &#8220;.screenrc&#8221;  file.  When  the initialization is completed, screen<br />
       switches to the last window specified in your  .screenrc  file  or,  if<br />
       none, opens a default window #0.<br />
       Screen  has built in some functionality of &#8220;cu&#8221; and &#8220;telnet&#8221;.  See also<br />
       chapter &#8220;WINDOW TYPES&#8221;.</p>
<p>       scrollback num</p>
<p>       Set the size of the scrollback buffer for the current  windows  to  num<br />
       lines.  The  default scrollback is 100 lines.  See also the &#8220;defscroll-<br />
       back&#8221; command and use &#8220;C-a i&#8221; to view the current setting.</p>
<p>       select [WindowID]</p>
<p>       Switch to the window identified by WindowID.  This can be a prefix of a<br />
       window title (alphanumeric window name) or a window number.  The param-<br />
       eter is optional and if omitted, you get prompted  for  an  identifier.<br />
       When  a  new  window  is  established,  the  first  available number is<br />
       assigned to this window.  Thus, the first window can  be  activated  by<br />
       &#8220;select  0&#8221;.   The  number of windows is limited at compile-time by the<br />
       MAXWIN configuration parameter (which defaults to 40 in Debian).  There<br />
       are  two  special  WindowIDs, &#8220;-&#8221; selects the internal blank window and<br />
       &#8220;.&#8221; selects the current window. The  latter  is  useful  if  used  with<br />
       screen&#8217;s &#8220;-X&#8221; option.</p>
<p>       sessionname [name]</p>
<p>       Rename  the  current  session.  Note,  that for &#8220;screen -list&#8221; the name<br />
       shows up with the process-id prepended. If the argument &#8220;name&#8221; is omit-<br />
       ted,  the name of this session is displayed. Caution: Among other prob-<br />
       lems, the $STY environment variable still reflects the old  name.   Use<br />
       of  this  command  is  strongly  discouraged.  Use the &#8220;-S&#8221; commandline<br />
       option if you need this feature.  The default is constructed  from  the<br />
       tty and host names.</p>
<p>       setenv [var [string]]</p>
<p>       Set the environment variable var to value string.  If only var is spec-<br />
       ified, the user will be prompted to enter a value.   If  no  parameters<br />
       are  specified,  the user will be prompted for both variable and value.<br />
       The environment is inherited by all subsequently forked shells.</p>
<p>       setsid [on|off]</p>
<p>       shelltitle title</p>
<p>       Set the title for all shells created during startup or by the  C-A  C-c<br />
       command.   For  details about what a title is, see the discussion enti-<br />
       tled &#8220;TITLES (naming windows)&#8221;.</p>
<p>       silence [on|off|sec]</p>
<p>       Toggles silence monitoring of windows.  When silence is turned  on  and<br />
       an  affected  window  is switched into the background, you will receive<br />
       the silence notification message in the status line after  a  specified<br />
       period of inactivity (silence). The default timeout can be changed with<br />
       the `silencewait&#8217; command or by specifying a number of seconds  instead<br />
       of `on&#8217; or `off&#8217;.  Silence is initially off for all windows.</p>
<p>       silencewait sec</p>
<p>       Define  the  time  that  all  windows monitored for silence should wait<br />
       before displaying a message. Default 30 seconds.</p>
<p>       sleep num</p>
<p>       This command will pause the execution  of  a  .screenrc  file  for  num<br />
       seconds.  Keyboard activity will end the sleep.  It may be used to give<br />
       users a chance to read the messages output by &#8220;echo&#8221;.</p>
<p>       slowpaste msec</p>
<p>       Define the speed at which text is inserted into the current  window  by<br />
       the paste (&#8220;C-a ]&#8221;) command.  If the slowpaste value is nonzero text is<br />
       written character by character.  screen will make a pause of msec  mil-<br />
       liseconds after each single character write to allow the application to<br />
       process its input. Only use slowpaste if your underlying system exposes<br />
       flow control problems while pasting large amounts of text.</p>
<p>       source file</p>
<p>       Read and execute commands from file file. Source commands may be nested<br />
       to a maximum recursion level of ten. If file is not  an  absolute  path<br />
       and screen is already processing a source command, the parent directory<br />
       of the running source command file is used to search for the  new  com-<br />
       mand file before screen&#8217;s current directory.</p>
<p>       Note  that  termcap/terminfo/termcapinfo  commands only work at startup<br />
       and reattach time, so they must be reached  via  the  default  screenrc<br />
       files to have an effect.</p>
<p>       sorendition [attr [color]]</p>
<p>       Change  the  way screen does highlighting for text marking and printing<br />
       messages.  See the &#8220;STRING ESCAPES&#8221; chapter for the syntax of the modi-<br />
       fiers.  The default is currently &#8220;=s dd&#8221; (standout, default colors).</p>
<p>       Stuff  the  string  string  in  the input buffer of the current window.<br />
       This is like the &#8220;paste&#8221; command but with much less overhead.  You can-<br />
       not paste large buffers with the &#8220;stuff&#8221; command. It is most useful for<br />
       key bindings. See also &#8220;bindkey&#8221;.</p>
<p>       su [username [password [password2]]</p>
<p>       Substitute the user of a display. The command prompts for  all  parame-<br />
       ters  that  are omitted. If passwords are specified as parameters, they<br />
       have to be specified un-crypted. The first password is matched  against<br />
       the systems passwd database, the second password is matched against the<br />
       screen password as set with the commands &#8220;acladd&#8221; or &#8220;password&#8221;.   &#8220;Su&#8221;<br />
       may  be  useful  for the screen administrator to test multiuser setups.<br />
       When the identification fails, the user  has  access  to  the  commands<br />
       available  for  user nobody.  These are &#8220;detach&#8221;, &#8220;license&#8221;, &#8220;version&#8221;,<br />
       &#8220;help&#8221; and &#8220;displays&#8221;.</p>
<p>       suspend</p>
<p>       Suspend screen.  The windows are in the `detached&#8217; state, while  screen<br />
       is  suspended.  This  feature  relies on the shell being able to do job<br />
       control.</p>
<p>       term term</p>
<p>       In each window&#8217;s environment screen opens, the $TERM variable is set to<br />
       &#8220;screen&#8221; by default.  But when no description for &#8220;screen&#8221; is installed<br />
       in the local termcap or terminfo data base, you set $TERM to  &#8211;  say  &#8211;<br />
       &#8220;vt100&#8221;.  This  won&#8217;t do much harm, as screen is VT100/ANSI compatible.<br />
       The use of the &#8220;term&#8221; command is discouraged for  non-default  purpose.<br />
       That  is,  one  may want to specify special $TERM settings (e.g. vt100)<br />
       for the next &#8220;screen rlogin  othermachine&#8221;  command.  Use  the  command<br />
       &#8220;screen -T vt100 rlogin othermachine&#8221; rather than setting and resetting<br />
       the default.</p>
<p>       termcap term terminal-tweaks [window-tweaks]<br />
       terminfo term terminal-tweaks [window-tweaks]<br />
       termcapinfo term terminal-tweaks [window-tweaks]</p>
<p>       Use this command to modify your terminal&#8217;s termcap entry without  going<br />
       through  all  the  hassles involved in creating a custom termcap entry.<br />
       Plus, you can optionally customize the termcap generated for  the  win-<br />
       dows.   You have to place these commands in one of the screenrc startup<br />
       files, as they are meaningless once the terminal emulator is booted.<br />
       If your system works uses the terminfo database  rather  than  termcap,<br />
       screen  will  understand  the  `terminfo&#8217;  command,  which has the same<br />
       effects as the `termcap&#8217; command.  Two separate commands are  provided,<br />
       as there are subtle syntactic differences, e.g. when parameter interpo-<br />
       lation (using `%&#8217;) is required. Note that termcap names of the capabil-<br />
       ities have to be used with the `terminfo&#8217; command.<br />
       In many cases, where the arguments are valid in both terminfo and term-<br />
       unchanged (e.g. &#8221;).  The second (optional) tweak modifies all the win-<br />
       dow  termcaps,  and  should contain definitions that screen understands<br />
       (see the &#8220;VIRTUAL TERMINAL&#8221; section).</p>
<p>       Some examples:</p>
<p>              termcap xterm*  LP:hs@</p>
<p>       Informs screen that all terminals that begin  with  `xterm&#8217;  have  firm<br />
       auto-margins  that  allow the last position on the screen to be updated<br />
       (LP), but they don&#8217;t really have a status line (no &#8216;hs&#8217; &#8211; append `@&#8217; to<br />
       turn  entries  off).   Note  that we assume `LP&#8217; for all terminal names<br />
       that start with &#8220;vt&#8221;, but only if you don&#8217;t specify a  termcap  command<br />
       for that terminal.</p>
<p>              termcap vt*  LP<br />
              termcap vt102|vt220  Z0=\E[?3h:Z1=\E[?3l</p>
<p>       Specifies  the  firm-margined  `LP&#8217;  capability  for all terminals that<br />
       begin with `vt&#8217;, and the second line will also add the escape-sequences<br />
       to switch into (Z0) and back out of (Z1) 132-character-per-line mode if<br />
       this is a VT102 or VT220.  (You must specify Z0 and Z1 in your  termcap<br />
       to use the width-changing commands.)</p>
<p>              termcap vt100  &#8220;&#8221;  l0=PF1:l1=PF2:l2=PF3:l3=PF4</p>
<p>       This  leaves  your vt100 termcap alone and adds the function key labels<br />
       to each window&#8217;s termcap entry.</p>
<p>              termcap h19|z19  am@:im=\E@:ei=\EO  dc=\E[P</p>
<p>       Takes a h19 or z19 termcap and turns off auto-margins (am@) and enables<br />
       the  insert  mode (im) and end-insert (ei) capabilities (the `@&#8217; in the<br />
       `im&#8217; string is after the `=&#8217;, so it is part of the string).  Having the<br />
       `im&#8217;  and  `ei&#8217; definitions put into your terminal&#8217;s termcap will cause<br />
       screen to automatically advertise the  character-insert  capability  in<br />
       each  window&#8217;s termcap.  Each window will also get the delete-character<br />
       capability (dc) added to its termcap, which screen will translate  into<br />
       a  line-update  for  the  terminal (we&#8217;re pretending it doesn&#8217;t support<br />
       character deletion).</p>
<p>       If you would like to fully specify each  window&#8217;s  termcap  entry,  you<br />
       should  instead  set  the  $SCREENCAP variable prior to running screen.<br />
       See the discussion on the &#8220;VIRTUAL TERMINAL&#8221; in this  manual,  and  the<br />
       <B>termcap(5)</B> man page for more information on termcap definitions.</p>
<p>       time [string]</p>
<p>       Uses  the  message  line to display the time of day, the host name, and<br />
       the load averages over 1, 5, and 15 minutes (if this  is  available  on<br />
       your system).  For window specific information use &#8220;info&#8221;.</p>
<p>       utf8 [on|off [on|off]]</p>
<p>       Change the encoding used in the current window. If utf8 is enabled, the<br />
       strings sent to the window will be UTF-8 encoded and vice versa.  Omit-<br />
       ting the parameter toggles the setting. If a second parameter is given,<br />
       the display&#8217;s encoding is also changed (this should rather be done with<br />
       screen&#8217;s  &#8220;-U&#8221;  option).  See also &#8220;defutf8&#8221;, which changes the default<br />
       setting of a new window.</p>
<p>       vbell [on|off]</p>
<p>       Sets the visual bell setting for this window.  Omitting  the  parameter<br />
       toggles  the  setting.  If vbell is switched on, but your terminal does<br />
       not support a visual bell, a `vbell-message&#8217; is displayed in the status<br />
       line  when the bell character (^G) is received.  Visual bell support of<br />
       a terminal is defined by the termcap variable `vb&#8217; (terminfo: &#8216;flash&#8217;).<br />
       Per  default,  vbell  is  off, thus the audible bell is used.  See also<br />
       `bell_msg&#8217;.</p>
<p>       vbell_msg [message]</p>
<p>       Sets the visual bell message. message is printed to the status line  if<br />
       the  window  receives  a bell character (^G), vbell is set to &#8220;on&#8221;, but<br />
       the terminal does not support a visual bell.  The  default  message  is<br />
       &#8220;Wuff, Wuff!!&#8221;.  Without parameter, the current message is shown.</p>
<p>       vbellwait sec</p>
<p>       Define  a  delay  in seconds after each display of screen&#8217;s visual bell<br />
       message. The default is 1 second.</p>
<p>       verbose [on|off]</p>
<p>       If verbose is switched on, the command name is echoed, whenever a  win-<br />
       dow  is  created  (or  resurrected  from zombie state). Default is off.<br />
       Without parameter, the current setting is shown.</p>
<p>       version</p>
<p>       Print the current version and the compile date in the status line.</p>
<p>       wall message</p>
<p>       Write a message to all displays. The message will appear in the  termi-<br />
       nal&#8217;s status line.</p>
<p>       width [-w|-d] [cols [lines]]</p>
<p>       Toggle  the  window  width between 80 and 132 columns or set it to cols<br />
       columns if an argument is specified.  This requires a capable  terminal<br />
       and  the  termcap entries &#8220;Z0&#8221; and &#8220;Z1&#8221;.  See the &#8220;termcap&#8221; command for<br />
       more information. You can also specify a new  height  if  you  want  to</p>
<p>       The table format can be changed with the string and title  option,  the<br />
       title  is displayed as table heading, while the lines are made by using<br />
       the string setting. The default setting is &#8220;Num  Name%=Flags&#8221;  for  the<br />
       title and &#8220;%3n %t%=%f&#8221; for the lines.  See the &#8220;STRING ESCAPES&#8221; chapter<br />
       for more codes (e.g. color settings).</p>
<p>       windows</p>
<p>       Uses the message line to display a list of all the windows.  Each  win-<br />
       dow  is listed by number with the name of process that has been started<br />
       in the window (or its title); the current window is marked with a  `*&#8217;;<br />
       the  previous  window  is  marked  with a `-&#8216;; all the windows that are<br />
       &#8220;logged in&#8221; are marked  with  a  `$&#8217;;  a  background  window  that  has<br />
       received a bell is marked with a `!&#8217;; a background window that is being<br />
       monitored and has had activity occur is marked with an  `@&#8217;;  a  window<br />
       which  has output logging turned on is marked with `(L)&#8217;; windows occu-<br />
       pied by other users are marked with `&amp;&#8217;; windows in  the  zombie  state<br />
       are marked with `Z&#8217;.  If this list is too long to fit on the terminal&#8217;s<br />
       status line only the portion around the current window is displayed.</p>
<p>       wrap [on|off]</p>
<p>       Sets the line-wrap setting for the current window.  When  line-wrap  is<br />
       on,  the second consecutive printable character output at the last col-<br />
       umn of a line will wrap to the start of  the  following  line.   As  an<br />
       added feature, backspace (^H) will also wrap through the left margin to<br />
       the previous line.  Default is `on&#8217;.</p>
<p>       writebuf [-e encoding] [filename]</p>
<p>       Writes the contents of the paste buffer to the specified file,  or  the<br />
       public accessible screen-exchange file if no filename is given. This is<br />
       thought of as a primitive means of communication between  screen  users<br />
       on  the  same  host.  If  an  encoding is specified the paste buffer is<br />
       recoded on the fly to match the encoding.  The filename can be set with<br />
       the bufferfile command and defaults to &#8220;/tmp/screen-exchange&#8221;.</p>
<p>       writelock [on|off|auto]</p>
<p>       In addition to access control lists, not all users may be able to write<br />
       to the same window at once. Per default, writelock is  in  `auto&#8217;  mode<br />
       and  grants  exclusive input permission to the user who is the first to<br />
       switch to the particular window. When he leaves the window, other users<br />
       may  obtain the writelock (automatically). The writelock of the current<br />
       window is disabled by the command &#8220;writelock off&#8221;. If the  user  issues<br />
       the  command  &#8220;writelock  on&#8221;  he  keeps the exclusive write permission<br />
       while switching to other windows.</p>
<p>       xoff<br />
       xon</p>
<p>       You can define the templates screen uses in &#8220;catch&#8221; mode via the second<br />
       and the third form.<br />
       Note also that this is an experimental feature.</p>
<p>       zombie [keys[onerror]]<br />
       defzombie [keys]</p>
<p>       Per default screen windows are removed from the window list as soon  as<br />
       the  windows  process  (e.g. shell) exits. When a string of two keys is<br />
       specified to the zombie command, `dead&#8217;  windows  will  remain  in  the<br />
       list.   The  kill command may be used to remove such a window. Pressing<br />
       the first key in the dead window has the same effect. When pressing the<br />
       second  key,  screen  will attempt to resurrect the window. The process<br />
       that was initially running in the window will be launched again.  Call-<br />
       ing  zombie without parameters will clear the zombie setting, thus mak-<br />
       ing windows disappear when their process exits.</p>
<p>       As the zombie-setting is manipulated globally  for  all  windows,  this<br />
       command  should  only  be called defzombie. Until we need this as a per<br />
       window setting, the commands zombie and defzombie are synonymous.</p>
<p>       Optionally you can put the word &#8220;onerror&#8221; after  the  keys.  This  will<br />
       cause  screen to monitor exit status of the process running in the win-<br />
       dow. If it exits normally (&#8216;0&#8217;), the window disappears. Any other  exit<br />
       value causes the window to become a zombie.</p>
<p>THE MESSAGE LINE<br />
       Screen  displays informational messages and other diagnostics in a mes-<br />
       sage line.  While this line is distributed to appear at the  bottom  of<br />
       the screen, it can be defined to appear at the top of the screen during<br />
       compilation.  If your terminal has a status line defined in  its  term-<br />
       cap, screen will use this for displaying its messages, otherwise a line<br />
       of the current screen will be temporarily overwritten and  output  will<br />
       be  momentarily  interrupted. The message line is automatically removed<br />
       after a few seconds delay, but it can also be removed early (on  termi-<br />
       nals without a status line) by beginning to type.</p>
<p>       The  message line facility can be used by an application running in the<br />
       current window by means of the ANSI Privacy message  control  sequence.<br />
       For instance, from within the shell, try something like:</p>
<p>              echo &#8216;&lt;esc&gt;^Hello world from window &#8216;$WINDOW'&lt;esc&gt;\\&#8217;</p>
<p>       where  &#8216;&lt;esc&gt;&#8217;  is an escape, &#8216;^&#8217; is a literal up-arrow, and &#8216;\\&#8217; turns<br />
       into a single backslash.</p>
<p>WINDOW TYPES<br />
       Screen provides three different window types. New windows  are  created<br />
       with screen&#8217;s screen command (see also the entry in chapter &#8220;CUSTOMIZA-<br />
       TION&#8221;). The first parameter to the screen command defines which type of<br />
          an  exclusive  open  is attempted on the node to mark the connection<br />
          line as busy.  An optional parameter  is  allowed  consisting  of  a<br />
          comma separated list of flags in the notation used by <B>stty(1)</B>:</p>
<p>          &lt;baud_rate&gt;<br />
                 Usually  300,  1200, 9600 or 19200. This affects transmission<br />
                 as well as receive speed.</p>
<p>          cs8 or cs7<br />
                 Specify the transmission of eight (or seven) bits per byte.</p>
<p>          ixon or -ixon<br />
                 Enables (or disables) software  flow-control  (CTRL-S/CTRL-Q)<br />
                 for sending data.</p>
<p>          ixoff or -ixoff<br />
                 Enables  (or  disables)  software  flow-control for receiving<br />
                 data.</p>
<p>          istrip or -istrip<br />
                 Clear (or keep) the eight bit in each received byte.</p>
<p>          You may want to specify as many  of  these  options  as  applicable.<br />
          Unspecified options cause the terminal driver to make up the parame-<br />
          ter values of the connection.  These values are system dependent and<br />
          may be in defaults or values saved from a previous connection.</p>
<p>          For  tty  windows,  the info command shows some of the modem control<br />
          lines in the status line. These may  include  `RTS&#8217;,  `CTS&#8217;,  &#8216;DTR&#8217;,<br />
          `DSR&#8217;,  `CD&#8217;  and more.  This depends on the available ioctl()&#8217;s and<br />
          system header files as well as the on the physical  capabilities  of<br />
          the  serial  board.   Signals  that  are logical low (inactive) have<br />
          their name preceded by an exclamation mark (!), otherwise the signal<br />
          is logical high (active).  Signals not supported by the hardware but<br />
          available to the ioctl() interface are usually shown low.<br />
          When the CLOCAL status bit is true, the whole set of  modem  signals<br />
          is  placed inside curly braces ({ and }).  When the CRTSCTS or TIOC-<br />
          SOFTCAR bit is set, the signals `CTS&#8217; or `CD&#8217; are shown in parenthe-<br />
          sis, respectively.</p>
<p>          For tty windows, the command break causes the Data transmission line<br />
          (TxD) to go low for a specified period of time. This is expected  to<br />
          be  interpreted  as break signal on the other side.  No data is sent<br />
          and no modem control line is changed when a break is issued.</p>
<p>       o  If the first  parameter  is  &#8220;//telnet&#8221;,  the  second  parameter  is<br />
          expected  to  be  a  host  name, and an optional third parameter may<br />
          specify a TCP port number (default decimal 23).  Screen will connect<br />
          to a server listening on the remote host and use the telnet protocol<br />
          to communicate with that server.<br />
          For telnet windows, the command info shows details about the connec-</p>
<p>          f      LFLOW.  The  remote  host will send flow control information.<br />
                 (Ignored at the moment.)</p>
<p>          Additional flags for debugging are x, t and n (XDISPLOC, TSPEED  and<br />
          NEWENV).</p>
<p>          For  telnet  windows,  the  command  break sends the telnet code IAC<br />
          BREAK (decimal 243) to the remote host.</p>
<p>          This window type is only available if screen was compiled  with  the<br />
          BUILTIN_TELNET option defined.</p>
<p>STRING ESCAPES<br />
       Screen provides an escape mechanism to insert information like the cur-<br />
       rent time into messages or file names. The escape character is &#8216;%&#8217; with<br />
       one  exception:  inside  of  a  window&#8217;s hardstatus &#8216;^%&#8217; (&#8216;^E&#8217;) is used<br />
       instead.</p>
<p>       Here is the full list of supported escapes:</p>
<p>       %      the escape character itself</p>
<p>       a      either &#8216;am&#8217; or &#8216;pm&#8217;</p>
<p>       A      either &#8216;AM&#8217; or &#8216;PM&#8217;</p>
<p>       c      current time HH:MM in 24h format</p>
<p>       C      current time HH:MM in 12h format</p>
<p>       d      day number</p>
<p>       D      weekday name</p>
<p>       f      flags of the window</p>
<p>       F      sets %? to true if the window has the focus</p>
<p>       h      hardstatus of the window</p>
<p>       H      hostname of the system</p>
<p>       l      current load of the system</p>
<p>       m      month number</p>
<p>       M      month name</p>
<p>       y      last two digits of the year number</p>
<p>       Y      full year number</p>
<p>       ?      the part to the next &#8216;%?&#8217; is displayed  only  if  a  &#8216;%&#8217;  escape<br />
              inside the part expands to a non-empty string</p>
<p>       :      else part of &#8216;%?&#8217;</p>
<p>       =      pad  the  string to the display&#8217;s width (like TeX&#8217;s hfill). If a<br />
              number is specified, pad  to  the  percentage  of  the  window&#8217;s<br />
              width.   A  &#8216;0&#8217;  qualifier  tells  screen to treat the number as<br />
              absolute position.  You can specify to pad relative to the  last<br />
              absolute  pad position by adding a &#8216;+&#8217; qualifier or to pad rela-<br />
              tive to the right margin by using &#8216;-&#8216;. The padding truncates the<br />
              string  if  the specified position lies before the current posi-<br />
              tion. Add the &#8216;L&#8217; qualifier to change this.</p>
<p>       &lt;      same as &#8216;%=&#8217; but just do truncation, do not fill with spaces</p>
<p>       &gt;      mark the current text position for  the  next  truncation.  When<br />
              screen  needs  to do truncation, it tries to do it in a way that<br />
              the marked position gets moved to the  specified  percentage  of<br />
              the  output  area.  (The  area starts from the last absolute pad<br />
              position and ends with the position specified by the  truncation<br />
              operator.)  The &#8216;L&#8217; qualifier tells screen to mark the truncated<br />
              parts with &#8216;&#8230;&#8217;.</p>
<p>       {      attribute/color modifier string terminated by the next &#8220;}&#8221;</p>
<p>       `      Substitute with the output of a &#8216;backtick&#8217; command.  The  length<br />
              qualifier is misused to identify one of the commands.</p>
<p>       The  &#8216;c&#8217;  and &#8216;C&#8217; escape may be qualified with a &#8216;0&#8217; to make screen use<br />
       zero instead of space as fill character. The &#8216;0&#8217; qualifier  also  makes<br />
       the  &#8216;=&#8217;  escape use absolute positions. The &#8216;n&#8217; and &#8216;=&#8217; escapes under-<br />
       stand a length qualifier (e.g. &#8216;%3n&#8217;), &#8216;D&#8217; and &#8216;M&#8217; can be prefixed with<br />
       &#8216;L&#8217;  to  generate long names, &#8216;w&#8217; and &#8216;W&#8217; also show the window flags if<br />
       &#8216;L&#8217; is given.</p>
<p>       An attribute/color modifier is is used to change the attributes or  the<br />
       color  settings.  Its  format  is &#8220;[attribute modifier] [color descrip-<br />
       tion]&#8221;. The attribute modifier must be prefixed by a change type  indi-<br />
       cator  if  it  can  be confused with a color description. The following<br />
       change types are known:</p>
<p>       +      add the specified set to the current attributes</p>
<p>       &#8211;      remove the set from the current attributes</p>
<p>       !      invert the set in the current attributes</p>
<p>       following colors are known:</p>
<p>       k      black<br />
       r      red<br />
       g      green<br />
       y      yellow<br />
       b      blue<br />
       m      magenta<br />
       c      cyan<br />
       w      white<br />
       d      default color<br />
       .      leave color unchanged</p>
<p>       The  capitalized  versions of the letter specify bright colors. You can<br />
       also use the pseudo-color &#8216;i&#8217; to set just the brightness and leave  the<br />
       color unchanged.<br />
       A  one digit/letter color description is treated as foreground or back-<br />
       ground color dependent on the current attributes: if  reverse  mode  is<br />
       set,  the  background color is changed instead of the foreground color.<br />
       If you don&#8217;t like this, prefix the color with a &#8220;.&#8221;. If  you  want  the<br />
       same  behavior for two-letter color descriptions, also prefix them with<br />
       a &#8220;.&#8221;.<br />
       As a special case, &#8220;%{-}&#8221; restores the attributes and colors that  were<br />
       set before the last change was made (i.e., pops one level of the color-<br />
       change stack).</p>
<p>       Examples:</p>
<p>       &#8220;G&#8221;    set color to bright green</p>
<p>       &#8220;+b r&#8221; use bold red</p>
<p>       &#8220;= yd&#8221; clear all attributes, write in default  color  on  yellow  back-<br />
              ground.</p>
<p>       %-Lw%{= BW}%50&gt;%n%f* %t%{-}%+Lw%&lt;<br />
              The  available  windows centered at the current window and trun-<br />
              cated to the available width. The current  window  is  displayed<br />
              white  on  blue.   This can be used with &#8220;hardstatus alwayslast-<br />
              line&#8221;.</p>
<p>       %?%F%{.R.}%?%3n %t%? [%h]%?<br />
              The window number and title and the window&#8217;s hardstatus, if  one<br />
              is  set.  Also use a red background if this is the active focus.<br />
              Useful for &#8220;caption string&#8221;.</p>
<p>FLOW-CONTROL<br />
       Each window has a flow-control setting that determines how screen deals<br />
       with the XON and XOFF characters (and perhaps the interrupt character).<br />
       When flow-control is turned off, screen ignores the XON and XOFF  char-<br />
       acters,  which  allows  the user to send them to the current program by<br />
       simply typing them (useful for the emacs editor,  for  instance).   The</p>
<p>       The automatic flow-switching mode deals with  flow  control  using  the<br />
       TIOCPKT  mode  (like &#8220;rlogin&#8221; does). If the tty driver does not support<br />
       TIOCPKT, screen tries to find out the right mode based on  the  current<br />
       setting of the application keypad &#8211; when it is enabled, flow-control is<br />
       turned off and visa versa.  Of course, you can still  manipulate  flow-<br />
       control manually when needed.</p>
<p>       If  you&#8217;re running with flow-control enabled and find that pressing the<br />
       interrupt key (usually  C-c)  does  not  interrupt  the  display  until<br />
       another 6-8 lines have scrolled by, try running screen with the &#8220;inter-<br />
       rupt&#8221; option (add the &#8220;interrupt&#8221; flag to the &#8220;flow&#8221;  command  in  your<br />
       .screenrc,  or use the -i command-line option).  This causes the output<br />
       that screen has accumulated from the interrupted program to be flushed.<br />
       One  disadvantage  is  that  the virtual terminal&#8217;s memory contains the<br />
       non-flushed version of the output, which in rare cases can cause  minor<br />
       inaccuracies  in  the  output.   For example, if you switch screens and<br />
       return, or update the screen with &#8220;C-a l&#8221; you would see the version  of<br />
       the  output  you would have gotten without &#8220;interrupt&#8221; being on.  Also,<br />
       you might need to turn off flow-control (or use auto-flow mode to  turn<br />
       it  off  automatically) when running a program that expects you to type<br />
       the interrupt character as input, as it is possible  to  interrupt  the<br />
       output of the virtual terminal to your physical terminal when flow-con-<br />
       trol is enabled.  If this happens, a simple refresh of the screen  with<br />
       &#8220;C-a  l&#8221; will restore it.  Give each mode a try, and use whichever mode<br />
       you find more comfortable.</p>
<p>TITLES (naming windows)<br />
       You can customize each window&#8217;s name in the window display (viewed with<br />
       the &#8220;windows&#8221; command (C-a w)) by setting it with one of the title com-<br />
       mands.  Normally the name displayed is the actual command name  of  the<br />
       program created in the window.  However, it is sometimes useful to dis-<br />
       tinguish various programs of the same name or to change  the  name  on-<br />
       the-fly to reflect the current state of the window.</p>
<p>       The default name for all shell windows can be set with the &#8220;shelltitle&#8221;<br />
       command in the .screenrc file, while all other windows are created with<br />
       a &#8220;screen&#8221; command and thus can have their name set with the -t option.<br />
       Interactively,    there    is    the    title-string    escape-sequence<br />
       (&lt;esc&gt;kname&lt;esc&gt;\)  and the &#8220;title&#8221; command (C-a A).  The former can be<br />
       output from an application to control the window&#8217;s name under  software<br />
       control,  and  the  latter  will prompt for a name when typed.  You can<br />
       also bind pre-defined names to keys with the  &#8220;title&#8221;  command  to  set<br />
       things quickly without prompting.</p>
<p>       Finally,  screen has a shell-specific heuristic that is enabled by set-<br />
       ting the window&#8217;s name to &#8220;search|name&#8221; and arranging to  have  a  null<br />
       title escape-sequence output as a part of your prompt.  The search por-<br />
       tion specifies an end-of-prompt search string, while the  name  portion<br />
       specifies the default shell name for the window.  If the name ends in a<br />
       screen will use the first word on the  following  line  (if  found)  in<br />
       preference  to  the  just-found  name.  This helps csh users get better<br />
       command names when using job control or history recall commands.</p>
<p>       Here&#8217;s some .screenrc examples:</p>
<p>              screen -t top 2 nice top</p>
<p>       Adding this line to your .screenrc would start a nice-d version of  the<br />
       &#8220;top&#8221; command in window 2 named &#8220;top&#8221; rather than &#8220;nice&#8221;.</p>
<p>                   shelltitle &#8216;&gt; |csh&#8217;<br />
                   screen 1</p>
<p>       These  commands  would  start  a  shell with the given shelltitle.  The<br />
       title specified is an auto-title that would expect the prompt  and  the<br />
       typed command to look something like the following:</p>
<p>              /usr/joe/src/dir&gt; trn</p>
<p>       (it  looks  after  the  &#8216;&gt;  &#8216; for the command name).  The window status<br />
       would show the name &#8220;trn&#8221; while the command was running, and revert  to<br />
       &#8220;csh&#8221; upon completion.</p>
<p>              bind R screen -t &#8216;% |root:&#8217; su</p>
<p>       Having  this command in your .screenrc would bind the key sequence &#8220;C-a<br />
       R&#8221; to the &#8220;su&#8221; command and give it an auto-title name of &#8220;root:&#8221;.   For<br />
       this auto-title to work, the screen could look something like this:</p>
<p>                   % !em<br />
                   emacs file.c</p>
<p>       Here  the user typed the csh history command &#8220;!em&#8221; which ran the previ-<br />
       ously  entered  &#8220;emacs&#8221;  command.   The  window   status   would   show<br />
       &#8220;root:emacs&#8221;  during the execution of the command, and revert to simply<br />
       &#8220;root:&#8221; at its completion.</p>
<p>                   bind o title<br />
                   bind E title &#8220;&#8221;<br />
                   bind u title (unknown)</p>
<p>       The first binding doesn&#8217;t have any arguments, so it  would  prompt  you<br />
       for  a title. when you type &#8220;C-a o&#8221;.  The second binding would clear an<br />
       auto-title&#8217;s current setting (C-a E).  The third binding would set  the<br />
       current window&#8217;s title to &#8220;(unknown)&#8221; (C-a u).</p>
<p>       One  thing  to keep in mind when adding a null title-escape-sequence to<br />
       your prompt is that some shells (like the csh) count all  the  non-con-<br />
       trol  characters  as  part  of the prompt&#8217;s length.  If these invisible<br />
       characters aren&#8217;t a multiple of 8 then  backspacing  over  a  tab  will<br />
       result in an incorrect display.  One way to get around this is to use a</p>
<p>THE VIRTUAL TERMINAL<br />
       Each  window  in  a screen session emulates a VT100 terminal, with some<br />
       extra functions added. The VT100 emulator is hard-coded, no other  ter-<br />
       minal types can be emulated.<br />
       Usually  screen  tries to emulate as much of the VT100/ANSI standard as<br />
       possible. But if your terminal lacks certain capabilities,  the  emula-<br />
       tion  may not be complete. In these cases screen has to tell the appli-<br />
       cations that some of the features are missing. This is  no  problem  on<br />
       machines using termcap, because screen can use the $TERMCAP variable to<br />
       customize the standard screen termcap.</p>
<p>       But if you do a rlogin on another machine or your machine supports only<br />
       terminfo  this  method  fails.  Because of this, screen offers a way to<br />
       deal with these cases.  Here is how it works:</p>
<p>       When screen tries to figure out a terminal name for  itself,  it  first<br />
       looks  for an entry named &#8220;screen.&lt;term&gt;&#8221;, where &lt;term&gt; is the contents<br />
       of your $TERM variable.  If no such entry exists, screen tries &#8220;screen&#8221;<br />
       (or  &#8220;screen-w&#8221;  if  the terminal is wide (132 cols or more)).  If even<br />
       this entry cannot be found, &#8220;vt100&#8221; is used as a substitute.</p>
<p>       The idea is that if you have a terminal which doesn&#8217;t support an impor-<br />
       tant  feature  (e.g.  delete  char or clear to EOS) you can build a new<br />
       termcap/terminfo entry for screen (named &#8220;screen.&lt;dumbterm&gt;&#8221;) in  which<br />
       this  capability  has been disabled. If this entry is installed on your<br />
       machines you are able to do a rlogin and still keep the  correct  term-<br />
       cap/terminfo  entry.  The terminal name is put in the $TERM variable of<br />
       all new windows.  Screen also sets the $TERMCAP variable reflecting the<br />
       capabilities of the virtual terminal emulated. Notice that, however, on<br />
       machines using the terminfo database this variable has no effect.  Fur-<br />
       thermore, the variable $WINDOW is set to the window number of each win-<br />
       dow.</p>
<p>       The actual set  of  capabilities  supported  by  the  virtual  terminal<br />
       depends  on  the  capabilities supported by the physical terminal.  If,<br />
       for instance, the physical terminal does not support  underscore  mode,<br />
       screen  does  not  put the `us&#8217; and `ue&#8217; capabilities into the window&#8217;s<br />
       $TERMCAP variable, accordingly.  However, a minimum number of capabili-<br />
       ties  must  be  supported  by a terminal in order to run screen; namely<br />
       scrolling, clear screen, and direct  cursor  addressing  (in  addition,<br />
       screen  does  not  run on hardcopy terminals or on terminals that over-<br />
       strike).</p>
<p>       Also, you can customize the $TERMCAP value used by screen by using  the<br />
       &#8220;termcap&#8221;  .screenrc  command,  or  by defining the variable $SCREENCAP<br />
       prior to startup.  When the is latter defined, its value will be copied<br />
       verbatim  into each window&#8217;s $TERMCAP variable.  This can either be the<br />
       full terminal definition, or a filename  where  the  terminal  &#8220;screen&#8221;<br />
       (and/or &#8220;screen-w&#8221;) is defined.</p>
<p>       Note  that screen honors the &#8220;terminfo&#8221; .screenrc command if the system<br />
       character by character translation string that  is  used  during  semi-<br />
       graphics  mode.  This string is built like the `acsc&#8217; terminfo capabil-<br />
       ity.</p>
<p>       When the `po&#8217; and `pf&#8217; capabilities are present in the terminal&#8217;s term-<br />
       cap  entry,  applications running in a screen window can send output to<br />
       the printer port of the terminal.  This allows a user to have an appli-<br />
       cation  in one window sending output to a printer connected to the ter-<br />
       minal, while all other windows are still active (the  printer  port  is<br />
       enabled  and  disabled  again  for  each  chunk of output).  As a side-<br />
       effect, programs running in different windows can send  output  to  the<br />
       printer  simultaneously.   Data sent to the printer is not displayed in<br />
       the window.  The info command displays a line starting `PRIN&#8217; while the<br />
       printer is active.</p>
<p>       Screen  maintains  a hardstatus line for every window. If a window gets<br />
       selected, the display&#8217;s hardstatus will be updated to  match  the  win-<br />
       dow&#8217;s  hardstatus  line. If the display has no hardstatus the line will<br />
       be displayed as a standard screen message.  The hardstatus line can  be<br />
       changed    with   the   ANSI   Application   Program   Command   (APC):<br />
       &#8220;ESC_&lt;string&gt;ESC\&#8221;. As a  convenience  for  xterm  users  the  sequence<br />
       &#8220;ESC]0..2;&lt;string&gt;^G&#8221; is also accepted.</p>
<p>       Some  capabilities  are only put into the $TERMCAP variable of the vir-<br />
       tual terminal if they can be efficiently implemented  by  the  physical<br />
       terminal.  For instance, `dl&#8217; (delete line) is only put into the $TERM-<br />
       CAP variable if the terminal supports  either  delete  line  itself  or<br />
       scrolling  regions. Note that this may provoke confusion, when the ses-<br />
       sion is reattached on a different terminal, as the  value  of  $TERMCAP<br />
       cannot be modified by parent processes.</p>
<p>       The  &#8220;alternate  screen&#8221; capability is not enabled by default.  Set the<br />
       altscreen .screenrc command to enable it.</p>
<p>       The following is a list of  control  sequences  recognized  by  screen.<br />
       &#8220;(V)&#8221; and &#8220;(A)&#8221; indicate VT100-specific and ANSI- or ISO-specific func-<br />
       tions, respectively.</p>
<p>       ESC E                      Next Line</p>
<p>       ESC D                      Index</p>
<p>       ESC M                      Reverse Index</p>
<p>       ESC H                      Horizontal Tab Set</p>
<p>       ESC Z                      Send VT100 Identification String</p>
<p>       ESC 7                 (V)  Save Cursor and Attributes</p>
<p>       ESC 8                 (V)  Restore Cursor and Attributes</p>
<p>       ESC =                 (V)  Application Keypad Mode</p>
<p>       ESC &gt;                 (V)  Numeric Keypad Mode</p>
<p>       ESC # 8               (V)  Fill Screen with E&#8217;s</p>
<p>       ESC \                 (A)  String Terminator</p>
<p>       ESC ^                 (A)  Privacy Message String (Message Line)</p>
<p>       ESC !                      Global Message String (Message Line)</p>
<p>       ESC k                      A.k.a. Definition String</p>
<p>       ESC P                 (A)  Device Control  String.   Outputs  a  string<br />
                                  directly to the host terminal without inter-<br />
                                  pretation.</p>
<p>       ESC _                 (A)  Application Program Command (Hardstatus)</p>
<p>       ESC ] 0 ; string ^G   (A)  Operating System Command (Hardstatus,  xterm<br />
                                  title hack)</p>
<p>       ESC ] 83 ; cmd ^G     (A)  Execute  screen  command. This only works if<br />
                                  multi-user support is compiled into  screen.<br />
                                  The  pseudo-user &#8220;:window:&#8221; is used to check<br />
                                  the access control list. Use  &#8220;addacl  :win-<br />
                                  dow:  -rwx  #?&#8221;  to  create  a  user with no<br />
                                  rights and allow only the needed commands.</p>
<p>       Control-N             (A)  Lock Shift G1 (SO)</p>
<p>       Control-O             (A)  Lock Shift G0 (SI)</p>
<p>       ESC n                 (A)  Lock Shift G2</p>
<p>       ESC o                 (A)  Lock Shift G3</p>
<p>       ESC N                 (A)  Single Shift G2</p>
<p>       ESC O                 (A)  Single Shift G3</p>
<p>       ESC ( Pcs             (A)  Designate character set as G0</p>
<p>       ESC ) Pcs             (A)  Designate character set as G1</p>
<p>       ESC * Pcs             (A)  Designate character set as G2</p>
<p>       ESC + Pcs             (A)  Designate character set as G3</p>
<p>       ESC [ Pn ; Pn H            Direct Cursor Addressing</p>
<p>                  1               From Beginning of Line to Cursor</p>
<p>                  2               Entire Line</p>
<p>       ESC [ Pn X                 Erase character</p>
<p>       ESC [ Pn A                 Cursor Up</p>
<p>       ESC [ Pn B                 Cursor Down</p>
<p>       ESC [ Pn C                 Cursor Right</p>
<p>       ESC [ Pn D                 Cursor Left</p>
<p>       ESC [ Pn E                 Cursor next line</p>
<p>       ESC [ Pn F                 Cursor previous line</p>
<p>       ESC [ Pn G                 Cursor horizontal position</p>
<p>       ESC [ Pn `                 same as above</p>
<p>       ESC [ Pn d                 Cursor vertical position</p>
<p>       ESC [ Ps ;&#8230;; Ps m        Select Graphic Rendition</p>
<p>             Ps = None or 0       Default Rendition</p>
<p>                  1               Bold</p>
<p>                  2          (A)  Faint</p>
<p>                  3          (A)  Standout Mode (ANSI: Italicized)</p>
<p>                  4               Underlined</p>
<p>                  5               Blinking</p>
<p>                  7               Negative Image</p>
<p>                  22         (A)  Normal Intensity</p>
<p>                  23         (A)  Standout Mode off (ANSI: Italicized off)</p>
<p>                  24         (A)  Not Underlined</p>
<p>                  25         (A)  Not Blinking</p>
<p>                  27         (A)  Positive Image</p>
<p>                  30         (A)  Foreground Black</p>
<p>                  39         (A)  Foreground Default</p>
<p>                  40         (A)  Background Black</p>
<p>                  &#8230;             &#8230;</p>
<p>                  49         (A)  Background Default</p>
<p>       ESC [ Pn g                 Tab Clear</p>
<p>             Pn = None or 0       Clear Tab at Current Position</p>
<p>                  3               Clear All Tabs</p>
<p>       ESC [ Pn ; Pn r       (V)  Set Scrolling Region</p>
<p>       ESC [ Pn I            (A)  Horizontal Tab</p>
<p>       ESC [ Pn Z            (A)  Backward Tab</p>
<p>       ESC [ Pn L            (A)  Insert Line</p>
<p>       ESC [ Pn M            (A)  Delete Line</p>
<p>       ESC [ Pn @            (A)  Insert Character</p>
<p>       ESC [ Pn P            (A)  Delete Character</p>
<p>       ESC [ Pn S                 Scroll Scrolling Region Up</p>
<p>       ESC [ Pn T                 Scroll Scrolling Region Down</p>
<p>       ESC [ Pn ^                 same as above</p>
<p>       ESC [ Ps ;&#8230;; Ps h        Set Mode</p>
<p>       ESC [ Ps ;&#8230;; Ps l        Reset Mode</p>
<p>             Ps = 4          (A)  Insert Mode</p>
<p>                  20         (A)  Automatic Linefeed Mode</p>
<p>                  34              Normal Cursor Visibility</p>
<p>                  ?1         (V)  Application Cursor Keys</p>
<p>                  ?3         (V)  Change Terminal Width to 132 columns</p>
<p>                  ?5         (V)  Reverse Video</p>
<p>                  ?6         (V)  Origin Mode</p>
<p>       ESC [ 5 i             (A)  Start relay to printer (ANSI Media Copy)</p>
<p>       ESC [ 4 i             (A)  Stop relay to printer (ANSI Media Copy)</p>
<p>       ESC [ 8 ; Ph ; Pw t        Resize the window to  `Ph&#8217;  lines  and  `Pw&#8217;<br />
                                  columns (SunView special)</p>
<p>       ESC [ c                    Send VT100 Identification String</p>
<p>       ESC [ x                    Send Terminal Parameter Report</p>
<p>       ESC [ &gt; c                  Send   VT220   Secondary  Device  Attributes<br />
                                  String</p>
<p>       ESC [ 6 n                  Send Cursor Position Report</p>
<p>INPUT TRANSLATION<br />
       In order to do a full VT100 emulation  screen  has  to  detect  that  a<br />
       sequence  of characters in the input stream was generated by a keypress<br />
       on the user&#8217;s keyboard and insert  the  VT100  style  escape  sequence.<br />
       Screen  has  a very flexible way of doing this by making it possible to<br />
       map arbitrary commands on arbitrary sequences of characters. For  stan-<br />
       dard  VT100  emulation  the  command will always insert a string in the<br />
       input buffer of the window (see also command stuff in the  command  ta-<br />
       ble).  Because the sequences generated by a keypress can change after a<br />
       reattach from a different terminal type, it is possible  to  bind  com-<br />
       mands  to the termcap name of the keys.  Screen will insert the correct<br />
       binding after each  reattach.  See  the  bindkey  command  for  further<br />
       details on the syntax and examples.</p>
<p>       Here  is the table of the default key bindings. (A) means that the com-<br />
       mand is executed if the keyboard is switched into application mode.</p>
<p>       Key name          Termcap name    Command<br />
       ______________________________________________________<br />
       Cursor up             ku          stuff 33[A<br />
                                         stuff 33OA    (A)<br />
       Cursor down           kd          stuff 33[B<br />
                                         stuff 33OB    (A)<br />
       Cursor right          kr          stuff 33[C<br />
                                         stuff 33OC    (A)<br />
       Cursor left           kl          stuff 33[D<br />
                                         stuff 33OD    (A)<br />
       Function key 0        k0          stuff 33[10~<br />
       Function key 1        k1          stuff 33OP<br />
       Function key 2        k2          stuff 33OQ<br />
       Function key 3        k3          stuff 33OR<br />
       Function key 4        k4          stuff 33OS<br />
       Function key 5        k5          stuff 33[15~<br />
                                         stuff 33Op    (A)<br />
       Keypad 1              f1          stuff 1<br />
                                         stuff 33Oq    (A)<br />
       Keypad 2              f2          stuff 2<br />
                                         stuff 33Or    (A)<br />
       Keypad 3              f3          stuff 3<br />
                                         stuff 33Os    (A)<br />
       Keypad 4              f4          stuff 4<br />
                                         stuff 33Ot    (A)<br />
       Keypad 5              f5          stuff 5<br />
                                         stuff 33Ou    (A)<br />
       Keypad 6              f6          stuff 6<br />
                                         stuff 33Ov    (A)<br />
       Keypad 7              f7          stuff 7<br />
                                         stuff 33Ow    (A)<br />
       Keypad 8              f8          stuff 8<br />
                                         stuff 33Ox    (A)<br />
       Keypad 9              f9          stuff 9<br />
                                         stuff 33Oy    (A)<br />
       Keypad +              f+          stuff +<br />
                                         stuff 33Ok    (A)<br />
       Keypad &#8211;              f-          stuff &#8211;<br />
                                         stuff 33Om    (A)<br />
       Keypad *              f*          stuff *<br />
                                         stuff 33Oj    (A)<br />
       Keypad /              f/          stuff /<br />
                                         stuff 33Oo    (A)<br />
       Keypad =              fq          stuff =<br />
                                         stuff 33OX    (A)<br />
       Keypad .              f.          stuff .<br />
                                         stuff 33On    (A)<br />
       Keypad ,              f,          stuff ,<br />
                                         stuff 33Ol    (A)<br />
       Keypad enter          fe          stuff 15<br />
                                         stuff 33OM    (A)</p>
<p>SPECIAL TERMINAL CAPABILITIES<br />
       The following table describes all terminal capabilities that are recog-<br />
       nized  by  screen  and are not in the <B>termcap(5)</B> manual.  You can place<br />
       these capabilities in your termcap entries (in `/etc/termcap&#8217;)  or  use<br />
       them  with the commands `termcap&#8217;, `terminfo&#8217; and `termcapinfo&#8217; in your<br />
       screenrc files. It is often not possible to place these capabilities in<br />
       the terminfo database.</p>
<p>       LP   (bool)  Terminal  has  VT100 style margins (`magic margins&#8217;). Note<br />
                    that this capability is obsolete because screen  uses  the<br />
                    standard &#8216;xn&#8217; instead.</p>
<p>       Z0   (str)   Change width to 132 columns.</p>
<p>       E0   (str)   Switch charset &#8216;G0&#8217; back to standard charset.  Default  is<br />
                    &#8216;\E(B&#8217;.</p>
<p>       C0   (str)   Use the string as a conversion table for font &#8216;0&#8217;. See the<br />
                    &#8216;ac&#8217; capability for more details.</p>
<p>       CS   (str)   Switch cursor-keys to application mode.</p>
<p>       CE   (str)   Switch cursor-keys back to normal mode.</p>
<p>       AN   (bool)  Turn on autonuke. See  the  &#8216;autonuke&#8217;  command  for  more<br />
                    details.</p>
<p>       OL   (num)   Set  the  output buffer limit. See the &#8216;obuflimit&#8217; command<br />
                    for more details.</p>
<p>       KJ   (str)   Set the encoding of the terminal. See the &#8216;encoding&#8217;  com-<br />
                    mand for valid encodings.</p>
<p>       AF   (str)   Change  character foreground color in an ANSI conform way.<br />
                    This capability will almost always  be  set  to  &#8216;\E[3%dm&#8217;<br />
                    (&#8216;\E[3%p1%dm&#8217; on terminfo machines).</p>
<p>       AB   (str)   Same as &#8216;AF&#8217;, but change background color.</p>
<p>       AX   (bool)  Does  understand  ANSI  set  default fg/bg color (\E[39m /<br />
                    \E[49m).</p>
<p>       XC   (str)   Describe a translation of characters to strings  depending<br />
                    on  the  current  font.  More  details  follow in the next<br />
                    section.</p>
<p>       XT   (bool)  Terminal understands special xterm sequences  (OSC,  mouse<br />
                    tracking).</p>
<p>       C8   (bool)  Terminal needs bold to display high-intensity colors (e.g.<br />
                    Eterm).</p>
<p>       TF   (bool)  Add missing capabilities to the termcap/info  entry.  (Set<br />
                    by default).</p>
<p>CHARACTER TRANSLATION<br />
       Screen  has  a  powerful mechanism to translate characters to arbitrary<br />
       strings depending on the current font and terminal type.  Use this fea-<br />
       ture  if  you  want  to  work with a common standard character set (say<br />
       ISO8851-latin1) even on terminals that scatter the more unusual charac-<br />
       ters over several national language font pages.</p>
<p>       Syntax:<br />
           XC=&lt;charset-mapping&gt;{,,&lt;charset-mapping&gt;}</p>
<p>       make it possible to use a real &#8216;%&#8217;. The &#8216;\&#8217; character quotes  the  spe-<br />
       cial characters &#8216;\&#8217;, &#8216;%&#8217;, and &#8216;,&#8217;.</p>
<p>       Here is an example:</p>
<p>           termcap hp700 &#8216;XC=B\E(K%\E(B,\304[,\326\\\\,\334]&#8217;</p>
<p>       This  tells  screen how to translate ISOlatin1 (charset &#8216;B&#8217;) upper case<br />
       umlaut characters on a hp700 terminal that has a German charset. &#8216;\304&#8217;<br />
       gets  translated  to  &#8216;\E(K[\E(B&#8217;  and so on.  Note that this line gets<br />
       parsed *three* times before the internal lookup table is built,  there-<br />
       fore a lot of quoting is needed to create a single &#8216;\&#8217;.</p>
<p>       Another  extension  was  added  to  allow  more emulation: If a mapping<br />
       translates the unquoted &#8216;%&#8217; char, it will be sent to the terminal when-<br />
       ever screen switches to the corresponding &lt;designator&gt;. In this special<br />
       case the template is assumed to be just &#8216;%&#8217; because the charset  switch<br />
       sequence and the character mappings normally haven&#8217;t much in common.</p>
<p>       This example shows one use of the extension:</p>
<p>           termcap xterm &#8216;XC=K%,%\E(B,[\304,\\\\\326,]\334&#8217;</p>
<p>       Here,  a  part of the German (&#8216;K&#8217;) charset is emulated on an xterm.  If<br />
       screen has to change to the &#8216;K&#8217; charset, &#8216;\E(B&#8217; will  be  sent  to  the<br />
       terminal,  i.e. the ASCII charset is used instead. The template is just<br />
       &#8216;%&#8217;, so the mapping is straightforward: &#8216;[&#8216; to &#8216;\304&#8217;, &#8216;\&#8217;  to  &#8216;\326&#8217;,<br />
       and &#8216;]&#8217; to &#8216;\334&#8242;.</p>
<p>ENVIRONMENT<br />
       COLUMNS        Number  of  columns  on  the terminal (overrides termcap<br />
                      entry).<br />
       HOME           Directory in which to look for .screenrc.<br />
       LINES          Number of  lines  on  the  terminal  (overrides  termcap<br />
                      entry).<br />
       LOCKPRG        Screen lock program.<br />
       NETHACKOPTIONS Turns on nethack option.<br />
       PATH           Used for locating programs to run.<br />
       SCREENCAP      For customizing a terminal&#8217;s TERMCAP value.<br />
       SCREENDIR      Alternate socket directory.<br />
       SCREENRC       Alternate user screenrc file.<br />
       SHELL          Default  shell  program  for  opening  windows  (default<br />
                      &#8220;/bin/sh&#8221;).<br />
       STY            Alternate socket name.<br />
       SYSSCREENRC    Alternate system screenrc file.<br />
       TERM           Terminal name.<br />
       TERMCAP        Terminal description.<br />
       WINDOW         Window number of a window (at creation time).</p>
<p>FILES<br />
       &#8230;/screen-4.?.??/etc/screenrc<br />
                                         buffer&#8217;<br />
       hardcopy.[0-9]                    Screen images created by the hardcopy<br />
                                         function<br />
       screenlog.[0-9]                   Output  log  files created by the log<br />
                                         function<br />
       /usr/lib/terminfo/?/*             or<br />
       /etc/termcap                      Terminal capability databases<br />
       /var/run/utmp                     Login records<br />
       $LOCKPRG                          Program that locks a terminal.</p>
<p>SEE ALSO<br />
       <B>termcap(5)</B>, <B>utmp(5)</B>, <B>vi(1)</B>, <B>captoinfo(1)</B>, <B>tic(1)</B></p>
<p>AUTHORS<br />
       Originally created by Oliver Laumann, this latest version was  produced<br />
       by Wayne Davison, Juergen Weigert and Michael Schroeder.</p>
<p>COPYLEFT<br />
       Copyright (C) 1993-2003<br />
            Juergen Weigert (jnweiger@immd4.informatik.uni-erlangen.de)<br />
            Michael Schroeder (mlschroe@immd4.informatik.uni-erlangen.de)<br />
       Copyright (C) 1987 Oliver Laumann<br />
       This program is free software; you can redistribute it and/or modify it<br />
       under the terms of the GNU General Public License as published  by  the<br />
       Free  Software  Foundation;  either  version 2, or (at your option) any<br />
       later version.<br />
       This program is distributed in the hope that it  will  be  useful,  but<br />
       WITHOUT  ANY  WARRANTY;  without  even  the  implied  warranty  of MER-<br />
       CHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU  General<br />
       Public License for more details.<br />
       You should have received a copy of the GNU General Public License along<br />
       with this program (see the file COPYING); if not,  write  to  the  Free<br />
       Software  Foundation,  Inc.,  59  Temple  Place &#8211; Suite 330, Boston, MA<br />
       02111-1307, USA</p>
<p>CONTRIBUTORS<br />
       Ken Beal (kbeal@amber.ssd.csd.harris.com),<br />
       Rudolf Koenig (rfkoenig@immd4.informatik.uni-erlangen.de),<br />
       Toerless Eckert (eckert@immd4.informatik.uni-erlangen.de),<br />
       Wayne Davison (davison@borland.com),<br />
       Patrick Wolfe (pat@kai.com, kailand!pat),<br />
       Bart Schaefer (schaefer@cse.ogi.edu),<br />
       Nathan Glasser (nathan@brokaw.lcs.mit.edu),<br />
       Larry W. Virden (lvirden@cas.org),<br />
       Howard Chu (hyc@hanauma.jpl.nasa.gov),<br />
       Tim MacKenzie (tym@dibbler.cs.monash.edu.au),<br />
       Markku Jarvinen (mta@{cc,cs,ee}.tut.fi),<br />
       Marc Boucher (marc@CAM.ORG),<br />
       Doug Siebert (dsiebert@isca.uiowa.edu),<br />
       Ken Stillson (stillson@tsfsrv.mitre.org),</p>
<p>VERSION<br />
       This is version 4.0.2. Its roots are a merge of a custom version 2.3PR7<br />
       by  Wayne  Davison and several enhancements to Oliver Laumann&#8217;s version<br />
       2.0. Note that all versions numbered 2.x are copyright by  Oliver  Lau-<br />
       mann.</p>
<p>AVAILABILITY<br />
       The  latest official release of screen available via anonymous ftp from<br />
       gnudist.gnu.org, nic.funet.fi or any other GNU distribution  site.  The<br />
       home site of screen is ftp.uni-erlangen.de, in the directory pub/utili-<br />
       ties/screen. The subdirectory `private&#8217; contains the latest beta  test-<br />
       ing  release.  If  you  want  to help, send a note to screen@uni-erlan-<br />
       gen.de.</p>
<p>BUGS<br />
       o  `dm&#8217; (delete mode) and `xs&#8217; are  not  handled  correctly  (they  are<br />
          ignored). `xn&#8217; is treated as a magic-margin indicator.</p>
<p>       o  Screen has no clue about double-high or double-wide characters.  But<br />
          this is the only area where vttest is allowed to fail.</p>
<p>       o  It is not possible to change the environment variable $TERMCAP  when<br />
          reattaching under a different terminal type.</p>
<p>       o  The  support of terminfo based systems is very limited. Adding extra<br />
          capabilities to $TERMCAP may not have any effects.</p>
<p>       o  Screen does not make use of hardware tabs.</p>
<p>       o  Screen must be installed as set-uid with owner root on most  systems<br />
          in  order to be able to correctly change the owner of the tty device<br />
          file for each window.  Special permission may also  be  required  to<br />
          write the file &#8220;/var/run/utmp&#8221;.</p>
<p>       o  Entries  in  &#8220;/var/run/utmp&#8221;  are  not removed when screen is killed<br />
          with SIGKILL.  This will cause some programs (like &#8220;w&#8221; or &#8220;rwho&#8221;) to<br />
          advertise that a user is logged on who really isn&#8217;t.</p>
<p>       o  Screen may give a strange warning when your tty has no utmp entry.</p>
<p>       o  When the modem line was hung up, screen may not automatically detach<br />
          (or quit) unless the device driver is configured to  send  a  HANGUP<br />
          signal.   To  detach  a screen session use the -D or -d command line<br />
          option.</p>
<p>       o  If a password is set, the command  line  options  -d  and  -D  still<br />
          detach a session without asking.</p>
<p>       o  Both  &#8220;breaktype&#8221;  and  &#8220;defbreaktype&#8221;  change  the break generating<br />
          method used by all terminal devices. The first should change a  win-<br />
          dow  specific  setting,  where  the  latter  should  change only the</p>
<p>4th Berkeley Distribution          Aug 2003                          <B>SCREEN(1)</B><br />
</PRE></p>
]]></content:encoded>
					
					<wfw:commentRss>https://manpageaday.wordpress.com/2011/05/04/screen/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">179</post-id>
		<media:content url="https://1.gravatar.com/avatar/7e5a914fa78c2f8cff1b5a3a1e56626bd1af981cea33e799a05a752770013ffc?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">manpageaday</media:title>
		</media:content>
	</item>
	</channel>
</rss>
