--- rxvt-unicode/src/urxvt.pm	2006/01/18 19:44:22	1.106
+++ rxvt-unicode/src/urxvt.pm	2006/01/19 21:02:06	1.112
@@ -37,6 +37,10 @@
 
   @@RXVT_NAME@@ -pe <extensionname>
 
+Or by adding them to the resource for extensions loaded by default:
+
+  URxvt.perl-ext-common: default,automove-background,selection-autotransform
+
 =over 4
 
 =item selection (enabled by default)
@@ -91,8 +95,9 @@
 text into various other formats/action (such as uri unescaping, perl
 evalution, web-browser starting etc.), depending on content.
 
-Other extensions can extend this popup menu by pushing a code reference onto
-C<@urxvt::ext::selection_popup::hook>, that is called whenever the popup is displayed.
+Other extensions can extend this popup menu by pushing a code reference
+onto C<@{ $term->{selection_popup_hook} }>, that is called whenever the
+popup is displayed.
 
 It's sole argument is the popup menu, which can be modified. The selection
 is in C<$_>, which can be used to decide wether to add something or not.
@@ -104,7 +109,7 @@
 the selection to C<b>s, but only if the selection currently contains any
 C<a>s:
 
-   push urxvt::ext::selection_popup::hook, sub {
+   push @{ $self->{term}{selection_popup_hook} }, sub {
       /a/ ? ("a to be" => sub { s/a/b/g }
           : ()
    };
@@ -145,15 +150,15 @@
 And this example matches the same,but replaces it with vi-commands you can
 paste directly into your (vi :) editor:
 
-   URxvt.selection-autotransform.0: s/^([^:[:space:]]+(\\d+):?$/\\x1b:e \\Q$1\\E\\x0d:$2\\x0d/
+   URxvt.selection-autotransform.0: s/^([^:[:space:]]+(\\d+):?$/:e \\Q$1\\E\\x0d:$2\\x0d/
 
 Of course, this can be modified to suit your needs and your editor :)
 
 To expand the example above to typical perl error messages ("XXX at
 FILENAME line YYY."), you need a slightly more elaborate solution:
 
-   URxvt.selection.pattern-0: ( at .*? line \\d+\\.)
-   URxvt.selection-autotransform.0: s/^ at (.*?) line (\\d+)\\.$/\x1b:e \\Q$1\E\\x0d:$2\\x0d/
+   URxvt.selection.pattern-0: ( at .*? line \\d+[,.])
+   URxvt.selection-autotransform.0: s/^ at (.*?) line (\\d+)[,.]$/:e \\Q$1\E\\x0d:$2\\x0d/
 
 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
@@ -300,9 +305,9 @@
 The first argument passed to them is an extension oject as described in
 the in the C<Extension Objects> section.
 
-B<All> of these hooks must return a boolean value. If it is true, then the
-event counts as being I<consumed>, and the invocation of other hooks is
-skipped, and the relevant action might not be carried out by the C++ code.
+B<All> of these hooks must return a boolean value. If any of the called
+hooks returns true, then the event counts as being I<consumed>, and the
+relevant action might not be carried out by the C++ code.
 
 I<< When in doubt, return a false value (preferably C<()>). >>
 
@@ -313,8 +318,14 @@
 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 C<on_start> hook is a better
+place.
+
+=item on_start $term
+
+Called at the very end of initialisation of a new terminal, just before
+returning to the mainloop.
 
 =item on_reset $term
 
@@ -322,10 +333,14 @@
 control sequences. Here is where you can react on changes to size-related
 variables.
 
-=item on_start $term
+=item on_child_start $term, $pid
 
-Called at the very end of initialisation of a new terminal, just before
-returning to the mainloop.
+Called just after the child process has been C<fork>ed.
+
+=item on_child_exit $term, $status
+
+Called just after the child process has exited. C<$status> is the status
+from C<waitpid>.
 
 =item on_sel_make $term, $eventtime
 
@@ -632,12 +647,6 @@
          unless $msg =~ /\n$/;
       urxvt::warn ($msg);
    };
-
-   # %ENV is the original startup environment
-   delete $ENV{IFS};
-   delete $ENV{CDPATH};
-   delete $ENV{BASH_ENV};
-   $ENV{PATH} = "/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin:/opt/bin:/opt/sbin";
 }
 
 my $verbosity = $ENV{URXVT_PERL_VERBOSITY};
@@ -728,8 +737,7 @@
       keys %$cb;
 
       while (my ($pkg, $cb) = each %$cb) {
-         $retval = eval { $cb->($TERM->{_pkg}{$pkg}, @_) }
-            and last;
+         $retval ||= eval { $cb->($TERM->{_pkg}{$pkg}, @_) };
 
          if ($@) {
             $TERM->ungrab; # better to lose the grab than the session
@@ -752,18 +760,6 @@
    $retval
 }
 
-sub exec_async(@) {
-   my $pid = fork;
-
-   return
-      if !defined $pid or $pid;
-
-   %ENV = %{ $TERM->env };
-
-   exec @_;
-   _exit 255;
-}
-
 # urxvt::term::extension
 
 package urxvt::term::extension;
@@ -950,6 +946,31 @@
 etc.). Please note that @@RXVT_NAME@@ will not exit as long as any event
 watchers (timers, io watchers) are still active.
 
+=item $term->exec_async ($cmd[, @args])
+
+Works like the combination of the C<fork>/C<exec> builtins, which executes
+("starts") programs in the background. This function takes care of setting
+the user environment before exec'ing the command (e.g. C<PATH>) and should
+be preferred over explicit calls to C<exec> or C<system>.
+
+Returns the pid of the subprocess or C<undef> on error.
+
+=cut
+
+sub exec_async {
+   my $self = shift;
+
+   my $pid = fork;
+
+   return $pid
+      if !defined $pid or $pid;
+
+   %ENV = %{ $self->env };
+
+   exec @_;
+   urxvt::_exit 255;
+}
+
 =item $isset = $term->option ($optval[, $set])
 
 Returns true if the option specified by C<$optval> is enabled, and