flush
Differences
This shows you the differences between two versions of the page.
| — |
flush [2006/08/01 03:13] (current) |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ======Synopsis:====== | ||
| + | __flush__ | ||
| + | |||
| + | ======Description:====== | ||
| + | This command effectively does a /[[REDIRECT]] 0 WAIT. In other words, it | ||
| + | suppresses all output to all of your windows from your current server for one | ||
| + | full "[[WAIT]]" cycle (the time it takes for a command to go out to the server | ||
| + | and come back) | ||
| + | |||
| + | This discards any incoming data from the server until a full second passes with | ||
| + | no new data from the server. This also discards the contents of the window's | ||
| + | "hold buffer" when you are in [[window HOLD_MODE|HOLD_MODE]]. | ||
| + | |||
| + | The __FLUSH__ command is non-blocking, and does not interfere with the | ||
| + | normal operation of other servers. | ||
| + | |||
| + | The __FLUSH__ command cannot actually tell the server to stop sending you | ||
| + | data; if you are being flooded, you will simply have to wait until the | ||
| + | flood stops. | ||
flush.txt ยท Last modified: 2006/08/01 03:13 (external edit)
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 4.0 International
