… | |
… | |
454 | Right now, @@RXVT_NAME@@ will first unmap/map the specified window, so it |
454 | Right now, @@RXVT_NAME@@ will first unmap/map the specified window, so it |
455 | shouldn't be a top-level window. @@RXVT_NAME@@ will also reconfigure it |
455 | shouldn't be a top-level window. @@RXVT_NAME@@ will also reconfigure it |
456 | quite a bit, so don't expect it to keep some specific state. It's best to |
456 | quite a bit, so don't expect it to keep some specific state. It's best to |
457 | create an extra subwindow for @@RXVT_NAME@@ and leave it alone. |
457 | create an extra subwindow for @@RXVT_NAME@@ and leave it alone. |
458 | .Sp |
458 | .Sp |
|
|
459 | The window will not be destroyed when @@RXVT_NAME@@ exits. |
|
|
460 | .Sp |
459 | It might be useful to know that @@RXVT_NAME@@ will not close file |
461 | It might be useful to know that @@RXVT_NAME@@ will not close file |
460 | descriptors passed to it (except for stdin/out/err, of course), so you |
462 | descriptors passed to it (except for stdin/out/err, of course), so you |
461 | can use file descriptors to communicate with the programs within the |
463 | can use file descriptors to communicate with the programs within the |
462 | terminal. This works regardless of wether the \f(CW\*(C`\-embed\*(C'\fR option was used or |
464 | terminal. This works regardless of wether the \f(CW\*(C`\-embed\*(C'\fR option was used or |
463 | not. |
465 | not. |