3 <h3>To new Irssi users (not to new IRC users ..)</h3>
5 <p>Copyright (c) 2000-2001 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></li>
13 <li><a href="#c3">Server and channel automation</a>
15 <li>how do I automatically connect to servers at startup?</li>
16 <li>how do I automatically join to channels at startup?</li>
18 <li><a href="#c4">Setting up windows and automatically restoring them
20 <li><a href="#c5">Status and msgs windows & message levels</a>
22 <li>I want /WHOIS to print reply to current window</li>
23 <li>I want all messages to go to one window, not create new windows</li>
25 <li><a href="#c6">How support for multiple servers works in irssi</a>
27 <li>I connected to some server that doesn't respond and now irssi
28 keeps trying to reconnect to it again and again, how can I stop
30 <li>I want to have own status and/or msgs window for each servers</li>
32 <li><a href="#c7">/LASTLOG and jumping around in scrollback</a>
34 <li>How can I save all texts in a window to file?</li>
36 <li><a href="#c8">Logging</a></li>
37 <li><a href="#c9">Proxies and IRC bouncers</a></li>
38 <li><a href="#c10">Irssi's settings</a></li>
41 <h3><a id="c1">1. For all the lazy people</a></h3>
43 <p>These settings should give you pretty good defaults (the ones I use):</p>
45 <p>I don't like automatic query windows, I don't like status window, I do
46 like msgs window where all messages go:</p>
49 /SET autocreate_own_query OFF
50 /SET autocreate_query_level DCCMSGS
51 /SET use_status_window OFF
52 /SET use_msgs_window ON
55 <p>Disable automatic window closing when /PARTing channel or /UNQUERYing
59 /SET autoclose_windows OFF
60 /SET reuse_unused_windows ON
63 <p>And example how to add servers:</p>
65 <p>(openprojects network, identify with nickserv and wait for 2 seconds before
69 /IRCNET ADD -autosendcmd "/^msg nickserv ident pass;wait -opn 2000" opn
72 <p>Then add some servers to different networks (ircnet is already set up
73 for them), irc.kpnqwest.fi is used by default for IRCNet but if it fails,
74 irc.funet.fi is tried next:</p>
77 /SERVER ADD -auto -ircnet ircnet irc.kpnqwest.fi 6667
78 /SERVER ADD -ircnet ircnet irc.funet.fi 6667
79 /SERVER ADD -auto -ircnet efnet efnet.cs.hut.fi 6667
82 <p>Automatically join to channels after connected to server, send op request
83 to bot after joined to efnet/#irssi:</p>
86 /CHANNEL ADD -auto #irssi ircnet
87 /CHANNEL ADD -auto -bots *!*bot@host.org -botcmd "/^msg $0 op pass"
91 If you want lines containing your nick to hilight:
97 <h3><a id="c2">2. Basic user interface usage</a></h3>
99 <p>Windows can be scrolled up/down with PgUp and PgDown keys. If they don't
100 work for you, use Meta-p and Meta-n keys. For jumping to beginning or end of
101 the buffer, use /SB HOME and /SB END commands.</p>
103 <p>By default, irssi uses "hidden windows" for everything. Hidden
104 window is created every time you /JOIN a channel or /QUERY someone.
105 There's several ways you can change between these windows:</p>
108 Meta-1, Meta-2, .. Meta-0 - Jump directly between windows 1-10
109 Meta-q .. Meta-o - Jump directly between windows 11-19
110 /WINDOW <number> - Jump to any window with specified number
111 Ctrl-P, Ctrl-N - Jump to previous / next window
114 <p>Clearly the easiest way is to use Meta-number keys. And what is the Meta
115 key? For some terminals, it's the same as ALT. If you have Windows keyboard,
116 it's probably the left Windows key. If they don't work directly, you'll need
117 to set a few X resources (NOTE: these work with both xterm and rxvt):</p>
120 XTerm*eightBitInput: false
121 XTerm*metaSendsEscape: true
124 <p>With rxvt, you can also specify which key acts as Meta key. So if you
125 want to use ALT instead of Windows key for it, use:</p>
131 <p>You could do this by changing the X key mappings:</p>
134 xmodmap -e "keysym Alt_L = Meta_L Alt_L"
137 <p>And how exactly do you set these X resources? For Debian, there's
138 /etc/X11/Xresources/xterm file where you can put them and it's read
139 automatically when X starts. ~/.Xresources and ~/.Xdefaults files might also
140 work. If you can't get anything else to work, just copy&paste those lines to
141 ~/.Xresources and directly call "xrdb -merge ~/.Xresources" in some xterm.
142 The resources affect only the new xterms you start, not existing ones.</p>
144 <p>Many windows SSH clients also don't allow usage of ALT. One excellent
145 client that does allow is putty, you can download it from
146 <a href="http://www.chiark.greenend.org.uk/~sgtatham/putty/">
147 http://www.chiark.greenend.org.uk/~sgtatham/putty/</a>.</p>
149 <p>Irssi also supports split windows, they've had some problems in past
150 but I think they should work pretty well now :) Here's some commands
154 /WINDOW NEW - Create new split window
155 /WINDOW NEW HIDE - Create new hidden window
156 /WINDOW CLOSE - Close split or hidden window
158 /WINDOW HIDE [<number>|<name>] - Make the split window hidden window
159 /WINDOW SHOW <number>|<name> - Make the hidden window a split window
161 /WINDOW SHRINK [<lines>] - Shrink the split window
162 /WINDOW GROW [<lines>] - Grow the split window
163 /WINDOW BALANCE - Balance the sizes of all split windows
166 <p>By default, irssi uses "sticky windowing" for split windows. This means
167 that windows created inside one split window cannot be moved to another
168 split window without some effort. For example you could have following
172 Split window 1: win#1 - Status window, win#2 - Messages window
173 Split window 2: win#3 - ircnet/#channel1, win#4 - ircnet/#channel2
174 Split window 3: win#5 - efnet/#channel1, win#6 - efnet/#channel2
177 <p>When you are in win#1 and press ALT-6, irssi jumps to split window
178 #3 and moves the efnet/#channel2 the active window.</p>
180 <p>With non-sticky windowing the windows don't have any relationship with
181 split windows, pressing ALT-6 in win#1 moves win#6 to split window 1
182 and sets it active, except if win#6 was already visible in some other
183 split window irssi just changes to that split window. This it the way
184 windows work with ircii, if you prefer it you can set it with</p>
187 /SET autostick_split_windows OFF
190 <p>Each window can have multiple channels, queries and other "window
191 items" inside them. If you don't like windows at all, you disable
192 automatic creating of them with</p>
195 /SET autocreate_windows OFF
198 <p>If you want to group only some channels or queries in one window,
202 /JOIN -window #channel
206 <h3><a id="c3">3. Server and channel automation</a></h3>
208 <p>Irssi's multiple IRC network support is IMHO very good - at least
209 compared to other clients :) Even if you're only in one IRC network you
210 should group all your servers to be in the same IRC network as this
211 helps with reconnecting if your primary server breaks and is probably
212 useful in some other ways too :) For information how to actually use
213 irssi correctly with multiple servers see the chapter 6.</p>
215 <p>First you need to have your IRC network set, use /IRCNET command to
216 see if it's already there. If it isn't, use /IRCNET ADD yourircnet. To
217 make Irssi work properly with different IRC networks, you might need to
218 give some special settings to /IRCNET ADD, see manual.txt for more
219 information about them. Irssi defaults to IRCNet's behaviour.</p>
221 <p>After that you need to add your servers. For example:</p>
224 /SERVER ADD -auto -ircnet ircnet irc.kpnqwest.fi 6667
225 /SERVER ADD -auto -ircnet worknet irc.mycompany.com 6667 password
228 <p>The -auto option specifies that this server is automatically connected
229 at startup. You don't need to make more than one server with -auto
230 option to one IRC network, other servers are automatically connected in
231 same network if the -auto server fails.</p>
233 <p>And finally channels:</p>
236 /CHANNEL ADD -auto -bots *!*bot@host.org -botcmd "/^msg $0 op pass"
238 /CHANNEL ADD -auto #secret ircnet password
241 <p>-bots and -botcmd should be the only ones needing a bit of
242 explaining. They're used to send commands automatically to bot when
243 channel is joined, usually to get ops automatically. You can specify
244 multiple bot masks with -bots option separated with spaces (and
245 remember to quote the string then). The $0 in -botcmd specifies the
246 first found bot in the list. If you don't need the bot masks (ie. the
247 bot is always with the same nick, like chanserv) you can give only the
248 -botcmd option and the command is always sent.</p>
251 <h3><a id="c4">4. Setting up windows and automatically restoring them at startup</a></h3>
253 <p>First connect to all the servers, join the channels and create the
254 queries you want. If you want to move the windows or channels around
258 /WINDOW MOVE LEFT/RIGHT/number - move window elsewhere
259 /WINDOW ITEM MOVE <number>|<name> - move channel/query to another window
262 <p>When everything looks the way you like, use /LAYOUT SAVE command
263 (and /SAVE, if you don't have autosaving enabled) and when you start
264 irssi next time, irssi remembers the positions of the channels, queries
265 and everything. This "remembering" doesn't mean that simply using
266 /LAYOUT SAVE would automatically make irssi reconnect to all servers
267 and join all channels, you'll need the /SERVER ADD -auto and /CHANNEL
268 ADD -auto commands to do that.</p>
270 <p>If you want to change the layout, you just rearrange the layout like
271 you want it and use /LAYOUT SAVE again. If you want to remove the
272 layout for some reason, use /LAYOUT RESET.</p>
275 <h3><a id="c5">5. Status and msgs windows & message levels</a></h3>
277 <p>By default, all the "extra messages" go to status window. This means
278 pretty much all messages that don't clearly belong to some channel or
279 query. Some people like it, some don't. If you want to remove it, use</p>
282 /SET use_status_window OFF
285 <p>This doesn't have any effect until you restart irssi. If you want to
286 remove it immediately, just /WINDOW CLOSE it.</p>
288 <p>Another common window is "messages window", where all private
289 messages go. By default it's disabled and query windows are created
290 instead. To make all private messages go to msgs window, say:</p>
293 /SET use_msgs_window ON
294 /SET autocreate_query_level DCCMSGS (or if you don't want queries to
295 dcc chats either, say NONE)
298 <p>use_msgs_window either doesn't have any effect until restarting
299 irssi. To create it immediately say:</p>
302 /WINDOW NEW HIDE - create the window
303 /WINDOW NAME (msgs) - name it to "(msgs)"
304 /WINDOW LEVEL MSGS - make all private messages go to this window
305 /WINDOW MOVE 1 - move it to first window
308 <p>Note that neither use_msgs_window nor use_status_window have any
309 effect at all if /LAYOUT SAVE has been used.</p>
311 <p>This brings us to message levels.. What are they? All messages that
312 irssi prints have one or more "message levels". Most common are PUBLIC
313 for public messages in channels, MSGS for private messages and CRAP for
314 all sorts of messages with no real classification. You can get a whole
315 list of levels with</p>
321 <p>Status window has message level "ALL -MSGS", meaning that all messages,
322 except private messages, without more specific place go to status
323 window. The -MSGS is there so it doesn't conflict with messages
327 <h3><a id="c6">6. How support for multiple servers works in irssi</a></h3>
329 <p>ircii and several other clients support multiple servers by placing
330 the connection into some window. IRSSI DOES NOT. There is no required
331 relationship between window and server. You can connect to 10 servers
332 and manage them all in just one window, or join channel in each one of
333 them to one sigle window if you really want to. That being said, here's
334 how you do connect to new server without closing the old connection:</p>
337 /CONNECT irc.server.org
340 <p>Instead of the /SERVER which disconnects the existing connection. To
341 see list of all active connections, use /SERVER without any parameters.
342 You should see a list of something like:</p>
345 -!- IRCNet: irc.telia.fi:6667 (IRCNet)
346 -!- OPN: tolkien.openprojects.net:6667 (OPN)
347 -!- RECON-1: 192.168.0.1:6667 () (02:59 left before reconnecting)
350 <p>Here you see that we're connected to IRCNet and OPN networks. The
351 the IRCNet at the beginning is called the "server tag" while the
352 (IRCnet) at the end shows the IRC network. Server tag specifies unique
353 tag to refer to the server, usually it's the same as the IRC network.
354 When the IRC network isn't known it's some part of the server name.
355 When there's multiple connections to same IRC network or server, irssi
356 adds a number after the tag so there could be ircnet, ircnet2, ircnet3
359 <p>Server tags beginning with RECON- mean server reconnections. Above we
360 see that connection to server at 192.168.0.1 wasn't successful and
361 irssi will try to connect it again in 3 minutes.</p>
363 <p>To disconnect one of the servers, or to stop irssi from
364 reconnecting, use</p>
367 /DISCONNECT ircnet - disconnect server with tag "ircnet"
368 /DISCONNECT recon-1 - stop trying to reconnect to RECON-1 server
369 /RMRECONNS - stop all server reconnections
371 /RECONNECT recon-1 - immediately try reconnecting back to RECON-1
372 /RECONNECT ALL - immediately try reconnecting back to all
373 servers in reconnection queue
376 <p>Now that you're connected to all your servers, you'll have to know how
377 to specify which one of them you want to use. One way is to have an
378 empty window, like status or msgs window. In it, you can specify which
379 server to set active with</p>
382 /WINDOW SERVER tag - set server "tag" active
383 Ctrl-X - set the next server in list active
386 <p>When the server is active, you can use it normally. When there's
387 multiple connected servers, irssi adds [servertag] prefix to all
388 messages in non-channel/query messages so you'll know where it came
391 <p>Several commands also accept -servertag option to specify which server
395 /MSG -tag nick message
400 <p>/MSG tab completion also automatically adds the -tag option when
401 nick isn't in active server.</p>
403 <p>Window's server can be made sticky. When sticky, it will never
404 automatically change to anything else, and if server gets disconnected, the
405 window won't have any active server. When the server gets connected again,
406 it is automatically set active in the window. To set the window's server
410 /WINDOW SERVER -sticky tag
413 <p>This is useful if you wish to have multiple status or msgs windows, one
414 for each server. Here's how to do them (repeat for each server)</p>
418 /WINDOW NAME (status)
419 /WINDOW LEVEL ALL -MSGS
420 /WINDOW SERVER -sticky ircnet
425 /WINDOW SERVER -sticky ircnet
428 <h3><a id="c7">7. /LASTLOG and jumping around in scrollback</a></h3>
430 <p>/LASTLOG command can be used for searching texts in scrollback
431 buffer. Simplest usages are</p>
434 /LASTLOG word - print all lines with "word" in them
435 /LASTLOG word 10 - print last 10 occurances of "word"
436 /LASTLOG -topics - print all topic changes
439 <p>If there's more lines to be printed than 1000, irssi doesn't thinks
440 that you probably made some mistake and won't print them without -force
441 option. If you want to save the full lastlog to file, use</p>
444 /LASTLOG -file ~/irc.log
447 <p>With -file option you don't need -force even if there's more than 1000
448 lines. /LASTLOG has a lot of other options too, see /HELP lastlog for
451 <p>Once you've found the lines you were interested in, you might want
452 to check the discussion around them. Irssi has /SCROLLBACK (or alias
453 /SB) command for jumping around in scrollback buffer. Since /LASTLOG
454 prints the timestamp when the message was originally printed, you can
455 use /SB GOTO hh:mm to jump directly there. To get back to the bottom of
456 scrollback, use /SB END command.</p>
459 <h3><a id="c8">8. Logging</a></h3>
461 <p>Irssi can automatically log important messages when you're set away
462 (/AWAY reason). When you set yourself unaway (/AWAY), the new messages
463 in away log are printed to screen. You can configure it with:</p>
466 /SET awaylog_level MSGS HILIGHT - Specifies what messages to log
467 /SET awaylog_file ~/.irssi/away.log - Specifies the file to use
470 <p>Easiest way to start logging with Irssi is to use autologging. With it
471 Irssi logs all channels and private messages to specified directory.
472 You can turn it on with</p>
478 <p>By default it logs pretty much everything execept CTCPS or CRAP
479 (/WHOIS requests, etc). You can specify the logging level yourself with</p>
482 /SET autolog_level ALL -CRAP -CLIENTCRAP -CTCPS (this is the default)
485 <p>By default irssi logs to ~/irclogs/<servertag>/<target>.log.
486 You can change this with</p>
489 /SET autolog_path ~/irclogs/$tag/$0.log (this is the default)
492 <p>The path is automatically created if it doesn't exist. $0 specifies
493 the target (channel/nick). You can make irssi automatically rotate the
494 logs by adding date/time formats to the file name. The formats are in
495 "man strftime" format. For example</p>
498 /SET autolog_path ~/irclogs/%Y/$tag/$0.%m-%d.log
501 <p>For logging only some specific channels or nicks, see /HELP log</p>
504 <h3><a id="c9">9. Proxies and IRC bouncers</a></h3>
506 <p>Irssi supports connecting to IRC servers via a proxy. All proxies have
507 these settings in common:</p>
511 /SET proxy_address <Proxy host address>
512 /SET proxy_port <Proxy port>
515 <p><strong>HTTP proxy</strong></p>
517 <p>Use these settings with HTTP proxies:</p>
520 /SET -clear proxy_password
521 /EVAL SET proxy_string CONNECT %s:%d\n\n
524 <p><strong>Irssi proxy</strong></p>
526 <p>Irssi contains it's own proxy which you can build giving
527 <strong>--with-proxy</strong> option to configure. You'll still need to run
528 irssi in a screen to use it though.</p>
530 <p>Irssi proxy is a bit different than most proxies, normally proxies create
531 a new connection to IRC server when you connect to it, but with irssi proxy
532 all the clients use the same IRC server connection (a bit like how screen -x
535 <p>Irssi proxy supports sharing multiple server connections in different
536 ports, like you can share ircnet in port 2777 and efnet in port 2778.</p>
538 <p>Usage in proxy side:</p>
541 /LOAD irc_proxy (/LOAD proxy in irssi 0.7.98.3 and older)
542 /SET irssiproxy_password <password>
543 /SET irssiproxy_ports <ircnet>=<port> ... (eg. ircnet=2777 efnet=2778)
546 <p><strong>NOTE</strong>: you <strong>MUST</strong> add all the servers you
547 are using to server and ircnet lists with /SERVER ADD and /IRCNET ADD.
548 ..Except if you really don't want to for some reason, and you only use
549 one server connection, you may simply set:</p>
552 /SET irssiproxy_ports *=2777 (irssi 0.7.99 and later only)
555 <p>Usage in client side:</p>
557 <p>Just connect to the irssi proxy like it is a normal server with password
558 specified in /SET irssiproxy_password. For example:</p>
561 /SERVER ADD -ircnet ircnet my.irssi-proxy.org 2777 secret
562 /SERVER ADD -ircnet efnet my.irssi-proxy.org 2778 secret
565 <p>Irssi proxy works fine with other IRC clients as well.</p>
567 <p><strong>SOCKS</strong></p>
569 Irssi can be compiled with socks support (<strong>--with-socks</strong>
570 option to configure), but I don't really know how it works, if at all. /SET
571 proxy settings don't have anything to do with socks however.
573 <p><strong>Others</strong></p>
575 <p>IRC bouncers usually work like IRC servers, and want a password. You can
579 /SET proxy_password <password>
582 <p>Irssi's default for connect string is</p>
585 /SET proxy_string CONNECT %s %d
588 <p>which you can modify according to your bouncer's needs.</p>
590 <h3><a id="c10">10. Irssi's settings</a></h3>
592 <p>You probably don't like Irssi's default settings. I don't like them.
593 But I'm still convinced that they're pretty good defaults. Here's some
594 of them you might want to change (the default value is shown):</p>
596 <p><strong>Queries</strong></p>
599 <dt>/SET autocreate_own_query ON</dt>
600 <dd>Should new query window be created when you send message to someone
603 <dt>/SET autocreate_query_level MSGS</dt>
604 <dd>New query window should be created when receiving messages with
605 this level. MSGS, DCCMSGS and NOTICES levels work currently. You can
606 disable this with /SET -clear autocrate_query_level.</dd>
608 <dt>/SET autoclose_query 0</dt>
609 <dd>Query windows can be automatically closed after certain time of
610 inactivity. Queries with unread messages aren't closed and active
611 window is neither never closed. The value is given in seconds.</dd>
614 <p><strong>Windows</strong></p>
617 <dt>/SET use_msgs_window OFF</dt>
618 <dd>Create messages window at startup. All private messages go to this
619 window. This only makes sense if you've disabled automatic query
620 windows. Message window can also be created manually with /WINDOW LEVEL
621 MSGS, /WINDOW NAME (msgs).</dd>
623 <dt>/SET use_status_window ON</dt>
624 <dd>Create status window at startup. All messages that don't really
625 have better place go here, like all /WHOIS replies etc. Status window
626 can also be created manually with /WINDOW LEVEL ALL -MSGS, /WINDOW NAME
629 <dt>/SET autocreate_windows ON</dt>
630 <dd>Should we create new windows for new window items or just place
631 everything in one window</dd>
633 <dt>/SET autoclose_windows ON</dt>
634 <dd>Should window be automatically closed when the last item in them is
635 removed (ie. /PART, /UNQUERY).</dd>
637 <dt>/SET reuse_unused_windows OFF</dt>
638 <dd>When finding where to place new window item (channel, query) Irssi
639 first tries to use already existing empty windows. If this is set ON,
640 new window will always be created for all window items. This setting is
641 ignored if autoclose_windows is set ON.</dd>
643 <dt>/SET window_auto_change OFF</dt>
644 <dd>Should Irssi automatically change to automatically created windows
645 - usually queries when someone sends you a message. To prevent
646 accidentally sending text meant to some other channel/nick, Irssi
647 clears the input buffer when changing the window. The text is still in
648 scrollback buffer, you can get it back with pressing arrow up key.</dd>
650 <dt>/SET print_active_channel OFF</dt>
651 <dd>When you keep more than one channel in same window, Irssi prints
652 the messages coming to active channel as "<nick> text"
653 and other channels as "<nick:channel> text". If this
654 setting is set ON, the messages to active channels are also printed in
657 <dt>/SET window_history OFF</dt>
658 <dd>Should command history be kept separate for each window.</dd>
662 <p><strong>User information</strong></p>
666 <dd>Your nick name</dd>
668 <dt>/SET alternate_nick</dt>
669 <dd>Your alternate nick.</dd>
671 <dt>/SET user_name</dt>
672 <dd>Your username, if you have ident enabled this doesn't affect
675 <dt>/SET real_name</dt>
676 <dd>Your real name.</dd>
680 <p><strong>Server information</strong></p>
683 <dt>/SET skip_motd OFF</dt>
684 <dd>Should we hide server's MOTD (Message Of The Day).</dd>
686 <dt>/SET server_reconnect_time 300</dt>
687 <dd>Seconds to wait before connecting to same server again. Don't set
688 this too low since it usually doesn't help at all - if the host is
689 down, the few extra minutes of waiting won't hurt much.</dd>
691 <dt>/SET lag_max_before_disconnect 300</dt>
692 <dd>Maximum server lag in seconds before disconnecting and trying to
693 reconnect. This happens mostly only when network breaks between you and
698 <p><strong>Appearance</strong></p>
701 <dt>/SET timestamps ON</dt>
702 <dd>Show timestamps before each message.</dd>
704 <dt>/SET hide_text_style OFF</dt>
705 <dd>Hide all bolds, underlines, MIRC colors, etc.</dd>
707 <dt>/SET show_nickmode ON</dt>
708 <dd>Show the nick's mode before nick in channels, ie. ops have
709 <@nick>, voices <+nick> and others < nick></dd>
711 <dt>/SET show_nickmode_empty ON</dt>
712 <dd>If the nick doesn't have a mode, use one space. ie. ON:
713 < nick>, OFF: <nick></dd>
715 <dt>/SET show_quit_once OFF</dt>
716 <dd>Show quit message only once in some of the channel windows the
717 nick was in instead of in all windows.</dd>
719 <dt>/SET topicbar ON</dt>
720 <dd>Show the channel's topic in top of screen.</dd>
722 <dt>/SET lag_min_show 100</dt>
723 <dd>Show the server lag in status bar if it's bigger than this, the
724 unit is 1/100 of seconds (ie. the default value of 100 = 1 second).</dd>
726 <dt>/SET indent 10</dt>
727 <dd>When lines are longer than screen width they have to be split to
728 multiple lines. This specifies how much space to put at the beginning
729 of the line before the text begins. This can be overridden in text
730 formats with %| format.</dd>
732 <dt>/SET activity_hide_targets</dt>
733 <dd>If you don't want to see window activity in some certain channels
734 or queries, list them here. For example "#boringchannel =bot1 =bot2".
735 If any highlighted text or message for you appears in that window, this
736 setting is ignored and the activity is shown.</dd>
738 <dt>/SET mail_counter ON</dt>
739 <dd>Show the number of mails in your mbox in status
740 bar. The mbox file is taken from $MAIL environment setting. Only mbox
741 format works for now.</dd>
744 <p><strong>Nick completion</strong></p>
747 <dt>/SET completion_auto OFF</dt>
748 <dd>Automatically complete the nick if line begins with start of nick
749 and the completion character. Learn to use the tab-completion instead,
750 it's a lot better ;)</dd>
752 <dt>/SET completion_char :</dt>
753 <dd>Completion character to use.</dd>