… | |
… | |
381 | |
381 | |
382 | Right now, @@RXVT_NAME@@ will first unmap/map the specified window, so it |
382 | Right now, @@RXVT_NAME@@ will first unmap/map the specified window, so it |
383 | shouldn't be a top-level window. @@RXVT_NAME@@ will also reconfigure it |
383 | shouldn't be a top-level window. @@RXVT_NAME@@ will also reconfigure it |
384 | quite a bit, so don't expect it to keep some specific state. It's best to |
384 | quite a bit, so don't expect it to keep some specific state. It's best to |
385 | create an extra subwindow for @@RXVT_NAME@@ and leave it alone. |
385 | create an extra subwindow for @@RXVT_NAME@@ and leave it alone. |
|
|
386 | |
|
|
387 | The window will not be destroyed when @@RXVT_NAME@@ exits. |
386 | |
388 | |
387 | It might be useful to know that @@RXVT_NAME@@ will not close file |
389 | It might be useful to know that @@RXVT_NAME@@ will not close file |
388 | descriptors passed to it (except for stdin/out/err, of course), so you |
390 | descriptors passed to it (except for stdin/out/err, of course), so you |
389 | can use file descriptors to communicate with the programs within the |
391 | can use file descriptors to communicate with the programs within the |
390 | terminal. This works regardless of wether the C<-embed> option was used or |
392 | terminal. This works regardless of wether the C<-embed> option was used or |