… | |
… | |
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 | |
|
|
451 | As an extremely special case, specifying C<-1> will completely suppress |
|
|
452 | pty/tty operations. |
450 | |
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; |