| … | |
… | |
| 435 | $rxvt->signal_connect_after (realize => sub { |
435 | $rxvt->signal_connect_after (realize => sub { |
| 436 | my $xid = $_[0]->window->get_xid; |
436 | my $xid = $_[0]->window->get_xid; |
| 437 | system "@@RXVT_NAME@@ -embed $xid &"; |
437 | system "@@RXVT_NAME@@ -embed $xid &"; |
| 438 | }); |
438 | }); |
| 439 | |
439 | |
| 440 | =item B<-pty-fd> I<fileno> |
440 | =item B<-pty-fd> I<file descriptor> |
| 441 | |
441 | |
| 442 | Tells @@RXVT_NAME@@ NOT to execute any commands or create a new pty/tty |
442 | Tells @@RXVT_NAME@@ NOT to execute any commands or create a new pty/tty |
| 443 | pair but instead use the given filehandle as the tty master. This is |
443 | pair but instead use the given filehandle as the tty master. This is |
| 444 | useful if you want to drive @@RXVT_NAME@@ as a generic terminal emulator |
444 | useful if you want to drive @@RXVT_NAME@@ as a generic terminal emulator |
| 445 | without having to run a program within it. |
445 | without having to run a program within it. |
| 446 | |
446 | |
| 447 | If this switch is given, @@RXVT_NAME@@ will not create any utmp/wtmp |
447 | If this switch is given, @@RXVT_NAME@@ will not create any utmp/wtmp |
| 448 | entries and will not tinker with pty/tty permissions - you have to do that |
448 | entries and will not tinker with pty/tty permissions - you have to do that |
| 449 | yourself if you want that. |
449 | yourself if you want that. |
| 450 | |
450 | |
|
|
451 | As an extremely special case, specifying C<-1> will completely suppress |
|
|
452 | pty/tty operations. |
|
|
453 | |
| 451 | Here is a example in perl that illustrates how this option can be used (a |
454 | Here is a example in perl that illustrates how this option can be used (a |
| 452 | longer example is in F<doc/pty-fd>): |
455 | longer example is in F<doc/pty-fd>): |
| 453 | |
456 | |
| 454 | use IO::Pty; |
457 | use IO::Pty; |
| 455 | use Fcntl; |
458 | use Fcntl; |
| … | |
… | |
| 463 | my $slave = $pty->slave; |
466 | my $slave = $pty->slave; |
| 464 | while (<$slave>) { print $slave "got <$_>\n" } |
467 | while (<$slave>) { print $slave "got <$_>\n" } |
| 465 | |
468 | |
| 466 | =item B<-pe> I<string> |
469 | =item B<-pe> I<string> |
| 467 | |
470 | |
| 468 | Colon-separated list of perl extension scripts to use in this terminal |
471 | Comma-separated list of perl extension scripts to use (or not to use) in |
| 469 | instance. See resource B<perl-ext>. |
472 | this terminal instance. See resource B<perl-ext> for details. |
| 470 | |
473 | |
| 471 | =back |
474 | =back |
| 472 | |
475 | |
| 473 | =head1 RESOURCES (available also as long-options) |
476 | =head1 RESOURCES (available also as long-options) |
| 474 | |
477 | |
| … | |
… | |
| 1081 | |
1084 | |
| 1082 | =item B<perl-ext-common>: I<string> |
1085 | =item B<perl-ext-common>: I<string> |
| 1083 | |
1086 | |
| 1084 | =item B<perl-ext>: I<string> |
1087 | =item B<perl-ext>: I<string> |
| 1085 | |
1088 | |
| 1086 | Colon-separated list(s) of perl extension scripts to use in this terminal |
1089 | Comma-separated list(s) of perl extension scripts (default: C<default>) to |
|
|
1090 | use in this terminal instance; option B<-pe>. |
|
|
1091 | |
|
|
1092 | Extension names can be prefixed with a C<-> sign to prohibit using |
|
|
1093 | it. This can be useful to selectively disable some extensions loaded |
|
|
1094 | by default, or specified via the C<perl-ext-common> resource. For |
|
|
1095 | example, C<default,-selection> will use all the default extension except |
|
|
1096 | C<selection>. |
|
|
1097 | |
| 1087 | instance. Each extension is looked up in the library directories, loaded |
1098 | Each extension is looked up in the library directories, loaded if |
| 1088 | if necessary, and bound to the current terminal instance. If this |
1099 | necessary, and bound to the current terminal instance. |
| 1089 | resource is empty or missing, then the perl interpreter will not be |
1100 | |
| 1090 | initialized. The idea behind two options is that B<perl-ext-common> will |
1101 | If both of these resources are the empty string, then the perl |
| 1091 | be used for extensions that should be available to all instances, while |
1102 | interpreter will not be initialized. The idea behind two options is that |
| 1092 | B<perl-ext> is used for specific instances; option B<-pe>. |
1103 | B<perl-ext-common> will be used for extensions that should be available to |
|
|
1104 | all instances, while B<perl-ext> is used for specific instances. |
| 1093 | |
1105 | |
| 1094 | =item B<perl-eval>: I<string> |
1106 | =item B<perl-eval>: I<string> |
| 1095 | |
1107 | |
| 1096 | Perl code to be evaluated when all extensions have been registered. See the |
1108 | Perl code to be evaluated when all extensions have been registered. See the |
| 1097 | @@RXVT_NAME@@perl(3) manpage. |
1109 | @@RXVT_NAME@@perl(3) manpage. |
