… | |
… | |
371 | $rxvt->signal_connect_after (realize => sub { |
371 | $rxvt->signal_connect_after (realize => sub { |
372 | my $xid = $_[0]->window->get_xid; |
372 | my $xid = $_[0]->window->get_xid; |
373 | system "rxvt -embed $xid &"; |
373 | system "rxvt -embed $xid &"; |
374 | }); |
374 | }); |
375 | |
375 | |
376 | -pty-fd *fileno* |
376 | -pty-fd *file descriptor* |
377 | Tells rxvt NOT to execute any commands or create a new pty/tty pair |
377 | Tells rxvt NOT to execute any commands or create a new pty/tty pair |
378 | but instead use the given filehandle as the tty master. This is |
378 | but instead use the given filehandle as the tty master. This is |
379 | useful if you want to drive rxvt as a generic terminal emulator |
379 | useful if you want to drive rxvt as a generic terminal emulator |
380 | without having to run a program within it. |
380 | without having to run a program within it. |
381 | |
381 | |
382 | If this switch is given, rxvt will not create any utmp/wtmp entries |
382 | If this switch is given, rxvt will not create any utmp/wtmp entries |
383 | and will not tinker with pty/tty permissions - you have to do that |
383 | and will not tinker with pty/tty permissions - you have to do that |
384 | yourself if you want that. |
384 | yourself if you want that. |
385 | |
385 | |
|
|
386 | As an extremely special case, specifying -1 will completely suppress |
|
|
387 | pty/tty operations. |
|
|
388 | |
386 | Here is a example in perl that illustrates how this option can be |
389 | Here is a example in perl that illustrates how this option can be |
387 | used (a longer example is in doc/pty-fd): |
390 | used (a longer example is in doc/pty-fd): |
388 | |
391 | |
389 | use IO::Pty; |
392 | use IO::Pty; |
390 | use Fcntl; |
393 | use Fcntl; |
… | |
… | |
397 | # now communicate with rxvt |
400 | # now communicate with rxvt |
398 | my $slave = $pty->slave; |
401 | my $slave = $pty->slave; |
399 | while (<$slave>) { print $slave "got <$_>\n" } |
402 | while (<$slave>) { print $slave "got <$_>\n" } |
400 | |
403 | |
401 | -pe *string* |
404 | -pe *string* |
402 | Colon-separated list of perl extension scripts to use in this |
405 | Comma-separated list of perl extension scripts to use in this |
403 | terminal instance. See resource perl-ext. |
406 | terminal instance. See resource perl-ext. |
404 | |
407 | |
405 | RESOURCES (available also as long-options) |
408 | RESOURCES (available also as long-options) |
406 | Note: `rxvt --help' gives a list of all resources (long options) |
409 | Note: `rxvt --help' gives a list of all resources (long options) |
407 | compiled into your version. |
410 | compiled into your version. |
… | |
… | |
938 | URxvt.keysym.M-C-3: command:\033[8;25;80t |
941 | URxvt.keysym.M-C-3: command:\033[8;25;80t |
939 | URxvt.keysym.M-C-4: command:\033[8;48;110t |
942 | URxvt.keysym.M-C-4: command:\033[8;48;110t |
940 | |
943 | |
941 | perl-ext-common: *string* |
944 | perl-ext-common: *string* |
942 | perl-ext: *string* |
945 | perl-ext: *string* |
943 | Colon-separated list(s) of perl extension scripts to use in this |
946 | Comma-separated list(s) of perl extension scripts to use in this |
944 | terminal instance. Each extension is looked up in the library |
947 | terminal instance. Each extension is looked up in the library |
945 | directories, loaded if necessary, and bound to the current terminal |
948 | directories, loaded if necessary, and bound to the current terminal |
946 | instance. If this resource is empty or missing, then the perl |
949 | instance. If this resource is empty or missing, then the perl |
947 | interpreter will not be initialized. The idea behind two options is |
950 | interpreter will not be initialized. The idea behind two options is |
948 | that perl-ext-common will be used for extensions that should be |
951 | that perl-ext-common will be used for extensions that should be |