| … | |
… | |
| 322 | |
322 | |
| 323 | Right now, rxvt will first unmap/map the specified window, so it |
323 | Right now, rxvt will first unmap/map the specified window, so it |
| 324 | shouldn't be a top-level window. rxvt will also reconfigure it quite |
324 | shouldn't be a top-level window. rxvt will also reconfigure it quite |
| 325 | a bit, so don't expect it to keep some specific state. It's best to |
325 | a bit, so don't expect it to keep some specific state. It's best to |
| 326 | create an extra subwindow for rxvt and leave it alone. |
326 | create an extra subwindow for rxvt and leave it alone. |
|
|
327 | |
|
|
328 | The window will not be destroyed when rxvt exits. |
| 327 | |
329 | |
| 328 | It might be useful to know that rxvt will not close file descriptors |
330 | It might be useful to know that rxvt will not close file descriptors |
| 329 | passed to it (except for stdin/out/err, of course), so you can use |
331 | passed to it (except for stdin/out/err, of course), so you can use |
| 330 | file descriptors to communicate with the programs within the |
332 | file descriptors to communicate with the programs within the |
| 331 | terminal. This works regardless of wether the "-embed" option was |
333 | terminal. This works regardless of wether the "-embed" option was |
