Window
For managing windows interactively, see the window command:
/window [window-reference] operation [arguments ...] ...
For programmatic queries and changes, see windowctl. For the event fired when output reaches a window, see on window. These are distinct interfaces.
Servers and screens
Windows hold output and associate it with servers, channels, query targets, and levels. Several windows can share one server connection. A screen is the terminal/input surface containing visible windows; hidden windows have no screen but can still receive routed output and retain history. Hiding is different from destroying a window.
A window associated with a server in reconnect state can initiate its connection. Losing the last associated window can close the connection when the server's autoclose policy is enabled; this is not an unconditional rule for every server. See server states.
Operation guide
| Purpose | Starting points |
|---|---|
| Server association | server, noserv. |
| Message routing and targets | channel, query, add, remove, level, rejoin, echo. |
| Placement and selection | new, new_hide, hide, show, swap, refnum, refnum_or_swap, balance, size. |
| Views and held output | clear, flush, hold_mode, scroll_backward, scroll_forward, scroll_end, scrollback. |
| Status and activity | double, status_format, status_special, notify, notify_level. |
| Retention, identity, and lifetime | lastlog, lastlog_level, log, logfile, name, number, describe, list, kill. |
Single-row and double-row status formats are separate: status_format1 supplies the top row and status_format2 the bottom row in double mode. Notification flags, activity messages, and custom activity formatting also have separate rules; see status lines and window activity handling.
Chaining operations
The initial target is the current window, not the server. A reference selects the target of subsequent operations without necessarily making it the input window. Each handler can change the target passed to the next operation. Invalid operations or references and handler failures stop further processing, but not every diagnostic is a failing return. Earlier changes are not rolled back.
Use full operation names: the dispatcher accepts prefixes in table order rather than universally rejecting ambiguous abbreviations. Each operation consumes its own arguments, so quote a string when that operation requires a single argument containing spaces. The command reference documents supported operations and current limitations; do not infer support from historical operation names alone.
History and source
The window command existed in ircII2.1.5g; many operations are EPIC extensions.
source/window.c: operation registry, dispatcher, window/server associations, and lifecycle.source/status.c: status-row selection and formatting.source/screen.c: window output routing.source/functions.c:windowctlfunction interface.