ViewVC Help
View File | Revision Log | Show Annotations | Download File
/cvs/rxvt-unicode/doc/rxvt.1.pod
(Generate patch)

Comparing rxvt-unicode/doc/rxvt.1.pod (file contents):
Revision 1.58 by root, Wed Feb 16 21:49:36 2005 UTC vs.
Revision 1.59 by root, Thu Feb 17 15:07:48 2005 UTC

368=item B<-ssr>|B<+ssr> 368=item B<-ssr>|B<+ssr>
369 369
370Turn on/off secondary screen scroll (default enabled); resource 370Turn on/off secondary screen scroll (default enabled); resource
371B<secondaryScroll>. 371B<secondaryScroll>.
372 372
373=item B<-keysym.>I<sym>: I<string> 373=item B<-keysym.>I<sym> I<string>
374 374
375Remap a key symbol. See resource B<keysym>. 375Remap a key symbol. See resource B<keysym>.
376 376
377=item B<-embed>: I<windowid> 377=item B<-embed> I<windowid>
378 378
379Tells @@RXVT_NAME@@ to embed it's windows into an already-existing window, 379Tells @@RXVT_NAME@@ to embed it's windows into an already-existing window,
380which enables applications to easily embed a terminal. 380which enables applications to easily embed a terminal.
381 381
382Right now, @@RXVT_NAME@@ will first unmap/map the specified window, so it 382Right now, @@RXVT_NAME@@ will first unmap/map the specified window, so it
389It might be useful to know that @@RXVT_NAME@@ will not close file 389It might be useful to know that @@RXVT_NAME@@ will not close file
390descriptors passed to it (except for stdin/out/err, of course), so you 390descriptors passed to it (except for stdin/out/err, of course), so you
391can use file descriptors to communicate with the programs within the 391can use file descriptors to communicate with the programs within the
392terminal. This works regardless of wether the C<-embed> option was used or 392terminal. This works regardless of wether the C<-embed> option was used or
393not. 393not.
394
395Here is a short Gtk2-perl snippet that illustrates how this option can be
396used (a longer example is in F<doc/embed>):
397
398 my $rxvt = new Gtk2::DrawingArea;
399 $...->add ($rxvt); # important to add it somewhere first
400 $rxvt->realize; # now it can be realized
401 my $xid = $rxvt->window->get_xid;
402
403 system "@@RXVT_NAME@@ -embed $xid &";
404
405=item B<-pty-fd> I<fileno>
406
407Tells @@RXVT_NAME@@ NOT to execute any commands or create a new pty/tty
408pair but instead use the given filehandle as the tty master. This is
409useful if you want to drive @@RXVT_NAME@@ as a generic terminal emulator
410without having to run a program within it.
411
412If this switch is given, @@RXVT_NAME@@ will not create any utmp/wtmp
413entries and will not tinker with pty/tty permissions - you have to do that
414yourself if you want that.
415
416Here is a example in perl that illustrates how this option can be used (a
417longer example is in F<doc/pty-fd>):
418
419 use IO::Pty;
420 use Fcntl;
421
422 my $pty = new IO::Pty;
423 fcntl $pty, F_SETFD, 0; # clear close-on-exec
424
425 system "@@RXVT_NAME@@ -pty-fd " . (fileno $pty) . "&";
426
427 # now communicate with rxvt
428 my $slave = $pty->slave;
429 while (<$slave>) { print $slave "got <$_>\n" }
394 430
395=back 431=back
396 432
397=head1 RESOURCES (available also as long-options) 433=head1 RESOURCES (available also as long-options)
398 434

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines