ac_status=$?
echo "$as_me:$LINENO: \$? = $ac_status" >&5
(exit $ac_status); }; }; then
- echo didididid
+ :
else
echo "$as_me: failed program was:" >&5
sed 's/^/| /' conftest.$ac_ext >&5
if test -z "$orig_CXXFLAGS"; then
if test x$GCC = xyes && test "x$GXX" = xyes; then
CXXFLAGS="-g -O3 -fno-threadsafe-statics -fno-enforce-eh-specs"
- AC_COMPILE_IFELSE([int i;], [echo didididid], [CXXFLAGS="-g -O3"])
+ AC_COMPILE_IFELSE([int i;], [], [CXXFLAGS="-g -O3"])
else
CXXFLAGS="-O"
fi
<dt><strong><a name="item_emanuele_giaquinta__3ce_2egiaquinta_40glauco_2eit_">Emanuele Giaquinta <em><a href="mailto:<e.giaquinta@glauco.it"><e.giaquinta@glauco.it</a></em>></a></strong><br />
</dt>
<dd>
-Pty/tty/utmp/wtmp rewrite, lots of random hacking and bugxifing.
+Pty/tty/utmp/wtmp rewrite, lots of random hacking and bugfixing.
</dd>
<p></p></dl>
.\" ========================================================================
.\"
.IX Title "rxvt 1"
-.TH rxvt 1 "2006-01-19" "7.1" "RXVT-UNICODE"
+.TH rxvt 1 "2006-01-20" "7.1" "RXVT-UNICODE"
.SH "NAME"
rxvt\-unicode (ouR XVT, unicode) \- (a VT102 emulator for the X window system)
.SH "SYNOPSIS"
Project Coordinator (Changes 1.0 \-)
.IP "Emanuele Giaquinta <e.giaquinta@glauco.it>" 4
.IX Item "Emanuele Giaquinta <e.giaquinta@glauco.it>"
-Pty/tty/utmp/wtmp rewrite, lots of random hacking and bugxifing.
+Pty/tty/utmp/wtmp rewrite, lots of random hacking and bugfixing.
Project Coordinator (Changes 1.0 -)
Emanuele Giaquinta <e.giaquinta@glauco.it>
- Pty/tty/utmp/wtmp rewrite, lots of random hacking and bugxifing.
+ Pty/tty/utmp/wtmp rewrite, lots of random hacking and bugfixing.
<li><a href="#the_urxvt__popup_class">The <code>urxvt::popup</code> Class</a></li>
<li><a href="#the_urxvt__timer_class">The <code>urxvt::timer</code> Class</a></li>
<li><a href="#the_urxvt__iow_class">The <code>urxvt::iow</code> Class</a></li>
+ <li><a href="#the_urxvt__iw_class">The <code>urxvt::iw</code> Class</a></li>
+ <li><a href="#the_urxvt__pw_class">The <code>urxvt::pw</code> Class</a></li>
</ul>
<li><a href="#environment">ENVIRONMENT</a></li>
<p>You can activate them like this:</p>
<pre>
rxvt -pe <extensionname></pre>
+<p>Or by adding them to the resource for extensions loaded by default:</p>
+<pre>
+ URxvt.perl-ext-common: default,automove-background,selection-autotransform</pre>
<dl>
<dt><strong><a name="item_selection">selection (enabled by default)</a></strong><br />
</dt>
the message into vi commands to load the file.</p>
</dd>
<p></p>
+<dt><strong><a name="item_tabbed">tabbed</a></strong><br />
+</dt>
+<dd>
+This transforms the terminal into a tabbar with additional terminals, that
+is, it implements what is commonly refered to as ``tabbed terminal''. The topmost line
+displays a ``[NEW]'' button, which, when clicked, will add a new tab, followed by one
+button per tab.
+</dd>
+<dd>
+<p>Clicking a button will activate that tab. Pressing Shift-Left and
+Shift-Right will switch to the tab left or right of the current one.</p>
+</dd>
+<p></p>
<dt><strong><a name="item_mark_2durls">mark-urls</a></strong><br />
</dt>
<dd>
called whenever the relevant event happens.</p>
<p>The first argument passed to them is an extension oject as described in
the in the <code>Extension Objects</code> section.</p>
-<p><strong>All</strong> of these hooks must return a boolean value. If it is true, then the
-event counts as being <em>consumed</em>, and the invocation of other hooks is
-skipped, and the relevant action might not be carried out by the C++ code.</p>
+<p><strong>All</strong> of these hooks must return a boolean value. If any of the called
+hooks returns true, then the event counts as being <em>consumed</em>, and the
+relevant action might not be carried out by the C++ code.</p>
<p><em>When in doubt, return a false value (preferably <code>()</code>). </em>></p>
<dl>
<dt><strong><a name="item_on_init__24term">on_init $term</a></strong><br />
Called after a new terminal object has been initialized, but before
windows are created or the command gets run. Most methods are unsafe to
call or deliver senseless data, as terminal size and other characteristics
-have not yet been determined. You can safely query and change resources,
-though.
+have not yet been determined. You can safely query and change resources
+and options, though. For many purposes the <code>on_start</code> hook is a better
+place.
</dd>
<p></p>
-<dt><strong><a name="item_on_reset__24term">on_reset $term</a></strong><br />
+<dt><strong><a name="item_on_start__24term">on_start $term</a></strong><br />
</dt>
<dd>
-Called after the screen is ``reset'' for any reason, such as resizing or
-control sequences. Here is where you can react on changes to size-related
-variables.
+Called at the very end of initialisation of a new terminal, just before
+trying to map (display) the toplevel and returning to the mainloop.
</dd>
<p></p>
-<dt><strong><a name="item_on_start__24term">on_start $term</a></strong><br />
+<dt><strong><a name="item_on_destroy__24term">on_destroy $term</a></strong><br />
</dt>
<dd>
-Called at the very end of initialisation of a new terminal, just before
-returning to the mainloop.
+Called whenever something tries to destroy terminal, before doing anything
+yet. If this hook returns true, then destruction is skipped, but this is
+rarely a good idea.
+</dd>
+<p></p>
+<dt><strong><a name="item_on_reset__24term">on_reset $term</a></strong><br />
+</dt>
+<dd>
+Called after the screen is ``reset'' for any reason, such as resizing or
+control sequences. Here is where you can react on changes to size-related
+variables.
</dd>
<p></p>
<dt><strong><a name="item_on_child_start__24term_2c__24pid">on_child_start $term, $pid</a></strong><br />
<dd>
<p>subwindow.</p>
</dd>
+<p></p>
+<dt><strong><a name="item_on_client_message__24term_2c__24event">on_client_message $term, $event</a></strong><br />
+</dt>
+<dt><strong><a name="item_on_wm_protocols__24term_2c__24event">on_wm_protocols $term, $event</a></strong><br />
+</dt>
+<dt><strong><a name="item_on_wm_delete_window__24term_2c__24event">on_wm_delete_window $term, $event</a></strong><br />
+</dt>
+<dd>
+Called when various types of ClientMessage events are received (all with
+format=32, WM_PROTOCOLS or WM_PROTOCOLS:WM_DELETE_WINDOW).
+</dd>
<p></p></dl>
<p>
</p>
The current terminal. This variable stores the current <code>urxvt::term</code>
object, whenever a callback/hook is executing.
</dd>
+<p></p>
+<dt><strong><a name="item__40urxvt_3a_3aterm_init">@urxvt::TERM_INIT</a></strong><br />
+</dt>
+<dd>
+All coderefs in this array will be called as methods of the next newly
+created <code>urxvt::term</code> object (during the <code>on_init</code> phase). The array
+gets cleared before the codereferences that were in it are being executed,
+so coderefs can push themselves onto it again if they so desire.
+</dd>
+<dd>
+<p>This complements to the perl-eval commandline option, but gets executed
+first.</p>
+</dd>
+<p></p>
+<dt><strong><a name="item__40urxvt_3a_3aterm_ext">@urxvt::TERM_EXT</a></strong><br />
+</dt>
+<dd>
+Works similar to <code>@TERM_INIT</code>, but contains perl package/class names, which
+get registered as normal extensions after calling the hooks in <code>@TERM_INIT</code>
+but before other extensions. Gets cleared just like <code>@TERM_INIT</code>.
+</dd>
<p></p></dl>
<p>
</p>
<p></p></dl>
<p>
</p>
+<h2><a name="the_urxvt__iw_class">The <code>urxvt::iw</code> Class</a></h2>
+<p>This class implements idle watchers, that get called automatically when
+the process is idle. They should return as fast as possible, after doing
+some useful work.</p>
+<dl>
+<dt><strong><a name="item__24iw__3d_new_urxvt_3a_3aiw">$iw = new urxvt::iw</a></strong><br />
+</dt>
+<dd>
+Create a new idle watcher object in stopped state.
+</dd>
+<p></p>
+<dt><strong>$iw = $iw->cb (sub { my ($iw) = @_; ... })</strong><br />
+</dt>
+<dd>
+Set the callback to be called when the watcher triggers.
+</dd>
+<p></p>
+<dt><strong>$timer = $timer->start</strong><br />
+</dt>
+<dd>
+Start the watcher.
+</dd>
+<p></p>
+<dt><strong>$timer = $timer->stop</strong><br />
+</dt>
+<dd>
+Stop the watcher.
+</dd>
+<p></p></dl>
+<p>
+</p>
+<h2><a name="the_urxvt__pw_class">The <code>urxvt::pw</code> Class</a></h2>
+<p>This class implements process watchers. They create an event whenever a
+process exits, after which they stop automatically.</p>
+<pre>
+ my $pid = fork;
+ ...
+ $term->{pw} = urxvt::pw
+ ->new
+ ->start ($pid)
+ ->cb (sub {
+ my ($pw, $exit_status) = @_;
+ ...
+ });</pre>
+<dl>
+<dt><strong><a name="item__24pw__3d_new_urxvt_3a_3apw">$pw = new urxvt::pw</a></strong><br />
+</dt>
+<dd>
+Create a new process watcher in stopped state.
+</dd>
+<p></p>
+<dt><strong>$pw = $pw->cb (sub { my ($pw, $exit_status) = @_; ... })</strong><br />
+</dt>
+<dd>
+Set the callback to be called when the timer triggers.
+</dd>
+<p></p>
+<dt><strong>$pw = $timer->start ($pid)</strong><br />
+</dt>
+<dd>
+Tells the wqtcher to start watching for process <code>$pid</code>.
+</dd>
+<p></p>
+<dt><strong>$pw = $pw->stop</strong><br />
+</dt>
+<dd>
+Stop the watcher.
+</dd>
+<p></p></dl>
+<p>
+</p>
<hr />
<h1><a name="environment">ENVIRONMENT</a></h1>
<p>
.\" ========================================================================
.\"
.IX Title "rxvt 3"
-.TH rxvt 3 "2006-01-19" "7.1" "RXVT-UNICODE"
+.TH rxvt 3 "2006-01-20" "7.1" "RXVT-UNICODE"
.SH "NAME"
@@RXVT_NAME@@perl \- rxvt\-unicode's embedded perl interpreter
.SH "SYNOPSIS"
.Vb 1
\& @@RXVT_NAME@@ -pe <extensionname>
.Ve
+.PP
+Or by adding them to the resource for extensions loaded by default:
+.PP
+.Vb 1
+\& URxvt.perl-ext-common: default,automove-background,selection-autotransform
+.Ve
.IP "selection (enabled by default)" 4
.IX Item "selection (enabled by default)"
(More) intelligent selection. This extension tries to be more intelligent
The first line tells the selection code to treat the unchanging part of
every error message as a selection pattern, and the second line transforms
the message into vi commands to load the file.
+.IP "tabbed" 4
+.IX Item "tabbed"
+This transforms the terminal into a tabbar with additional terminals, that
+is, it implements what is commonly refered to as \*(L"tabbed terminal\*(R". The topmost line
+displays a \*(L"[\s-1NEW\s0]\*(R" button, which, when clicked, will add a new tab, followed by one
+button per tab.
+.Sp
+Clicking a button will activate that tab. Pressing Shift-Left and
+Shift-Right will switch to the tab left or right of the current one.
.IP "mark-urls" 4
.IX Item "mark-urls"
Uses per-line display filtering (\f(CW\*(C`on_line_update\*(C'\fR) to underline urls and
The first argument passed to them is an extension oject as described in
the in the \f(CW\*(C`Extension Objects\*(C'\fR section.
.PP
-\&\fBAll\fR of these hooks must return a boolean value. If it is true, then the
-event counts as being \fIconsumed\fR, and the invocation of other hooks is
-skipped, and the relevant action might not be carried out by the \*(C+ code.
+\&\fBAll\fR of these hooks must return a boolean value. If any of the called
+hooks returns true, then the event counts as being \fIconsumed\fR, and the
+relevant action might not be carried out by the \*(C+ code.
.PP
\&\fIWhen in doubt, return a false value (preferably \f(CI\*(C`()\*(C'\fI).\fR
.ie n .IP "on_init $term" 4
Called after a new terminal object has been initialized, but before
windows are created or the command gets run. Most methods are unsafe to
call or deliver senseless data, as terminal size and other characteristics
-have not yet been determined. You can safely query and change resources,
-though.
+have not yet been determined. You can safely query and change resources
+and options, though. For many purposes the \f(CW\*(C`on_start\*(C'\fR hook is a better
+place.
+.ie n .IP "on_start $term" 4
+.el .IP "on_start \f(CW$term\fR" 4
+.IX Item "on_start $term"
+Called at the very end of initialisation of a new terminal, just before
+trying to map (display) the toplevel and returning to the mainloop.
+.ie n .IP "on_destroy $term" 4
+.el .IP "on_destroy \f(CW$term\fR" 4
+.IX Item "on_destroy $term"
+Called whenever something tries to destroy terminal, before doing anything
+yet. If this hook returns true, then destruction is skipped, but this is
+rarely a good idea.
.ie n .IP "on_reset $term" 4
.el .IP "on_reset \f(CW$term\fR" 4
.IX Item "on_reset $term"
Called after the screen is \*(L"reset\*(R" for any reason, such as resizing or
control sequences. Here is where you can react on changes to size-related
variables.
-.ie n .IP "on_start $term" 4
-.el .IP "on_start \f(CW$term\fR" 4
-.IX Item "on_start $term"
-Called at the very end of initialisation of a new terminal, just before
-returning to the mainloop.
.ie n .IP "on_child_start $term\fR, \f(CW$pid" 4
.el .IP "on_child_start \f(CW$term\fR, \f(CW$pid\fR" 4
.IX Item "on_child_start $term, $pid"
output, if any, in locale-specific encoding.
.Sp
subwindow.
+.ie n .IP "on_client_message $term\fR, \f(CW$event" 4
+.el .IP "on_client_message \f(CW$term\fR, \f(CW$event\fR" 4
+.IX Item "on_client_message $term, $event"
+.PD 0
+.ie n .IP "on_wm_protocols $term\fR, \f(CW$event" 4
+.el .IP "on_wm_protocols \f(CW$term\fR, \f(CW$event\fR" 4
+.IX Item "on_wm_protocols $term, $event"
+.ie n .IP "on_wm_delete_window $term\fR, \f(CW$event" 4
+.el .IP "on_wm_delete_window \f(CW$term\fR, \f(CW$event\fR" 4
+.IX Item "on_wm_delete_window $term, $event"
+.PD
+Called when various types of ClientMessage events are received (all with
+format=32, \s-1WM_PROTOCOLS\s0 or \s-1WM_PROTOCOLS:WM_DELETE_WINDOW\s0).
.ie n .Sh "Variables in the ""urxvt"" Package"
.el .Sh "Variables in the \f(CWurxvt\fP Package"
.IX Subsection "Variables in the urxvt Package"
.IX Item "$urxvt::TERM"
The current terminal. This variable stores the current \f(CW\*(C`urxvt::term\*(C'\fR
object, whenever a callback/hook is executing.
+.IP "@urxvt::TERM_INIT" 4
+.IX Item "@urxvt::TERM_INIT"
+All coderefs in this array will be called as methods of the next newly
+created \f(CW\*(C`urxvt::term\*(C'\fR object (during the \f(CW\*(C`on_init\*(C'\fR phase). The array
+gets cleared before the codereferences that were in it are being executed,
+so coderefs can push themselves onto it again if they so desire.
+.Sp
+This complements to the perl-eval commandline option, but gets executed
+first.
+.IP "@urxvt::TERM_EXT" 4
+.IX Item "@urxvt::TERM_EXT"
+Works similar to \f(CW@TERM_INIT\fR, but contains perl package/class names, which
+get registered as normal extensions after calling the hooks in \f(CW@TERM_INIT\fR
+but before other extensions. Gets cleared just like \f(CW@TERM_INIT\fR.
.ie n .Sh "Functions in the ""urxvt"" Package"
.el .Sh "Functions in the \f(CWurxvt\fP Package"
.IX Subsection "Functions in the urxvt Package"
.el .IP "$iow = \f(CW$iow\fR\->stop" 4
.IX Item "$iow = $iow->stop"
Stop watching for events on the given filehandle.
+.ie n .Sh "The ""urxvt::iw"" Class"
+.el .Sh "The \f(CWurxvt::iw\fP Class"
+.IX Subsection "The urxvt::iw Class"
+This class implements idle watchers, that get called automatically when
+the process is idle. They should return as fast as possible, after doing
+some useful work.
+.IP "$iw = new urxvt::iw" 4
+.IX Item "$iw = new urxvt::iw"
+Create a new idle watcher object in stopped state.
+.ie n .IP "$iw = $iw\fR\->cb (sub { my ($iw) = \f(CW@_; ... })" 4
+.el .IP "$iw = \f(CW$iw\fR\->cb (sub { my ($iw) = \f(CW@_\fR; ... })" 4
+.IX Item "$iw = $iw->cb (sub { my ($iw) = @_; ... })"
+Set the callback to be called when the watcher triggers.
+.ie n .IP "$timer = $timer\->start" 4
+.el .IP "$timer = \f(CW$timer\fR\->start" 4
+.IX Item "$timer = $timer->start"
+Start the watcher.
+.ie n .IP "$timer = $timer\->stop" 4
+.el .IP "$timer = \f(CW$timer\fR\->stop" 4
+.IX Item "$timer = $timer->stop"
+Stop the watcher.
+.ie n .Sh "The ""urxvt::pw"" Class"
+.el .Sh "The \f(CWurxvt::pw\fP Class"
+.IX Subsection "The urxvt::pw Class"
+This class implements process watchers. They create an event whenever a
+process exits, after which they stop automatically.
+.PP
+.Vb 9
+\& my $pid = fork;
+\& ...
+\& $term->{pw} = urxvt::pw
+\& ->new
+\& ->start ($pid)
+\& ->cb (sub {
+\& my ($pw, $exit_status) = @_;
+\& ...
+\& });
+.Ve
+.IP "$pw = new urxvt::pw" 4
+.IX Item "$pw = new urxvt::pw"
+Create a new process watcher in stopped state.
+.ie n .IP "$pw = $pw\fR\->cb (sub { my ($pw, \f(CW$exit_status\fR) = \f(CW@_; ... })" 4
+.el .IP "$pw = \f(CW$pw\fR\->cb (sub { my ($pw, \f(CW$exit_status\fR) = \f(CW@_\fR; ... })" 4
+.IX Item "$pw = $pw->cb (sub { my ($pw, $exit_status) = @_; ... })"
+Set the callback to be called when the timer triggers.
+.ie n .IP "$pw = $timer\->start ($pid)" 4
+.el .IP "$pw = \f(CW$timer\fR\->start ($pid)" 4
+.IX Item "$pw = $timer->start ($pid)"
+Tells the wqtcher to start watching for process \f(CW$pid\fR.
+.ie n .IP "$pw = $pw\->stop" 4
+.el .IP "$pw = \f(CW$pw\fR\->stop" 4
+.IX Item "$pw = $pw->stop"
+Stop the watcher.
.SH "ENVIRONMENT"
.IX Header "ENVIRONMENT"
.Sh "\s-1URXVT_PERL_VERBOSITY\s0"
rxvt -pe <extensionname>
+ Or by adding them to the resource for extensions loaded by default:
+
+ URxvt.perl-ext-common: default,automove-background,selection-autotransform
+
selection (enabled by default)
(More) intelligent selection. This extension tries to be more
intelligent when the user extends selections (double-click and
of every error message as a selection pattern, and the second line
transforms the message into vi commands to load the file.
+ tabbed
+ This transforms the terminal into a tabbar with additional
+ terminals, that is, it implements what is commonly refered to as
+ "tabbed terminal". The topmost line displays a "[NEW]" button,
+ which, when clicked, will add a new tab, followed by one button per
+ tab.
+
+ Clicking a button will activate that tab. Pressing Shift-Left and
+ Shift-Right will switch to the tab left or right of the current one.
+
mark-urls
Uses per-line display filtering ("on_line_update") to underline urls
and make them clickable. When middle-clicked, the program specified
The first argument passed to them is an extension oject as described in
the in the "Extension Objects" section.
- All of these hooks must return a boolean value. If it is true, then the
- event counts as being *consumed*, and the invocation of other hooks is
- skipped, and the relevant action might not be carried out by the C++
- code.
+ All of these hooks must return a boolean value. If any of the called
+ hooks returns true, then the event counts as being *consumed*, and the
+ relevant action might not be carried out by the C++ code.
*When in doubt, return a false value (preferably "()").*
windows are created or the command gets run. Most methods are unsafe
to call or deliver senseless data, as terminal size and other
characteristics have not yet been determined. You can safely query
- and change resources, though.
+ and change resources and options, though. For many purposes the
+ "on_start" hook is a better place.
+
+ on_start $term
+ Called at the very end of initialisation of a new terminal, just
+ before trying to map (display) the toplevel and returning to the
+ mainloop.
+
+ on_destroy $term
+ Called whenever something tries to destroy terminal, before doing
+ anything yet. If this hook returns true, then destruction is
+ skipped, but this is rarely a good idea.
on_reset $term
Called after the screen is "reset" for any reason, such as resizing
or control sequences. Here is where you can react on changes to
size-related variables.
- on_start $term
- Called at the very end of initialisation of a new terminal, just
- before returning to the mainloop.
-
on_child_start $term, $pid
Called just after the child process has been "fork"ed.
subwindow.
+ on_client_message $term, $event
+ on_wm_protocols $term, $event
+ on_wm_delete_window $term, $event
+ Called when various types of ClientMessage events are received (all
+ with format=32, WM_PROTOCOLS or WM_PROTOCOLS:WM_DELETE_WINDOW).
+
Variables in the "urxvt" Package
$urxvt::LIBDIR
The rxvt-unicode library directory, where, among other things, the
The current terminal. This variable stores the current "urxvt::term"
object, whenever a callback/hook is executing.
+ @urxvt::TERM_INIT
+ All coderefs in this array will be called as methods of the next
+ newly created "urxvt::term" object (during the "on_init" phase). The
+ array gets cleared before the codereferences that were in it are
+ being executed, so coderefs can push themselves onto it again if
+ they so desire.
+
+ This complements to the perl-eval commandline option, but gets
+ executed first.
+
+ @urxvt::TERM_EXT
+ Works similar to @TERM_INIT, but contains perl package/class names,
+ which get registered as normal extensions after calling the hooks in
+ @TERM_INIT but before other extensions. Gets cleared just like
+ @TERM_INIT.
+
Functions in the "urxvt" Package
urxvt::fatal $errormessage
Fatally aborts execution with the given error message. Avoid at all
$iow = $iow->stop
Stop watching for events on the given filehandle.
+ The "urxvt::iw" Class
+ This class implements idle watchers, that get called automatically when
+ the process is idle. They should return as fast as possible, after doing
+ some useful work.
+
+ $iw = new urxvt::iw
+ Create a new idle watcher object in stopped state.
+
+ $iw = $iw->cb (sub { my ($iw) = @_; ... })
+ Set the callback to be called when the watcher triggers.
+
+ $timer = $timer->start
+ Start the watcher.
+
+ $timer = $timer->stop
+ Stop the watcher.
+
+ The "urxvt::pw" Class
+ This class implements process watchers. They create an event whenever a
+ process exits, after which they stop automatically.
+
+ my $pid = fork;
+ ...
+ $term->{pw} = urxvt::pw
+ ->new
+ ->start ($pid)
+ ->cb (sub {
+ my ($pw, $exit_status) = @_;
+ ...
+ });
+
+ $pw = new urxvt::pw
+ Create a new process watcher in stopped state.
+
+ $pw = $pw->cb (sub { my ($pw, $exit_status) = @_; ... })
+ Set the callback to be called when the timer triggers.
+
+ $pw = $timer->start ($pid)
+ Tells the wqtcher to start watching for process $pid.
+
+ $pw = $pw->stop
+ Stop the watcher.
+
ENVIRONMENT
URXVT_PERL_VERBOSITY
This variable controls the verbosity level of the perl extension. Higher
every error message as a selection pattern, and the second line transforms
the message into vi commands to load the file.
+=item tabbed
+
+This transforms the terminal into a tabbar with additional terminals, that
+is, it implements what is commonly refered to as "tabbed terminal". The topmost line
+displays a "[NEW]" button, which, when clicked, will add a new tab, followed by one
+button per tab.
+
+Clicking a button will activate that tab. Pressing Shift-Left and
+Shift-Right will switch to the tab left or right of the current one.
+
=item mark-urls
Uses per-line display filtering (C<on_line_update>) to underline urls and
// VERSION _must_ be \d.\d+
-#define VERSION "7.1"
+#define VERSION "7.2"
#define DATE "2006-01-19"
projects / dana / urxvt.git / commitdiff