3 <h3>To new Irssi users (not to new IRC users ..)</h3>
5 <p>Copyright (c) 2000-2002 by Timo Sirainen</p>
8 <p>Index with some FAQ questions that are answered in the chapter:</p>
11 <li><a href="#c1">For all the lazy people</a></li>
12 <li><a href="#c2">Basic user interface usage</a>
14 <li>Split windows work in weird way</li>
16 <li><a href="#c3">Server and channel automation</a>
18 <li>How do I automatically connect to servers at startup?</li>
19 <li>How do I automatically join to channels at startup?</li>
21 <li><a href="#c4">Setting up windows and automatically restoring them
23 <li><a href="#c5">Status and msgs windows & message levels</a>
25 <li>I want /WHOIS to print reply to current window</li>
26 <li>I want all messages to go to one window, not create new windows</li>
28 <li><a href="#c6">How support for multiple servers works in irssi</a>
30 <li>I connected to some server that doesn't respond and now irssi
31 keeps trying to reconnect to it again and again, how can I stop
33 <li>I want to have own status and/or msgs window for each servers</li>
35 <li><a href="#c7">/LASTLOG and jumping around in scrollback</a>
37 <li>How can I save all texts in a window to file?</li>
39 <li><a href="#c8">Logging</a></li>
40 <li><a href="#c9">Changing keyboard bindings</a>
42 <li>How do I make F1 key do something?</li>
44 <li><a href="#c10">Proxies and IRC bouncers</a></li>
45 <li><a href="#c11">Irssi's settings</a></li>
48 <h3><a id="c1">1. For all the lazy people</a></h3>
50 <p>These settings should give you pretty good defaults (the ones I use):</p>
52 <p>I don't like automatic query windows, I don't like status window, I do
53 like msgs window where all messages go:</p>
56 /SET autocreate_own_query OFF
57 /SET autocreate_query_level DCCMSGS
58 /SET use_status_window OFF
59 /SET use_msgs_window ON
62 <p>Disable automatic window closing when /PARTing channel or /UNQUERYing
66 /SET autoclose_windows OFF
67 /SET reuse_unused_windows ON
70 <p>And example how to add servers:</p>
72 <p>(openprojects network, identify with nickserv and wait for 2 seconds before
76 /IRCNET ADD -autosendcmd "/^msg nickserv ident pass;wait -opn 2000" opn
79 <p>Then add some servers to different networks (ircnet is already set up
80 for them), irc.kpnqwest.fi is used by default for IRCNet but if it fails,
81 irc.funet.fi is tried next:</p>
84 /SERVER ADD -auto -ircnet ircnet irc.kpnqwest.fi 6667
85 /SERVER ADD -ircnet ircnet irc.funet.fi 6667
86 /SERVER ADD -auto -ircnet efnet efnet.cs.hut.fi 6667
89 <p>Automatically join to channels after connected to server, send op request
90 to bot after joined to efnet/#irssi:</p>
93 /CHANNEL ADD -auto #irssi ircnet
94 /CHANNEL ADD -auto -bots *!*bot@host.org -botcmd "/^msg $0 op pass"
98 If you want lines containing your nick to hilight:
104 <h3><a id="c2">2. Basic user interface usage</a></h3>
106 <p>Windows can be scrolled up/down with PgUp and PgDown keys. If they don't
107 work for you, use Meta-p and Meta-n keys. For jumping to beginning or end of
108 the buffer, use /SB HOME and /SB END commands.</p>
110 <p>By default, irssi uses "hidden windows" for everything. Hidden
111 window is created every time you /JOIN a channel or /QUERY someone.
112 There's several ways you can change between these windows:</p>
115 Meta-1, Meta-2, .. Meta-0 - Jump directly between windows 1-10
116 Meta-q .. Meta-o - Jump directly between windows 11-19
117 /WINDOW <number> - Jump to any window with specified number
118 Ctrl-P, Ctrl-N - Jump to previous / next window
121 <p>Clearly the easiest way is to use Meta-number keys. And what is the Meta
122 key? For some terminals, it's the same as ALT. If you have Windows keyboard,
123 it's probably the left Windows key. If they don't work directly, you'll need
124 to set a few X resources (NOTE: these work with both xterm and rxvt):</p>
127 XTerm*eightBitInput: false
128 XTerm*metaSendsEscape: true
131 <p>With rxvt, you can also specify which key acts as Meta key. So if you
132 want to use ALT instead of Windows key for it, use:</p>
138 <p>You could do this by changing the X key mappings:</p>
141 xmodmap -e "keysym Alt_L = Meta_L Alt_L"
144 <p>And how exactly do you set these X resources? For Debian, there's
145 /etc/X11/Xresources/xterm file where you can put them and it's read
146 automatically when X starts. ~/.Xresources and ~/.Xdefaults files might also
147 work. If you can't get anything else to work, just copy&paste those lines to
148 ~/.Xresources and directly call "xrdb -merge ~/.Xresources" in some xterm.
149 The resources affect only the new xterms you start, not existing ones.</p>
151 <p>Many windows SSH clients also don't allow usage of ALT. One excellent
152 client that does allow is putty, you can download it from
153 <a href="http://www.chiark.greenend.org.uk/~sgtatham/putty/">
154 http://www.chiark.greenend.org.uk/~sgtatham/putty/</a>.</p>
156 <p>Irssi also supports split windows, they've had some problems in past
157 but I think they should work pretty well now :) Here's some commands
161 /WINDOW NEW - Create new split window
162 /WINDOW NEW HIDE - Create new hidden window
163 /WINDOW CLOSE - Close split or hidden window
165 /WINDOW HIDE [<number>|<name>] - Make the split window hidden window
166 /WINDOW SHOW <number>|<name> - Make the hidden window a split window
168 /WINDOW SHRINK [<lines>] - Shrink the split window
169 /WINDOW GROW [<lines>] - Grow the split window
170 /WINDOW BALANCE - Balance the sizes of all split windows
173 <p>By default, irssi uses "sticky windowing" for split windows. This means
174 that windows created inside one split window cannot be moved to another
175 split window without some effort. For example you could have following
179 Split window 1: win#1 - Status window, win#2 - Messages window
180 Split window 2: win#3 - ircnet/#channel1, win#4 - ircnet/#channel2
181 Split window 3: win#5 - efnet/#channel1, win#6 - efnet/#channel2
184 <p>When you are in win#1 and press ALT-6, irssi jumps to split window
185 #3 and moves the efnet/#channel2 the active window.</p>
187 <p>With non-sticky windowing the windows don't have any relationship with
188 split windows, pressing ALT-6 in win#1 moves win#6 to split window 1
189 and sets it active, except if win#6 was already visible in some other
190 split window irssi just changes to that split window. This it the way
191 windows work with ircii, if you prefer it you can set it with</p>
194 /SET autostick_split_windows OFF
197 <p>Each window can have multiple channels, queries and other "window
198 items" inside them. If you don't like windows at all, you disable
199 automatic creating of them with</p>
202 /SET autocreate_windows OFF
205 <p>If you want to group only some channels or queries in one window,
209 /JOIN -window #channel
213 <h3><a id="c3">3. Server and channel automation</a></h3>
215 <p>Irssi's multiple IRC network support is IMHO very good - at least
216 compared to other clients :) Even if you're only in one IRC network you
217 should group all your servers to be in the same IRC network as this
218 helps with reconnecting if your primary server breaks and is probably
219 useful in some other ways too :) For information how to actually use
220 irssi correctly with multiple servers see the chapter 6.</p>
222 <p>First you need to have your IRC network set, use /IRCNET command to
223 see if it's already there. If it isn't, use /IRCNET ADD yourircnet. To
224 make Irssi work properly with different IRC networks, you might need to
225 give some special settings to /IRCNET ADD, see manual.txt for more
226 information about them. Irssi defaults to IRCNet's behaviour.</p>
228 <p>After that you need to add your servers. For example:</p>
231 /SERVER ADD -auto -ircnet ircnet irc.kpnqwest.fi 6667
232 /SERVER ADD -auto -ircnet worknet irc.mycompany.com 6667 password
235 <p>The -auto option specifies that this server is automatically connected
236 at startup. You don't need to make more than one server with -auto
237 option to one IRC network, other servers are automatically connected in
238 same network if the -auto server fails.</p>
240 <p>And finally channels:</p>
243 /CHANNEL ADD -auto -bots *!*bot@host.org -botcmd "/^msg $0 op pass"
245 /CHANNEL ADD -auto #secret ircnet password
248 <p>-bots and -botcmd should be the only ones needing a bit of
249 explaining. They're used to send commands automatically to bot when
250 channel is joined, usually to get ops automatically. You can specify
251 multiple bot masks with -bots option separated with spaces (and
252 remember to quote the string then). The $0 in -botcmd specifies the
253 first found bot in the list. If you don't need the bot masks (ie. the
254 bot is always with the same nick, like chanserv) you can give only the
255 -botcmd option and the command is always sent.</p>
258 <h3><a id="c4">4. Setting up windows and automatically restoring them at startup</a></h3>
260 <p>First connect to all the servers, join the channels and create the
261 queries you want. If you want to move the windows or channels around
265 /WINDOW MOVE LEFT/RIGHT/number - move window elsewhere
266 /WINDOW ITEM MOVE <number>|<name> - move channel/query to another window
269 <p>When everything looks the way you like, use /LAYOUT SAVE command
270 (and /SAVE, if you don't have autosaving enabled) and when you start
271 irssi next time, irssi remembers the positions of the channels, queries
272 and everything. This "remembering" doesn't mean that simply using
273 /LAYOUT SAVE would automatically make irssi reconnect to all servers
274 and join all channels, you'll need the /SERVER ADD -auto and /CHANNEL
275 ADD -auto commands to do that.</p>
277 <p>If you want to change the layout, you just rearrange the layout like
278 you want it and use /LAYOUT SAVE again. If you want to remove the
279 layout for some reason, use /LAYOUT RESET.</p>
282 <h3><a id="c5">5. Status and msgs windows & message levels</a></h3>
284 <p>By default, all the "extra messages" go to status window. This means
285 pretty much all messages that don't clearly belong to some channel or
286 query. Some people like it, some don't. If you want to remove it, use</p>
289 /SET use_status_window OFF
292 <p>This doesn't have any effect until you restart irssi. If you want to
293 remove it immediately, just /WINDOW CLOSE it.</p>
295 <p>Another common window is "messages window", where all private
296 messages go. By default it's disabled and query windows are created
297 instead. To make all private messages go to msgs window, say:</p>
300 /SET use_msgs_window ON
301 /SET autocreate_query_level DCCMSGS (or if you don't want queries to
302 dcc chats either, say NONE)
305 <p>use_msgs_window either doesn't have any effect until restarting
306 irssi. To create it immediately say:</p>
309 /WINDOW NEW HIDE - create the window
310 /WINDOW NAME (msgs) - name it to "(msgs)"
311 /WINDOW LEVEL MSGS - make all private messages go to this window
312 /WINDOW MOVE 1 - move it to first window
315 <p>Note that neither use_msgs_window nor use_status_window have any
316 effect at all if /LAYOUT SAVE has been used.</p>
318 <p>This brings us to message levels.. What are they? All messages that
319 irssi prints have one or more "message levels". Most common are PUBLIC
320 for public messages in channels, MSGS for private messages and CRAP for
321 all sorts of messages with no real classification. You can get a whole
322 list of levels with</p>
328 <p>Status window has message level "ALL -MSGS", meaning that all messages,
329 except private messages, without more specific place go to status
330 window. The -MSGS is there so it doesn't conflict with messages
334 <h3><a id="c6">6. How support for multiple servers works in irssi</a></h3>
336 <p>ircii and several other clients support multiple servers by placing
337 the connection into some window. IRSSI DOES NOT. There is no required
338 relationship between window and server. You can connect to 10 servers
339 and manage them all in just one window, or join channel in each one of
340 them to one sigle window if you really want to. That being said, here's
341 how you do connect to new server without closing the old connection:</p>
344 /CONNECT irc.server.org
347 <p>Instead of the /SERVER which disconnects the existing connection. To
348 see list of all active connections, use /SERVER without any parameters.
349 You should see a list of something like:</p>
352 -!- IRCNet: irc.song.fi:6667 (IRCNet)
353 -!- OPN: tolkien.openprojects.net:6667 (OPN)
354 -!- RECON-1: 192.168.0.1:6667 () (02:59 left before reconnecting)
357 <p>Here you see that we're connected to IRCNet and OPN networks. The
358 the IRCNet at the beginning is called the "server tag" while the
359 (IRCnet) at the end shows the IRC network. Server tag specifies unique
360 tag to refer to the server, usually it's the same as the IRC network.
361 When the IRC network isn't known it's some part of the server name.
362 When there's multiple connections to same IRC network or server, irssi
363 adds a number after the tag so there could be ircnet, ircnet2, ircnet3
366 <p>Server tags beginning with RECON- mean server reconnections. Above we
367 see that connection to server at 192.168.0.1 wasn't successful and
368 irssi will try to connect it again in 3 minutes.</p>
370 <p>To disconnect one of the servers, or to stop irssi from
371 reconnecting, use</p>
374 /DISCONNECT ircnet - disconnect server with tag "ircnet"
375 /DISCONNECT recon-1 - stop trying to reconnect to RECON-1 server
376 /RMRECONNS - stop all server reconnections
378 /RECONNECT recon-1 - immediately try reconnecting back to RECON-1
379 /RECONNECT ALL - immediately try reconnecting back to all
380 servers in reconnection queue
383 <p>Now that you're connected to all your servers, you'll have to know how
384 to specify which one of them you want to use. One way is to have an
385 empty window, like status or msgs window. In it, you can specify which
386 server to set active with</p>
389 /WINDOW SERVER tag - set server "tag" active
390 Ctrl-X - set the next server in list active
393 <p>When the server is active, you can use it normally. When there's
394 multiple connected servers, irssi adds [servertag] prefix to all
395 messages in non-channel/query messages so you'll know where it came
398 <p>Several commands also accept -servertag option to specify which server
402 /MSG -tag nick message
407 <p>/MSG tab completion also automatically adds the -tag option when
408 nick isn't in active server.</p>
410 <p>Window's server can be made sticky. When sticky, it will never
411 automatically change to anything else, and if server gets disconnected, the
412 window won't have any active server. When the server gets connected again,
413 it is automatically set active in the window. To set the window's server
417 /WINDOW SERVER -sticky tag
420 <p>This is useful if you wish to have multiple status or msgs windows, one
421 for each server. Here's how to do them (repeat for each server)</p>
425 /WINDOW NAME (status)
426 /WINDOW LEVEL ALL -MSGS
427 /WINDOW SERVER -sticky ircnet
432 /WINDOW SERVER -sticky ircnet
435 <h3><a id="c7">7. /LASTLOG and jumping around in scrollback</a></h3>
437 <p>/LASTLOG command can be used for searching texts in scrollback
438 buffer. Simplest usages are</p>
441 /LASTLOG word - print all lines with "word" in them
442 /LASTLOG word 10 - print last 10 occurances of "word"
443 /LASTLOG -topics - print all topic changes
446 <p>If there's more than 1000 lines to be printed, irssi thinks that you
447 probably made some mistake and won't print them without -force option.
448 If you want to save the full lastlog to file, use</p>
451 /LASTLOG -file ~/irc.log
454 <p>With -file option you don't need -force even if there's more than 1000
455 lines. /LASTLOG has a lot of other options too, see /HELP lastlog for
458 <p>Once you've found the lines you were interested in, you might want
459 to check the discussion around them. Irssi has /SCROLLBACK (or alias
460 /SB) command for jumping around in scrollback buffer. Since /LASTLOG
461 prints the timestamp when the message was originally printed, you can
462 use /SB GOTO hh:mm to jump directly there. To get back to the bottom of
463 scrollback, use /SB END command.</p>
466 <h3><a id="c8">8. Logging</a></h3>
468 <p>Irssi can automatically log important messages when you're set away
469 (/AWAY reason). When you set yourself unaway (/AWAY), the new messages
470 in away log are printed to screen. You can configure it with:</p>
473 /SET awaylog_level MSGS HILIGHT - Specifies what messages to log
474 /SET awaylog_file ~/.irssi/away.log - Specifies the file to use
477 <p>Easiest way to start logging with Irssi is to use autologging. With it
478 Irssi logs all channels and private messages to specified directory.
479 You can turn it on with</p>
485 <p>By default it logs pretty much everything execept CTCPS or CRAP
486 (/WHOIS requests, etc). You can specify the logging level yourself with</p>
489 /SET autolog_level ALL -CRAP -CLIENTCRAP -CTCPS (this is the default)
492 <p>By default irssi logs to ~/irclogs/<servertag>/<target>.log.
493 You can change this with</p>
496 /SET autolog_path ~/irclogs/$tag/$0.log (this is the default)
499 <p>The path is automatically created if it doesn't exist. $0 specifies
500 the target (channel/nick). You can make irssi automatically rotate the
501 logs by adding date/time formats to the file name. The formats are in
502 "man strftime" format. For example</p>
505 /SET autolog_path ~/irclogs/%Y/$tag/$0.%m-%d.log
508 <p>For logging only some specific channels or nicks, see /HELP log</p>
511 <h3><a id="c9">9. Changing keyboard bindings</a></h3>
513 <p>You can change any keyboard binding that terminal lets irssi know
514 about. It doesn't let irssi know everything, so for example
515 shift-backspace can't be bound unless you modify xterm resources
518 <p>/HELP bind tells pretty much everything there is to know about
519 keyboard bindings. However, there's the problem of how to bind some
520 non-standard keys. They might differ a bit with each terminal, so
521 you'll need to find out what exactly the keypress produces. Easiest
522 way to check that would be to see what it prints in "cat". Here's
523 an example for pressing F1 key:</p>
530 <p>So in irssi you would use /BIND ^[OP /ECHO F1 pressed. If you use
531 multiple terminals which have different bindings for the key, it would
532 be better to use eg.:</p>
537 /BIND F1 /ECHO F1 pressed.
540 <h3><a id="c10">10. Proxies and IRC bouncers</a></h3>
542 <p>Irssi supports connecting to IRC servers via a proxy. All proxies have
543 these settings in common:</p>
547 /SET proxy_address <Proxy host address>
548 /SET proxy_port <Proxy port>
551 <p><strong>HTTP proxy</strong></p>
553 <p>Use these settings with HTTP proxies:</p>
556 /SET -clear proxy_password
557 /EVAL SET proxy_string CONNECT %s:%d\n\n
560 <p><strong>BNC</strong></p>
563 /SET proxy_password your_pass
564 /SET -clear proxy_string
565 /SET proxy_string conn %s %d
568 <p><strong>dircproxy</strong></p>
570 <p>dircproxy separates the server connections by passwords. So, if you
571 for example have ircnet connection with password ircpass and
572 openprojects connection with opnpass, you would do something like
576 /SET -clear proxy_password
577 /SET -clear proxy_string
579 /SERVER ADD -auto -ircnet ircnet fake.ircnet 6667 ircpass
580 /SERVER ADD -auto -ircnet opn fake.opn 6667 opnpass
583 <p>The server name and port you give isn't used anywhere, so you can
584 put anything you want in there.</p>
586 <p><strong>Irssi proxy</strong></p>
588 <p>Irssi contains it's own proxy which you can build giving
589 <strong>--with-proxy</strong> option to configure. You'll still need to run
590 irssi in a screen to use it though.</p>
592 <p>Irssi proxy is a bit different than most proxies, normally proxies create
593 a new connection to IRC server when you connect to it, but with irssi proxy
594 all the clients use the same IRC server connection (a bit like how screen -x
597 <p>Irssi proxy supports sharing multiple server connections in different
598 ports, like you can share ircnet in port 2777 and efnet in port 2778.</p>
600 <p>Usage in proxy side:</p>
604 /SET irssiproxy_password <password>
605 /SET irssiproxy_ports <ircnet>=<port> ... (eg. ircnet=2777 efnet=2778)
608 <p><strong>NOTE</strong>: you <strong>MUST</strong> add all the servers you
609 are using to server and ircnet lists with /SERVER ADD and /IRCNET ADD.
610 ..Except if you really don't want to for some reason, and you only use
611 one server connection, you may simply set:</p>
614 /SET irssiproxy_ports *=2777
617 <p>Usage in client side:</p>
619 <p>Just connect to the irssi proxy like it is a normal server with password
620 specified in /SET irssiproxy_password. For example:</p>
623 /SERVER ADD -ircnet ircnet my.irssi-proxy.org 2777 secret
624 /SERVER ADD -ircnet efnet my.irssi-proxy.org 2778 secret
627 <p>Irssi proxy works fine with other IRC clients as well.</p>
629 <p><strong>SOCKS</strong></p>
631 Irssi can be compiled with socks support (<strong>--with-socks</strong>
632 option to configure), but I don't really know how it works, if at all. /SET
633 proxy settings don't have anything to do with socks however.
635 <p><strong>Others</strong></p>
637 <p>IRC bouncers usually work like IRC servers, and want a password. You can
641 /SET proxy_password <password>
644 <p>Irssi's defaults for connect strings are</p>
647 /SET proxy_string CONNECT %s %d
648 /SET proxy_string_after
651 <p>The proxy_string is sent before NICK/USER commands, the
652 proxy_string_after is sent after them. %s and %d can be used with both
655 <h3><a id="c11">11. Irssi's settings</a></h3>
657 <p>You probably don't like Irssi's default settings. I don't like them.
658 But I'm still convinced that they're pretty good defaults. Here's some
659 of them you might want to change (the default value is shown):</p>
661 <p><strong>Queries</strong></p>
664 <dt>/SET autocreate_own_query ON</dt>
665 <dd>Should new query window be created when you send message to someone
668 <dt>/SET autocreate_query_level MSGS</dt>
669 <dd>New query window should be created when receiving messages with
670 this level. MSGS, DCCMSGS and NOTICES levels work currently. You can
671 disable this with /SET -clear autocrate_query_level.</dd>
673 <dt>/SET autoclose_query 0</dt>
674 <dd>Query windows can be automatically closed after certain time of
675 inactivity. Queries with unread messages aren't closed and active
676 window is neither never closed. The value is given in seconds.</dd>
679 <p><strong>Windows</strong></p>
682 <dt>/SET use_msgs_window OFF</dt>
683 <dd>Create messages window at startup. All private messages go to this
684 window. This only makes sense if you've disabled automatic query
685 windows. Message window can also be created manually with /WINDOW LEVEL
686 MSGS, /WINDOW NAME (msgs).</dd>
688 <dt>/SET use_status_window ON</dt>
689 <dd>Create status window at startup. All messages that don't really
690 have better place go here, like all /WHOIS replies etc. Status window
691 can also be created manually with /WINDOW LEVEL ALL -MSGS, /WINDOW NAME
694 <dt>/SET autocreate_windows ON</dt>
695 <dd>Should we create new windows for new window items or just place
696 everything in one window</dd>
698 <dt>/SET autoclose_windows ON</dt>
699 <dd>Should window be automatically closed when the last item in them is
700 removed (ie. /PART, /UNQUERY).</dd>
702 <dt>/SET reuse_unused_windows OFF</dt>
703 <dd>When finding where to place new window item (channel, query) Irssi
704 first tries to use already existing empty windows. If this is set ON,
705 new window will always be created for all window items. This setting is
706 ignored if autoclose_windows is set ON.</dd>
708 <dt>/SET window_auto_change OFF</dt>
709 <dd>Should Irssi automatically change to automatically created windows
710 - usually queries when someone sends you a message. To prevent
711 accidentally sending text meant to some other channel/nick, Irssi
712 clears the input buffer when changing the window. The text is still in
713 scrollback buffer, you can get it back with pressing arrow up key.</dd>
715 <dt>/SET print_active_channel OFF</dt>
716 <dd>When you keep more than one channel in same window, Irssi prints
717 the messages coming to active channel as "<nick> text"
718 and other channels as "<nick:channel> text". If this
719 setting is set ON, the messages to active channels are also printed in
722 <dt>/SET window_history OFF</dt>
723 <dd>Should command history be kept separate for each window.</dd>
727 <p><strong>User information</strong></p>
731 <dd>Your nick name</dd>
733 <dt>/SET alternate_nick</dt>
734 <dd>Your alternate nick.</dd>
736 <dt>/SET user_name</dt>
737 <dd>Your username, if you have ident enabled this doesn't affect
740 <dt>/SET real_name</dt>
741 <dd>Your real name.</dd>
745 <p><strong>Server information</strong></p>
748 <dt>/SET skip_motd OFF</dt>
749 <dd>Should we hide server's MOTD (Message Of The Day).</dd>
751 <dt>/SET server_reconnect_time 300</dt>
752 <dd>Seconds to wait before connecting to same server again. Don't set
753 this too low since it usually doesn't help at all - if the host is
754 down, the few extra minutes of waiting won't hurt much.</dd>
756 <dt>/SET lag_max_before_disconnect 300</dt>
757 <dd>Maximum server lag in seconds before disconnecting and trying to
758 reconnect. This happens mostly only when network breaks between you and
763 <p><strong>Appearance</strong></p>
766 <dt>/SET timestamps ON</dt>
767 <dd>Show timestamps before each message.</dd>
769 <dt>/SET hide_text_style OFF</dt>
770 <dd>Hide all bolds, underlines, MIRC colors, etc.</dd>
772 <dt>/SET show_nickmode ON</dt>
773 <dd>Show the nick's mode before nick in channels, ie. ops have
774 <@nick>, voices <+nick> and others < nick></dd>
776 <dt>/SET show_nickmode_empty ON</dt>
777 <dd>If the nick doesn't have a mode, use one space. ie. ON:
778 < nick>, OFF: <nick></dd>
780 <dt>/SET show_quit_once OFF</dt>
781 <dd>Show quit message only once in some of the channel windows the
782 nick was in instead of in all windows.</dd>
784 <dt>/SET lag_min_show 100</dt>
785 <dd>Show the server lag in status bar if it's bigger than this, the
786 unit is 1/100 of seconds (ie. the default value of 100 = 1 second).</dd>
788 <dt>/SET indent 10</dt>
789 <dd>When lines are longer than screen width they have to be split to
790 multiple lines. This specifies how much space to put at the beginning
791 of the line before the text begins. This can be overridden in text
792 formats with %| format.</dd>
794 <dt>/SET activity_hide_targets</dt>
795 <dd>If you don't want to see window activity in some certain channels
796 or queries, list them here. For example "#boringchannel =bot1 =bot2".
797 If any highlighted text or message for you appears in that window, this
798 setting is ignored and the activity is shown.</dd>
800 <p><strong>Nick completion</strong></p>
803 <dt>/SET completion_auto OFF</dt>
804 <dd>Automatically complete the nick if line begins with start of nick
805 and the completion character. Learn to use the tab-completion instead,
806 it's a lot better ;)</dd>
808 <dt>/SET completion_char :</dt>
809 <dd>Completion character to use.</dd>