ViewVC Help
View File | Revision Log | Show Annotations | Download File
/cvs/rxvt-unicode/doc/rxvt.1.html
(Generate patch)

Comparing rxvt-unicode/doc/rxvt.1.html (file contents):
Revision 1.41 by root, Wed Jan 11 02:13:55 2006 UTC vs.
Revision 1.45 by root, Fri Jan 13 12:40:46 2006 UTC

… …
41<p>rxvt-unicode (ouR XVT, unicode) - (a VT102 emulator for the X window system)</p> 41<p>rxvt-unicode (ouR XVT, unicode) - (a VT102 emulator for the X window system)</p>
42<p> 42<p>
43</p> 43</p>
44<hr /> 44<hr />
45<h1><a name="synopsis">SYNOPSIS</a></h1> 45<h1><a name="synopsis">SYNOPSIS</a></h1>
46<p><strong>rxvt</strong> [options] [-e command [ args ]]</p> 46<p><strong>urxvt</strong> [options] [-e command [ args ]]</p>
47<p> 47<p>
48</p> 48</p>
49<hr /> 49<hr />
50<h1><a name="description">DESCRIPTION</a></h1> 50<h1><a name="description">DESCRIPTION</a></h1>
51<p><strong>rxvt-unicode</strong>, version <strong>6.3</strong>, is a colour vt102 terminal 51<p><strong>rxvt-unicode</strong>, version <strong>7.0</strong>, is a colour vt102 terminal
52emulator intended as an <em>xterm</em>(1) replacement for users who do not 52emulator intended as an <em>xterm</em>(1) replacement for users who do not
53require features such as Tektronix 4014 emulation and toolkit-style 53require features such as Tektronix 4014 emulation and toolkit-style
54configurability. As a result, <strong>rxvt-unicode</strong> uses much less swap space -- 54configurability. As a result, <strong>rxvt-unicode</strong> uses much less swap space --
55a significant advantage on a machine serving many X sessions.</p> 55a significant advantage on a machine serving many X sessions.</p>
56<p> 56<p>
57</p> 57</p>
58<hr /> 58<hr />
59<h1><a name="frequently_asked_questions">FREQUENTLY ASKED QUESTIONS</a></h1> 59<h1><a name="frequently_asked_questions">FREQUENTLY ASKED QUESTIONS</a></h1>
60<p>See <code>rxvt(7)</code> (try <code>man 7 rxvt</code>) for a list of 60<p>See <code>urxvt(7)</code> (try <code>man 7 urxvt</code>) for a list of
61frequently asked questions and answer to them and some common 61frequently asked questions and answer to them and some common
62problems. That document is also accessible on the World-Wide-Web at 62problems. That document is also accessible on the World-Wide-Web at
63<a href="http://cvs.schmorp.de/browse/*checkout*/rxvt-unicode/doc/rxvt.7.html">http://cvs.schmorp.de/browse/*checkout*/rxvt-unicode/doc/rxvt.7.html</a>.</p> 63<a href="http://cvs.schmorp.de/browse/*checkout*/rxvt-unicode/doc/rxvt.7.html">http://cvs.schmorp.de/browse/*checkout*/rxvt-unicode/doc/rxvt.7.html</a>.</p>
64<p> 64<p>
65</p> 65</p>
… …
93<p>It is still faithfully following the original rxvt idea of being lean 93<p>It is still faithfully following the original rxvt idea of being lean
94and nice on resources: for example, you can still configure rxvt-unicode 94and nice on resources: for example, you can still configure rxvt-unicode
95without most of it's features to get a lean binary. It also comes with 95without most of it's features to get a lean binary. It also comes with
96a client/daemon pair that lets you open any number of terminal windows 96a client/daemon pair that lets you open any number of terminal windows
97from within a single process, which makes startup time very fast and 97from within a single process, which makes startup time very fast and
98drastically reduces memory usage. See <code>rxvtd(1)</code> (daemon) and 98drastically reduces memory usage. See <code>urxvtd(1)</code> (daemon) and
99<code>rxvtc(1)</code> (client).</p> 99<code>urxvtc(1)</code> (client).</p>
100<p>It also makes technical information about escape sequences (which have 100<p>It also makes technical information about escape sequences (which have
101been extended) easier accessible: see <code>rxvt(7)</code> for technical 101been extended) easier accessible: see <code>urxvt(7)</code> for technical
102reference documentation (escape sequences etc.).</p> 102reference documentation (escape sequences etc.).</p>
103<p> 103<p>
104</p> 104</p>
105<hr /> 105<hr />
106<h1><a name="options">OPTIONS</a></h1> 106<h1><a name="options">OPTIONS</a></h1>
107<p>The <strong>rxvt</strong> options (mostly a subset of <em>xterm</em>'s) are listed 107<p>The <strong>urxvt</strong> options (mostly a subset of <em>xterm</em>'s) are listed
108below. In keeping with the smaller-is-better philosophy, options may be 108below. In keeping with the smaller-is-better philosophy, options may be
109eliminated or default values chosen at compile-time, so options and 109eliminated or default values chosen at compile-time, so options and
110defaults listed may not accurately reflect the version installed on 110defaults listed may not accurately reflect the version installed on
111your system. `rxvt -h' gives a list of major compile-time options on 111your system. `urxvt -h' gives a list of major compile-time options on
112the <em>Options</em> line. Option descriptions may be prefixed with which 112the <em>Options</em> line. Option descriptions may be prefixed with which
113compile option each is dependent upon. e.g. `Compile <em>XIM</em>:' requires 113compile option each is dependent upon. e.g. `Compile <em>XIM</em>:' requires
114<em>XIM</em> on the <em>Options</em> line. Note: `rxvt -help' gives a list of all 114<em>XIM</em> on the <em>Options</em> line. Note: `urxvt -help' gives a list of all
115command-line options compiled into your version.</p> 115command-line options compiled into your version.</p>
116<p>Note that <strong>rxvt</strong> permits the resource name to be used as a 116<p>Note that <strong>urxvt</strong> permits the resource name to be used as a
117long-option (--/++ option) so the potential command-line options are 117long-option (--/++ option) so the potential command-line options are
118far greater than those listed. For example: `rxvt --loginShell --color1 118far greater than those listed. For example: `urxvt --loginShell --color1
119Orange'.</p> 119Orange'.</p>
120<p>The following options are available:</p> 120<p>The following options are available:</p>
121<dl> 121<dl>
122<dt><strong><a name="item__2dhelp_2c__2d_2dhelp"><strong>-help</strong>, <strong>--help</strong></a></strong><br /> 122<dt><strong><a name="item__2dhelp_2c__2d_2dhelp"><strong>-help</strong>, <strong>--help</strong></a></strong><br />
123</dt> 123</dt>
… …
182used to brighten or darken the image in addition to tinting it; resource 182used to brighten or darken the image in addition to tinting it; resource
183<em>tintColor</em>. Example: 183<em>tintColor</em>. Example:
184</dd> 184</dd>
185<dd> 185<dd>
186<pre> 186<pre>
187 rxvt -tr -tint blue -sh 40</pre> 187 urxvt -tr -tint blue -sh 40</pre>
188</dd> 188</dd>
189<p></p> 189<p></p>
190<dt><strong><a name="item__2dsh"><strong>-sh</strong></a></strong><br /> 190<dt><strong><a name="item__2dsh"><strong>-sh</strong></a></strong><br />
191</dt> 191</dt>
192<dd> 192<dd>
… …
243<p></p> 243<p></p>
244<dt><strong><a name="item__2dfn_fontlist"><strong>-fn</strong> <em>fontlist</em></a></strong><br /> 244<dt><strong><a name="item__2dfn_fontlist"><strong>-fn</strong> <em>fontlist</em></a></strong><br />
245</dt> 245</dt>
246<dd> 246<dd>
247Select the fonts to be used. This is a comma separated list of font names 247Select the fonts to be used. This is a comma separated list of font names
248that are used in turn when trying to display Unicode characters. The 248that are checked in order when trying to find glyphs for characters. The
249first font defines the cell size for characters; other fonts might be 249first font defines the cell size for characters; other fonts might be
250smaller, but not (in general) larger. A (hopefully) reasonable default 250smaller, but not (in general) larger. A (hopefully) reasonable default
251font list is always appended to it. See resource <strong>font</strong> for more details. 251font list is always appended to it. See resource <strong>font</strong> for more details.
252</dd> 252</dd>
253<dd> 253<dd>
… …
255with <code>x:</code>. To specify an XFT-font, you need to prefix it with <code>xft:</code>, 255with <code>x:</code>. To specify an XFT-font, you need to prefix it with <code>xft:</code>,
256e.g.:</p> 256e.g.:</p>
257</dd> 257</dd>
258<dd> 258<dd>
259<pre> 259<pre>
260 rxvt -fn &quot;xft:Bitstream Vera Sans Mono:pixelsize=15&quot; 260 urxvt -fn &quot;xft:Bitstream Vera Sans Mono:pixelsize=15&quot;
261 rxvt -fn &quot;9x15bold,xft:Bitstream Vera Sans Mono&quot;</pre> 261 urxvt -fn &quot;9x15bold,xft:Bitstream Vera Sans Mono&quot;</pre>
262</dd> 262</dd>
263<dd> 263<dd>
264<p>See also the question ``How does rxvt-unicode choose fonts?'' in the FAQ 264<p>See also the question ``How does rxvt-unicode choose fonts?'' in the FAQ
265section of rxvt(7).</p> 265section of urxvt(7).</p>
266</dd> 266</dd>
267<p></p> 267<p></p>
268<dt><strong><a name="item__2dfb_fontlist"><strong>-fb</strong> <em>fontlist</em></a></strong><br /> 268<dt><strong><a name="item__2dfb_fontlist"><strong>-fb</strong> <em>fontlist</em></a></strong><br />
269</dt> 269</dt>
270<dd> 270<dd>
… …
444</dd> 444</dd>
445<p></p> 445<p></p>
446<dt><strong><a name="item__2de_command__5barguments_5d"><strong>-e</strong> <em>command [arguments]</em></a></strong><br /> 446<dt><strong><a name="item__2de_command__5barguments_5d"><strong>-e</strong> <em>command [arguments]</em></a></strong><br />
447</dt> 447</dt>
448<dd> 448<dd>
449Run the command with its command-line arguments in the <strong>rxvt</strong> 449Run the command with its command-line arguments in the <strong>urxvt</strong>
450window; also sets the window title and icon name to be the basename of 450window; also sets the window title and icon name to be the basename of
451the program being executed if neither <em>-title</em> (<em>-T</em>) nor <em>-n</em> are 451the program being executed if neither <em>-title</em> (<em>-T</em>) nor <em>-n</em> are
452given on the command line. If this option is used, it must be the last 452given on the command line. If this option is used, it must be the last
453on the command-line. If there is no <strong>-e</strong> option then the default is to 453on the command-line. If there is no <strong>-e</strong> option then the default is to
454run the program specified by the <strong>SHELL</strong> environment variable or, 454run the program specified by the <strong>SHELL</strong> environment variable or,
… …
458<p>Please note that you must specify a program with arguments. If you want to 458<p>Please note that you must specify a program with arguments. If you want to
459run shell commands, you have to specify the shell, like this:</p> 459run shell commands, you have to specify the shell, like this:</p>
460</dd> 460</dd>
461<dd> 461<dd>
462<pre> 462<pre>
463 rxvt -e sh -c &quot;shell commands&quot;</pre> 463 urxvt -e sh -c &quot;shell commands&quot;</pre>
464</dd> 464</dd>
465<p></p> 465<p></p>
466<dt><strong><a name="item__2dtitle_text"><strong>-title</strong> <em>text</em></a></strong><br /> 466<dt><strong><a name="item__2dtitle_text"><strong>-title</strong> <em>text</em></a></strong><br />
467</dt> 467</dt>
468<dd> 468<dd>
… …
553</dd> 553</dd>
554<p></p> 554<p></p>
555<dt><strong><a name="item__2dhold_7c_2bhold"><strong>-hold</strong>|<strong>+hold</strong></a></strong><br /> 555<dt><strong><a name="item__2dhold_7c_2bhold"><strong>-hold</strong>|<strong>+hold</strong></a></strong><br />
556</dt> 556</dt>
557<dd> 557<dd>
558Turn on/off hold window after exit support. If enabled, rxvt 558Turn on/off hold window after exit support. If enabled, urxvt
559will not immediately destroy its window when the program executed within 559will not immediately destroy its window when the program executed within
560it exits. Instead, it will wait till it is being killed or closed by the 560it exits. Instead, it will wait till it is being killed or closed by the
561user; resource <strong>hold</strong>. 561user; resource <strong>hold</strong>.
562</dd> 562</dd>
563<p></p> 563<p></p>
… …
568</dd> 568</dd>
569<p></p> 569<p></p>
570<dt><strong><a name="item__2dembed_windowid"><strong>-embed</strong> <em>windowid</em></a></strong><br /> 570<dt><strong><a name="item__2dembed_windowid"><strong>-embed</strong> <em>windowid</em></a></strong><br />
571</dt> 571</dt>
572<dd> 572<dd>
573Tells rxvt to embed it's windows into an already-existing window, 573Tells urxvt to embed it's windows into an already-existing window,
574which enables applications to easily embed a terminal. 574which enables applications to easily embed a terminal.
575</dd> 575</dd>
576<dd> 576<dd>
577<p>Right now, rxvt will first unmap/map the specified window, so it 577<p>Right now, urxvt will first unmap/map the specified window, so it
578shouldn't be a top-level window. rxvt will also reconfigure it 578shouldn't be a top-level window. urxvt will also reconfigure it
579quite a bit, so don't expect it to keep some specific state. It's best to 579quite a bit, so don't expect it to keep some specific state. It's best to
580create an extra subwindow for rxvt and leave it alone.</p> 580create an extra subwindow for urxvt and leave it alone.</p>
581</dd>
582<dd> 581</dd>
582<dd>
583<p>The window will not be destroyed when rxvt exits.</p> 583<p>The window will not be destroyed when urxvt exits.</p>
584</dd>
585<dd> 584</dd>
585<dd>
586<p>It might be useful to know that rxvt will not close file 586<p>It might be useful to know that urxvt will not close file
587descriptors passed to it (except for stdin/out/err, of course), so you 587descriptors passed to it (except for stdin/out/err, of course), so you
588can use file descriptors to communicate with the programs within the 588can use file descriptors to communicate with the programs within the
589terminal. This works regardless of wether the <code>-embed</code> option was used or 589terminal. This works regardless of wether the <code>-embed</code> option was used or
590not.</p> 590not.</p>
591</dd> 591</dd>
… …
596<dd> 596<dd>
597<pre> 597<pre>
598 my $rxvt = new Gtk2::Socket; 598 my $rxvt = new Gtk2::Socket;
599 $rxvt-&gt;signal_connect_after (realize =&gt; sub { 599 $rxvt-&gt;signal_connect_after (realize =&gt; sub {
600 my $xid = $_[0]-&gt;window-&gt;get_xid; 600 my $xid = $_[0]-&gt;window-&gt;get_xid;
601 system &quot;rxvt -embed $xid &amp;&quot;; 601 system &quot;urxvt -embed $xid &amp;&quot;;
602 });</pre> 602 });</pre>
603</dd> 603</dd>
604<p></p> 604<p></p>
605<dt><strong><a name="item__2dpty_2dfd_file_descriptor"><strong>-pty-fd</strong> <em>file descriptor</em></a></strong><br /> 605<dt><strong><a name="item__2dpty_2dfd_file_descriptor"><strong>-pty-fd</strong> <em>file descriptor</em></a></strong><br />
606</dt> 606</dt>
607<dd> 607<dd>
608Tells rxvt NOT to execute any commands or create a new pty/tty 608Tells urxvt NOT to execute any commands or create a new pty/tty
609pair but instead use the given filehandle as the tty master. This is 609pair but instead use the given filehandle as the tty master. This is
610useful if you want to drive rxvt as a generic terminal emulator 610useful if you want to drive urxvt as a generic terminal emulator
611without having to run a program within it. 611without having to run a program within it.
612</dd> 612</dd>
613<dd> 613<dd>
614<p>If this switch is given, rxvt will not create any utmp/wtmp 614<p>If this switch is given, urxvt will not create any utmp/wtmp
615entries and will not tinker with pty/tty permissions - you have to do that 615entries and will not tinker with pty/tty permissions - you have to do that
616yourself if you want that.</p> 616yourself if you want that.</p>
617</dd> 617</dd>
618<dd> 618<dd>
619<p>As an extremely special case, specifying <code>-1</code> will completely suppress 619<p>As an extremely special case, specifying <code>-1</code> will completely suppress
… …
630</dd> 630</dd>
631<dd> 631<dd>
632<pre> 632<pre>
633 my $pty = new IO::Pty; 633 my $pty = new IO::Pty;
634 fcntl $pty, F_SETFD, 0; # clear close-on-exec 634 fcntl $pty, F_SETFD, 0; # clear close-on-exec
635 system &quot;rxvt -pty-fd &quot; . (fileno $pty) . &quot;&amp;&quot;; 635 system &quot;urxvt -pty-fd &quot; . (fileno $pty) . &quot;&amp;&quot;;
636 close $pty;</pre> 636 close $pty;</pre>
637</dd> 637</dd>
638<dd> 638<dd>
639<pre> 639<pre>
640 # now communicate with rxvt 640 # now communicate with rxvt
… …
651<p></p></dl> 651<p></p></dl>
652<p> 652<p>
653</p> 653</p>
654<hr /> 654<hr />
655<h1><a name="resources__available_also_as_longoptions_">RESOURCES (available also as long-options)</a></h1> 655<h1><a name="resources__available_also_as_longoptions_">RESOURCES (available also as long-options)</a></h1>
656<p>Note: `rxvt --help' gives a list of all resources (long 656<p>Note: `urxvt --help' gives a list of all resources (long
657options) compiled into your version.</p> 657options) compiled into your version.</p>
658<p>There are two different methods that rxvt can use to get the 658<p>You can set and change the resources using X11 tools like <strong>xrdb</strong>. Many
659Xresource data: using the X libraries (Xrm*-functions) or internal
660Xresources reader (<strong>~/.Xdefaults</strong>). For the first method (ie.
661<strong>rxvt -h</strong> lists <strong>XGetDefaults</strong>), you can set and change the
662resources using X11 tools like <strong>xrdb</strong>. Many distribution do also load
663settings from the <strong>~/.Xresources</strong> file when X starts. rxvt 659distribution do also load settings from the <strong>~/.Xresources</strong> file when X
664will consult the following files/resources in order, with later settings 660starts. urxvt will consult the following files/resources in order,
665overwriting earlier ones:</p> 661with later settings overwriting earlier ones:</p>
666<pre> 662<pre>
667 1. system-wide app-defaults file, either locale-dependent OR global 663 1. system-wide app-defaults file, either locale-dependent OR global
668 2. app-defaults file in $XAPPLRESDIR 664 2. app-defaults file in $XAPPLRESDIR
669 3. RESOURCE_MANAGER property on root-window OR $HOME/.Xdefaults 665 3. RESOURCE_MANAGER property on root-window OR $HOME/.Xdefaults
670 4. SCREEN_RESOURCES for the current screen 666 4. SCREEN_RESOURCES for the current screen
671 5. $XENVIRONMENT file OR $HOME/.Xdefaults-&lt;nodename&gt;</pre> 667 5. $XENVIRONMENT file OR $HOME/.Xdefaults-&lt;nodename&gt;</pre>
672<p>If compiled with internal Xresources support (i.e. <strong>rxvt -h</strong>
673lists <strong>.Xdefaults</strong>) then <strong>rxvt</strong> accepts application defaults
674set in XAPPLOADDIR/URxvt (compile-time defined: usually
675<strong>/usr/lib/X11/app-defaults/URxvt</strong>) and resources set in
676<strong>~/.Xdefaults</strong>, or <strong>~/.Xresources</strong> if <strong>~/.Xdefaults</strong> does not exist.
677Note that when reading X resources, <strong>rxvt</strong> recognizes two 668<p>Note that when reading X resources, <strong>urxvt</strong> recognizes two class
678class names: <strong>XTerm</strong> and <strong>URxvt</strong>. The class name <strong>Rxvt</strong> allows 669names: <strong>Rxvt</strong> and <strong>URxvt</strong>. The class name <strong>Rxvt</strong> allows resources
679resources common to both <strong>rxvt</strong> and the original <em>rxvt</em> to be 670common to both <strong>urxvt</strong> and the original <em>rxvt</em> to be easily
680easily configured, while the class name <strong>URxvt</strong> allows resources 671configured, while the class name <strong>URxvt</strong> allows resources unique to
681unique to <strong>rxvt</strong>, notably colours and key-handling, to be 672<strong>urxvt</strong>, to be shared between different <strong>urxvt</strong>
682shared between different <strong>rxvt</strong> configurations. If no 673configurations. If no resources are specified, suitable defaults will
683resources are specified, suitable defaults will be used. Command-line 674be used. Command-line arguments can be used to override resource
684arguments can be used to override resource settings. The following 675settings. The following resources are supported (you might want to
685resources are allowed:</p> 676check the <code>urxvtperl(3)</code> manpage for additional settings by perl
677extensions not documented here):</p>
686<dl> 678<dl>
687<dt><strong><a name="item_geometry_3a_geom"><strong>geometry:</strong> <em>geom</em></a></strong><br /> 679<dt><strong><a name="item_geometry_3a_geom"><strong>geometry:</strong> <em>geom</em></a></strong><br />
688</dt> 680</dt>
689<dd> 681<dd>
690Create the window with the specified X window geometry [default 80x24]; 682Create the window with the specified X window geometry [default 80x24];
… …
7153=yellow, 4=blue, 5=magenta, 6=cyan, 7=white, but the actual colour 7073=yellow, 4=blue, 5=magenta, 6=cyan, 7=white, but the actual colour
716names used are listed in the <strong>COLORS AND GRAPHICS</strong> section. 708names used are listed in the <strong>COLORS AND GRAPHICS</strong> section.
717</dd> 709</dd>
718<dd> 710<dd>
719<p>Colours higher than 15 cannot be set using resources (yet), but can be 711<p>Colours higher than 15 cannot be set using resources (yet), but can be
720changed using an escape command (see rxvt(7)).</p> 712changed using an escape command (see urxvt(7)).</p>
721</dd> 713</dd>
722<dd> 714<dd>
723<p>Colours 16-79 form a standard 4x4x4 colour cube (the same as xterm with 715<p>Colours 16-79 form a standard 4x4x4 colour cube (the same as xterm with
72488 colour support). Colours 80-87 are evenly spaces grey steps.</p> 71688 colour support). Colours 80-87 are evenly spaces grey steps.</p>
725</dd> 717</dd>
… …
872</dd> 864</dd>
873<p></p> 865<p></p>
874<dt><strong><a name="item_font_3a_fontlist"><strong>font:</strong> <em>fontlist</em></a></strong><br /> 866<dt><strong><a name="item_font_3a_fontlist"><strong>font:</strong> <em>fontlist</em></a></strong><br />
875</dt> 867</dt>
876<dd> 868<dd>
877Select the fonts to be used. This is a comma separated list of font 869Select the fonts to be used. This is a comma separated list of font names
878names that are used in turn when trying to display Unicode characters. 870that are checked in order when trying to find glyphs for characters. The
879The first font defines the cell size for characters; other fonts might 871first font defines the cell size for characters; other fonts might be
880be smaller, but not larger. A reasonable default font list is always 872smaller, but not (in general) larger. A (hopefully) reasonable default
881appended to it; option <strong>-fn</strong>. 873font list is always appended to it; option <strong>-fn</strong>.
882</dd> 874</dd>
883<dd> 875<dd>
884<p>Each font can either be a standard X11 core font (XLFD) name, with 876<p>Each font can either be a standard X11 core font (XLFD) name, with
885optional prefix <code>x:</code> or a Xft font (Compile <em>xft</em>), prefixed with <code>xft:</code>.</p> 877optional prefix <code>x:</code> or a Xft font (Compile <em>xft</em>), prefixed with <code>xft:</code>.</p>
886</dd> 878</dd>
… …
1253</dt> 1245</dt>
1254<dd> 1246<dd>
1255Specify the font-set used for XIM styles <code>OverTheSpot</code> or 1247Specify the font-set used for XIM styles <code>OverTheSpot</code> or
1256<code>OffTheSpot</code>. It must be a standard X font set (XLFD patterns separated 1248<code>OffTheSpot</code>. It must be a standard X font set (XLFD patterns separated
1257by commas), i.e. it's not in the same format as the other font lists used 1249by commas), i.e. it's not in the same format as the other font lists used
1258in rxvt. The default will be set-up to chose *any* suitable found 1250in urxvt. The default will be set-up to chose *any* suitable found
1259found, preferably one or two pixels differing in size to the base font. 1251found, preferably one or two pixels differing in size to the base font.
1260option <strong>-imfont</strong>. 1252option <strong>-imfont</strong>.
1261</dd> 1253</dd>
1262<p></p> 1254<p></p>
1263<dt><strong><a name="item_tripleclickwords_3a_boolean"><strong>tripleclickwords:</strong> <em>boolean</em></a></strong><br /> 1255<dt><strong><a name="item_tripleclickwords_3a_boolean"><strong>tripleclickwords:</strong> <em>boolean</em></a></strong><br />
… …
1318</dd> 1310</dd>
1319<p></p> 1311<p></p>
1320<dt><strong><a name="item_hold_3a_bool"><strong>hold</strong>: <em>bool</em></a></strong><br /> 1312<dt><strong><a name="item_hold_3a_bool"><strong>hold</strong>: <em>bool</em></a></strong><br />
1321</dt> 1313</dt>
1322<dd> 1314<dd>
1323Turn on/off hold window after exit support. If enabled, rxvt 1315Turn on/off hold window after exit support. If enabled, urxvt
1324will not immediately destroy its window when the program executed within 1316will not immediately destroy its window when the program executed within
1325it exits. Instead, it will wait till it is being killed or closed by the 1317it exits. Instead, it will wait till it is being killed or closed by the
1326user. 1318user.
1327</dd> 1319</dd>
1328<p></p> 1320<p></p>
… …
1358<code>\000</code>: octal number) or verbatim control characters (<code>^?</code>: delete, 1350<code>\000</code>: octal number) or verbatim control characters (<code>^?</code>: delete,
1359<code>^@</code>: null, <code>^A</code> ...) and may be enclosed with double quotes so that it 1351<code>^@</code>: null, <code>^A</code> ...) and may be enclosed with double quotes so that it
1360can start or end with whitespace.</p> 1352can start or end with whitespace.</p>
1361</dd> 1353</dd>
1362<dd> 1354<dd>
1363<p>Please note that you need to double the <code>\</code> when using 1355<p>Please note that you need to double the <code>\</code> in resource files, as
1364<code>--enable-xgetdefault</code>, as X itself does it's own de-escaping (you can 1356Xlib itself does it's own de-escaping (you can use <code>\033</code> instead of
1365use <code>\033</code> instead of <code>\e</code> (and so on), which will work with both Xt and 1357<code>\e</code> (and so on), which will work with both Xt and urxvt's own
1366rxvt's own processing).</p> 1358processing).</p>
1367</dd> 1359</dd>
1368<dd> 1360<dd>
1369<p>You can define a range of keysyms in one shot by providing a <em>string</em> 1361<p>You can define a range of keysyms in one shot by providing a <em>string</em>
1370with pattern <strong>list/PREFIX/MIDDLE/SUFFIX</strong>, where the delimeter `/' 1362with pattern <strong>list/PREFIX/MIDDLE/SUFFIX</strong>, where the delimeter `/'
1371should be a character not used by the strings.</p> 1363should be a character not used by the strings.</p>
… …
1386 URxvt.keysym.Meta-Control-0x62: \033&lt;M-C-b&gt; 1378 URxvt.keysym.Meta-Control-0x62: \033&lt;M-C-b&gt;
1387 URxvt.keysym.Meta-Control-0x63: \033&lt;M-C-c&gt;</pre> 1379 URxvt.keysym.Meta-Control-0x63: \033&lt;M-C-c&gt;</pre>
1388</dd> 1380</dd>
1389<dd> 1381<dd>
1390<p>If <em>string</em> takes the form of <code>command:STRING</code>, the specified <strong>STRING</strong> 1382<p>If <em>string</em> takes the form of <code>command:STRING</code>, the specified <strong>STRING</strong>
1391is interpreted and executed as rxvt's control sequence. For 1383is interpreted and executed as urxvt's control sequence. For
1392example the following means ``change the current locale to <code>zh_CN.GBK</code> 1384example the following means ``change the current locale to <code>zh_CN.GBK</code>
1393when Control-Meta-c is being pressed'':</p> 1385when Control-Meta-c is being pressed'':</p>
1394</dd> 1386</dd>
1395<dd> 1387<dd>
1396<pre> 1388<pre>
1397 URxvt.keysym.M-C-c: command:\033]701;zh_CN.GBK\007</pre> 1389 URxvt.keysym.M-C-c: command:\033]701;zh_CN.GBK\007</pre>
1398</dd> 1390</dd>
1399<dd> 1391<dd>
1400<p>If <em>string</em> takes the form <code>perl:STRING</code>, then the specified <strong>STRING</strong> 1392<p>If <em>string</em> takes the form <code>perl:STRING</code>, then the specified <strong>STRING</strong>
1401is passed to the <code>on_keyboard_command</code> perl handler. See the <code>rxvtperl(3)</code> 1393is passed to the <code>on_keyboard_command</code> perl handler. See the <code>urxvtperl(3)</code>
1402manpage. For example, the <em>selection</em> extension (activated via 1394manpage. For example, the <em>selection</em> extension (activated via
1403<code>rxvt -pe selection</code>) listens for <code>selection:rot13</code> events:</p> 1395<code>urxvt -pe selection</code>) listens for <code>selection:rot13</code> events:</p>
1404</dd> 1396</dd>
1405<dd> 1397<dd>
1406<pre> 1398<pre>
1407 URxvt.keysym.M-C-c: perl:selection:rot13</pre> 1399 URxvt.keysym.M-C-c: perl:selection:rot13</pre>
1408</dd> 1400</dd>
… …
1414definitions for <code>Meta-a</code>, <code>Shift-a</code> and so on, unless some of those are defined 1406definitions for <code>Meta-a</code>, <code>Shift-a</code> and so on, unless some of those are defined
1415mappings themselves.</p> 1407mappings themselves.</p>
1416</dd> 1408</dd>
1417<dd> 1409<dd>
1418<p>Unfortunately, this will override built-in key mappings. For example 1410<p>Unfortunately, this will override built-in key mappings. For example
1419if you overwrite the <code>Insert</code> key you will disable rxvt's 1411if you overwrite the <code>Insert</code> key you will disable urxvt's
1420<code>Shift-Insert</code> mapping. To re-enable that, you can poke ``holes'' into the 1412<code>Shift-Insert</code> mapping. To re-enable that, you can poke ``holes'' into the
1421user-defined keymap using the <code>builtin:</code> replacement:</p> 1413user-defined keymap using the <code>builtin:</code> replacement:</p>
1422</dd> 1414</dd>
1423<dd> 1415<dd>
1424<pre> 1416<pre>
… …
1439<pre> 1431<pre>
1440 URxvt.keysym.M-C-1: command:\033]50;suxuseuro\007 1432 URxvt.keysym.M-C-1: command:\033]50;suxuseuro\007
1441 URxvt.keysym.M-C-2: command:\033]50;9x15bold\007</pre> 1433 URxvt.keysym.M-C-2: command:\033]50;9x15bold\007</pre>
1442</dd> 1434</dd>
1443<dd> 1435<dd>
1444<p>Other things are possible, e.g. resizing (see <code>rxvt(7)</code> for more 1436<p>Other things are possible, e.g. resizing (see <code>urxvt(7)</code> for more
1445info):</p> 1437info):</p>
1446</dd> 1438</dd>
1447<dd> 1439<dd>
1448<pre> 1440<pre>
1449 URxvt.keysym.M-C-3: command:\033[8;25;80t 1441 URxvt.keysym.M-C-3: command:\033[8;25;80t
… …
1485<p></p> 1477<p></p>
1486<dt><strong><a name="item_perl_2deval_3a_string"><strong>perl-eval</strong>: <em>string</em></a></strong><br /> 1478<dt><strong><a name="item_perl_2deval_3a_string"><strong>perl-eval</strong>: <em>string</em></a></strong><br />
1487</dt> 1479</dt>
1488<dd> 1480<dd>
1489Perl code to be evaluated when all extensions have been registered. See 1481Perl code to be evaluated when all extensions have been registered. See
1490the <code>rxvtperl(3)</code> manpage. Due to security reasons, this resource 1482the <code>urxvtperl(3)</code> manpage. Due to security reasons, this resource
1491will be ignored when running setuid/setgid. 1483will be ignored when running setuid/setgid.
1492</dd> 1484</dd>
1493<p></p> 1485<p></p>
1494<dt><strong><a name="item_perl_2dlib_3a_path"><strong>perl-lib</strong>: <em>path</em></a></strong><br /> 1486<dt><strong><a name="item_perl_2dlib_3a_path"><strong>perl-lib</strong>: <em>path</em></a></strong><br />
1495</dt> 1487</dt>
1496<dd> 1488<dd>
1497Colon-separated list of additional directories that hold extension 1489Colon-separated list of additional directories that hold extension
1498scripts. When looking for extensions specified by the <code>perl</code> resource, 1490scripts. When looking for extensions specified by the <code>perl</code> resource,
1499rxvt will first look in these directories and then in 1491urxvt will first look in these directories and then in
1500<em>/opt/rxvt/lib/urxvt/perl/</em>. Due to security reasons, this resource 1492<em>/usr/local/lib/urxvt/perl/</em>. Due to security reasons, this resource
1501will be ignored when running setuid/setgid. 1493will be ignored when running setuid/setgid.
1502</dd> 1494</dd>
1503<dd> 1495<dd>
1504<p>See the <code>rxvtperl(3)</code> manpage.</p> 1496<p>See the <code>urxvtperl(3)</code> manpage.</p>
1497</dd>
1498<p></p>
1499<dt><strong><a name="item_selection_2epattern_2didx_3a_perl_2dregex"><strong>selection.pattern-<em>idx</em> </strong>&gt;: <em>perl-regex</em></a></strong><br />
1500</dt>
1501<dd>
1502Additional selection patterns, see the <code>urxvtperl(3)</code> manpage for
1503details.
1504</dd>
1505<p></p>
1506<dt><strong><a name="item_selection_2dautotransform_2eidx_3a_perl_2dtransfor"><strong>selection-autotransform.<em>idx</em> </strong>&gt;: <em>perl-transform</em></a></strong><br />
1507</dt>
1508<dd>
1509Selection auto-transform patterns, see the <code>urxvtperl(3)</code> manpage
1510for details.
1511</dd>
1512<p></p>
1513<dt><strong><a name="item_searchable_2dscrollback_3a_keysym"><strong>searchable-scrollback:</strong> <em>keysym</em></a></strong><br />
1514</dt>
1515<dd>
1516Sets the hotkey that starts the incremental scrollback buffer search
1517(default: <code>M-s</code>).
1505</dd> 1518</dd>
1506<p></p> 1519<p></p>
1507<dt><strong><a name="item_urllauncher_3a_string"><strong>urlLauncher</strong>: <em>string</em></a></strong><br /> 1520<dt><strong><a name="item_urllauncher_3a_string"><strong>urlLauncher</strong>: <em>string</em></a></strong><br />
1508</dt> 1521</dt>
1509<dd> 1522<dd>
… …
1519<p></p></dl> 1532<p></p></dl>
1520<p> 1533<p>
1521</p> 1534</p>
1522<hr /> 1535<hr />
1523<h1><a name="the_scrollbar">THE SCROLLBAR</a></h1> 1536<h1><a name="the_scrollbar">THE SCROLLBAR</a></h1>
1524<p>Lines of text that scroll off the top of the <strong>rxvt</strong> window 1537<p>Lines of text that scroll off the top of the <strong>urxvt</strong> window
1525(resource: <strong>saveLines</strong>) and can be scrolled back using the scrollbar 1538(resource: <strong>saveLines</strong>) and can be scrolled back using the scrollbar
1526or by keystrokes. The normal <strong>rxvt</strong> scrollbar has arrows and 1539or by keystrokes. The normal <strong>urxvt</strong> scrollbar has arrows and
1527its behaviour is fairly intuitive. The <strong>xterm-scrollbar</strong> is without 1540its behaviour is fairly intuitive. The <strong>xterm-scrollbar</strong> is without
1528arrows and its behaviour mimics that of <em>xterm</em></p> 1541arrows and its behaviour mimics that of <em>xterm</em></p>
1529<p>Scroll down with <strong>Button1</strong> (<strong>xterm-scrollbar</strong>) or <strong>Shift-Next</strong>. 1542<p>Scroll down with <strong>Button1</strong> (<strong>xterm-scrollbar</strong>) or <strong>Shift-Next</strong>.
1530Scroll up with <strong>Button3</strong> (<strong>xterm-scrollbar</strong>) or <strong>Shift-Prior</strong>. 1543Scroll up with <strong>Button3</strong> (<strong>xterm-scrollbar</strong>) or <strong>Shift-Prior</strong>.
1531Continuous scroll with <strong>Button2</strong>.</p> 1544Continuous scroll with <strong>Button2</strong>.</p>
… …
1568<p></p> 1581<p></p>
1569<dt><strong><a name="item_insertion_3a"><strong>Insertion</strong>:</a></strong><br /> 1582<dt><strong><a name="item_insertion_3a"><strong>Insertion</strong>:</a></strong><br />
1570</dt> 1583</dt>
1571<dd> 1584<dd>
1572Pressing and releasing the Middle mouse button (or <strong>Shift-Insert</strong>) in 1585Pressing and releasing the Middle mouse button (or <strong>Shift-Insert</strong>) in
1573an <strong>rxvt</strong> window causes the current text selection to be 1586an <strong>urxvt</strong> window causes the current text selection to be
1574inserted as if it had been typed on the keyboard. 1587inserted as if it had been typed on the keyboard.
1575</dd> 1588</dd>
1576<p></p></dl> 1589<p></p></dl>
1577<p> 1590<p>
1578</p> 1591</p>
… …
1644both scenario A and B of ISO 14755, including part 5.2.</p> 1657both scenario A and B of ISO 14755, including part 5.2.</p>
1645<p> 1658<p>
1646</p> 1659</p>
1647<hr /> 1660<hr />
1648<h1><a name="login_stamp">LOGIN STAMP</a></h1> 1661<h1><a name="login_stamp">LOGIN STAMP</a></h1>
1649<p><strong>rxvt</strong> tries to write an entry into the <em>utmp</em>(5) file so that 1662<p><strong>urxvt</strong> tries to write an entry into the <em>utmp</em>(5) file so that
1650it can be seen via the <em>who(1)</em> command, and can accept messages. To 1663it can be seen via the <em>who(1)</em> command, and can accept messages. To
1651allow this feature, <strong>rxvt</strong> may need to be installed setuid root 1664allow this feature, <strong>urxvt</strong> may need to be installed setuid root
1652on some systems or setgid to root or to some other group on others.</p> 1665on some systems or setgid to root or to some other group on others.</p>
1653<p> 1666<p>
1654</p> 1667</p>
1655<hr /> 1668<hr />
1656<h1><a name="colors_and_graphics">COLORS AND GRAPHICS</a></h1> 1669<h1><a name="colors_and_graphics">COLORS AND GRAPHICS</a></h1>
1657<p>In addition to the default foreground and background colours, 1670<p>In addition to the default foreground and background colours,
1658<strong>rxvt</strong> can display up to 16 colours (8 ANSI colours plus 1671<strong>urxvt</strong> can display up to 16 colours (8 ANSI colours plus
1659high-intensity bold/blink versions of the same). Here is a list of the 1672high-intensity bold/blink versions of the same). Here is a list of the
1660colours with their <strong>rgb.txt</strong> names.</p> 1673colours with their <strong>rgb.txt</strong> names.</p>
1661<table> 1674<table>
1662<tr><td>color0</td><td>(black)</td><td>= Black</td></tr> 1675<tr><td>color0</td><td>(black)</td><td>= Black</td></tr>
1663<tr><td>color1</td><td>(red)</td><td>= Red3</td></tr> 1676<tr><td>color1</td><td>(red)</td><td>= Red3</td></tr>
… …
1684<p>Note that <strong>-rv</strong> (<strong>``reverseVideo: True''</strong>) simulates reverse video by 1697<p>Note that <strong>-rv</strong> (<strong>``reverseVideo: True''</strong>) simulates reverse video by
1685always swapping the foreground/background colours. This is in contrast to 1698always swapping the foreground/background colours. This is in contrast to
1686<em>xterm</em>(1) where the colours are only swapped if they have not otherwise 1699<em>xterm</em>(1) where the colours are only swapped if they have not otherwise
1687been specified. For example,</p> 1700been specified. For example,</p>
1688<dl> 1701<dl>
1689<dt><strong><a name="item_rxvt__2dfg_black__2dbg_white__2drv"><strong>rxvt -fg Black -bg White -rv</strong></a></strong><br /> 1702<dt><strong><a name="item_urxvt__2dfg_black__2dbg_white__2drv"><strong>urxvt -fg Black -bg White -rv</strong></a></strong><br />
1690</dt> 1703</dt>
1691<dd> 1704<dd>
1692would yield White on Black, while on <em>xterm</em>(1) it would yield Black 1705would yield White on Black, while on <em>xterm</em>(1) it would yield Black
1693on White. 1706on White.
1694</dd> 1707</dd>
1695<p></p></dl> 1708<p></p></dl>
1696<p> 1709<p>
1697</p> 1710</p>
1698<hr /> 1711<hr />
1699<h1><a name="environment">ENVIRONMENT</a></h1> 1712<h1><a name="environment">ENVIRONMENT</a></h1>
1700<p><strong>rxvt</strong> sets and/or uses the following environment variables:</p> 1713<p><strong>urxvt</strong> sets and/or uses the following environment variables:</p>
1701<dl> 1714<dl>
1702<dt><strong><a name="item_term"><strong>TERM</strong></a></strong><br /> 1715<dt><strong><a name="item_term"><strong>TERM</strong></a></strong><br />
1703</dt> 1716</dt>
1704<dd> 1717<dd>
1705Normally set to <code>rxvt-unicode</code>, unless overwritten at configure time, via 1718Normally set to <code>rxvt-unicode</code>, unless overwritten at configure time, via
… …
1707</dd> 1720</dd>
1708<p></p> 1721<p></p>
1709<dt><strong><a name="item_colorterm"><strong>COLORTERM</strong></a></strong><br /> 1722<dt><strong><a name="item_colorterm"><strong>COLORTERM</strong></a></strong><br />
1710</dt> 1723</dt>
1711<dd> 1724<dd>
1712Either <code>rxvt</code>, <code>rxvt-xpm</code>, depending on wether rxvt was 1725Either <code>rxvt</code>, <code>rxvt-xpm</code>, depending on wether urxvt was
1713compiled with XPM support, and optionally with the added extension 1726compiled with XPM support, and optionally with the added extension
1714<code>-mono</code> to indicate that rxvt-unicode runs on a monochrome screen. 1727<code>-mono</code> to indicate that rxvt-unicode runs on a monochrome screen.
1715</dd> 1728</dd>
1716<p></p> 1729<p></p>
1717<dt><strong><a name="item_colorfgbg"><strong>COLORFGBG</strong></a></strong><br /> 1730<dt><strong><a name="item_colorfgbg"><strong>COLORFGBG</strong></a></strong><br />
… …
1719<dd> 1732<dd>
1720Set to a string of the form <code>fg;bg</code> or <code>fg;xpm;bg</code>, where <code>fg</code> is 1733Set to a string of the form <code>fg;bg</code> or <code>fg;xpm;bg</code>, where <code>fg</code> is
1721the colour code used as default foreground/text colour (or the string 1734the colour code used as default foreground/text colour (or the string
1722<code>default</code> to indicate that the default-colour escape sequence is to be 1735<code>default</code> to indicate that the default-colour escape sequence is to be
1723used), <code>bg</code> is the colour code used as default background colour (or the 1736used), <code>bg</code> is the colour code used as default background colour (or the
1724string <code>default</code>), and <code>xpm</code> is the string <code>default</code> if rxvt 1737string <code>default</code>), and <code>xpm</code> is the string <code>default</code> if urxvt
1725was compiled with XPM support. Libraries like <code>ncurses</code> and <code>slang</code> can 1738was compiled with XPM support. Libraries like <code>ncurses</code> and <code>slang</code> can
1726(and do) use this information to optimize screen output. 1739(and do) use this information to optimize screen output.
1727</dd> 1740</dd>
1728<p></p> 1741<p></p>
1729<dt><strong><a name="item_windowid"><strong>WINDOWID</strong></a></strong><br /> 1742<dt><strong><a name="item_windowid"><strong>WINDOWID</strong></a></strong><br />
1730</dt> 1743</dt>
1731<dd> 1744<dd>
1732Set to the (decimal) X Window ID of the rxvt window (the toplevel 1745Set to the (decimal) X Window ID of the urxvt window (the toplevel
1733window, which usually has subwindows for the scrollbar, the terminal 1746window, which usually has subwindows for the scrollbar, the terminal
1734window and so on). 1747window and so on).
1735</dd> 1748</dd>
1736<p></p> 1749<p></p>
1737<dt><strong><a name="item_terminfo"><strong>TERMINFO</strong></a></strong><br /> 1750<dt><strong><a name="item_terminfo"><strong>TERMINFO</strong></a></strong><br />
1738</dt> 1751</dt>
1739<dd> 1752<dd>
1740Set to the terminfo directory iff rxvt was configured with 1753Set to the terminfo directory iff urxvt was configured with
1741<code>--with-terminfo=PATH</code>. 1754<code>--with-terminfo=PATH</code>.
1742</dd> 1755</dd>
1743<p></p> 1756<p></p>
1744<dt><strong><a name="item_display"><strong>DISPLAY</strong></a></strong><br /> 1757<dt><strong><a name="item_display"><strong>DISPLAY</strong></a></strong><br />
1745</dt> 1758</dt>
1746<dd> 1759<dd>
1747Used by rxvt to connect to the display and set to the correct 1760Used by urxvt to connect to the display and set to the correct
1748display in it's child processes. 1761display in it's child processes.
1749</dd> 1762</dd>
1750<p></p> 1763<p></p>
1751<dt><strong><a name="item_shell"><strong>SHELL</strong></a></strong><br /> 1764<dt><strong><a name="item_shell"><strong>SHELL</strong></a></strong><br />
1752</dt> 1765</dt>
… …
1755</dd> 1768</dd>
1756<p></p> 1769<p></p>
1757<dt><strong><a name="item_rxvtpath"><strong>RXVTPATH</strong></a></strong><br /> 1770<dt><strong><a name="item_rxvtpath"><strong>RXVTPATH</strong></a></strong><br />
1758</dt> 1771</dt>
1759<dd> 1772<dd>
1760The path where rxvt looks for support files such as menu and xpm 1773The path where urxvt looks for support files such as menu and xpm
1761files. 1774files.
1762</dd> 1775</dd>
1763<p></p> 1776<p></p>
1764<dt><strong><a name="item_path"><strong>PATH</strong></a></strong><br /> 1777<dt><strong><a name="item_path"><strong>PATH</strong></a></strong><br />
1765</dt> 1778</dt>
… …
1768</dd> 1781</dd>
1769<p></p> 1782<p></p>
1770<dt><strong><a name="item_rxvt_socket"><strong>RXVT_SOCKET</strong></a></strong><br /> 1783<dt><strong><a name="item_rxvt_socket"><strong>RXVT_SOCKET</strong></a></strong><br />
1771</dt> 1784</dt>
1772<dd> 1785<dd>
1773The unix domain socket path used by <code>rxvtc(1)</code> and 1786The unix domain socket path used by <code>urxvtc(1)</code> and
1774rxvtd(1). 1787urxvtd(1).
1775</dd> 1788</dd>
1776<dd> 1789<dd>
1777<p>Default <em>$HOME/.rxvt-unicode-<em>&lt;nodename </em></em> &gt;&gt;&gt;.</p> 1790<p>Default <em>$HOME/.rxvt-unicode-<em>&lt;nodename </em></em> &gt;&gt;&gt;.</p>
1778</dd> 1791</dd>
1779<p></p> 1792<p></p>
… …
1793<p></p> 1806<p></p>
1794<dt><strong><a name="item_xenvironment"><strong>XENVIRONMENT</strong></a></strong><br /> 1807<dt><strong><a name="item_xenvironment"><strong>XENVIRONMENT</strong></a></strong><br />
1795</dt> 1808</dt>
1796<dd> 1809<dd>
1797If set and accessible, gives the name of a X resource file to be loaded by 1810If set and accessible, gives the name of a X resource file to be loaded by
1798rxvt. 1811urxvt.
1799</dd> 1812</dd>
1800<p></p></dl> 1813<p></p></dl>
1801<p> 1814<p>
1802</p> 1815</p>
1803<hr /> 1816<hr />
… …
1811<p></p></dl> 1824<p></p></dl>
1812<p> 1825<p>
1813</p> 1826</p>
1814<hr /> 1827<hr />
1815<h1><a name="see_also">SEE ALSO</a></h1> 1828<h1><a name="see_also">SEE ALSO</a></h1>
1816<p>rxvt(7), rxvtc(1), rxvtd(1), xterm(1), sh(1), resize(1), X(1), pty(4), tty(4), <code>utmp(5)</code></p> 1829<p>urxvt(7), urxvtc(1), urxvtd(1), xterm(1), sh(1), resize(1), X(1), pty(4), tty(4), <code>utmp(5)</code></p>
1817<p> 1830<p>
1818</p> 1831</p>
1819<hr /> 1832<hr />
1820<h1><a name="current_project_coordinator">CURRENT PROJECT COORDINATOR</a></h1> 1833<h1><a name="current_project_coordinator">CURRENT PROJECT COORDINATOR</a></h1>
1821<dl> 1834<dl>

Diff Legend

– Removed lines
+ Added lines
< Changed lines
> Changed lines