Beruflich Dokumente
Kultur Dokumente
SUPPORT
NEWS
DOCUMENTATION
DOWNLOAD
ABOUT
THEMES
SCRIPTS
Startup HOWTO
To new Irssi users (not to new IRC users ..)
Copyright (c) 2000-2002 by Timo Sirainen, release under GNU FDL 1.1 license.
Index with some FAQ questions that are answered in the chapter:
1.
2.
3.
Server
4.
5.
6.
keeps trying to reconnect to it again and again, how can I stop it??
I want to have own status and/or msgs window for each servers
7.
8.
9.
Logging
Changing keyboard bindings
How do I make F1 key do something?
What's this?
You are visiting the official
website for the IRC client
Irssi, for more information
see the about section.
Search this
site
Search function coming
soon!
GO!
What's
new?
Irssi 0.8.16 has been
released!
11.Irssi's settings
12.Statusbar
By default, irssi uses "sticky windowing" for split windows. This means that windows created
inside one split window cannot be moved to another split window without some effort. For
example you could have following window layout:
Split window 1: win#1 - Status window, win#2 - Messages window
Split window 2: win#3 - IRCnet/#channel1, win#4 - IRCnet/#channel2
Split window 3: win#5 - efnet/#channel1, win#6 - efnet/#channel2
When you are in win#1 and press ALT-6, irssi jumps to split window #3 and moves the
efnet/#channel2 the active window.
With non-sticky windowing the windows don't have any relationship with split windows, pressing ALT-6 in win#1
moves win#6 to split window 1 and sets it active, except if win#6 was already visible in some other split window
irssi just changes to that split window. This it the way windows work with ircii, if you prefer it you can set it with
/SET autostick_split_windows OFF
Each window can have multiple channels, queries and other "window items" inside them. If
you don't like windows at all, you disable automatic creating of them with
/SET autocreate_windows OFF
And if you keep all channels in one window, you most probably want the channel name printed
in each line:
/SET print_active_channel ON
If you want to group only some channels or queries in one window, use
/JOIN -window #channel
/QUERY -window nick
3. Server and channel automation
Irssi's multiple IRC network support is IMHO very good - at least compared to other clients :) Even if you're only in
one IRC network you should group all your servers to be in the same IRC network as this helps with reconnecting if
your primary server breaks and is probably useful in some other ways too :) For information how to actually use
irssi correctly with multiple servers see the chapter 6.
First you need to have your IRC network set, use /NETWORK command to see if it's already there. If it isn't,
use/NETWORK ADD yournetwork. If you want to execute some commands automatically when you're connected to
some network, use -autosendcmd option. (NOTE: use /IRCNET with 0.8.9 and older.) Here's some examples:
/NETWORK ADD -autosendcmd '^msg bot invite' IRCnet
/NETWORK ADD -autosendcmd "/^msg nickserv ident pass;wait 2000" OFTC
After that you need to add your servers. For example:
/SERVER ADD -auto -network IRCnet irc.kpnqwest.fi 6667
/SERVER ADD -auto -network worknet irc.mycompany.com 6667 password
The -auto option specifies that this server is automatically connected at startup. You don't
need to make more than one server with -auto option to one IRC network, other servers are
automatically connected in same network if the -auto server fails.
And finally channels:
/CHANNEL ADD -auto -bots *!*bot@host.org -botcmd "/^msg $0 op pass" #irssi
efnet
/CHANNEL ADD -auto #secret IRCnet password
-bots and -botcmd should be the only ones needing a bit of explaining. They're used to send
commands automatically to bot when channel is joined, usually to get ops automatically. You
can specify multiple bot masks with -bots option separated with spaces (and remember to
quote the string then). The $0 in -botcmdspecifies the first found bot in the list. If you don't
need the bot masks (ie. the bot is always with the same nick, like chanserv) you can give only
the -botcmd option and the command is always sent.
4. Setting up windows and automatically restoring them at startup
First connect to all the servers, join the channels and create the queries you want. If you want to move the windows
/RECONNECT recon-1
/RECONNECT ALL
Now that you're connected to all your servers, you'll have to know how to specify which one of
them you want to use. One way is to have an empty window, like status or msgs window. In it,
you can specify which server to set active with
/WINDOW SERVER tag
- set server "tag" active
Ctrl-X
- set the next server in list active
When the server is active, you can use it normally. When there's multiple connected servers,
irssi adds [servertag] prefix to all messages in non-channel/query messages so you'll know
where it came from.
Several commands also accept -servertag option to specify which server it should use:
/MSG -tag nick message
/JOIN -tag #channel
/QUERY -tag nick
/MSG tab completion also automatically adds the -tag option when nick isn't in active server.
Window's server can be made sticky. When sticky, it will never automatically change to anything else, and if server
gets disconnected, the window won't have any active server. When the server gets connected again, it is
automatically set active in the window. To set the window's server sticky use
/WINDOW SERVER -sticky tag
This is useful if you wish to have multiple status or msgs windows, one for each server. Here's
how to do them (repeat for each server)
/WINDOW NEW HIDE
/WINDOW NAME (status)
/WINDOW LEVEL ALL -MSGS
/WINDOW SERVER -sticky network
/WINDOW
/WINDOW
/WINDOW
/WINDOW
NEW HIDE
NAME (msgs)
LEVEL MSGS
SERVER -sticky network
give
HTTP proxy
Use these settings with HTTP proxies:
/SET -clear proxy_password
/EVAL SET proxy_string CONNECT %s:%d HTTP/1.0\n\n
BNC
/SET proxy_password your_pass
/SET -clear proxy_string
/SET proxy_string_after conn %s %d
dircproxy
dircproxy separates the server connections by passwords. So, if you for example have network connection with
password ircpass and OFTC connection with oftcpass, you would do something like this:
/SET -clear proxy_password
/SET -clear proxy_string
/SERVER ADD -auto -network IRCnet fake.network 6667 ircpass
/SERVER ADD -auto -network OFTC fake.oftc 6667 oftcpass
The server name and port you give isn't used anywhere, so you can put anything you want in
there.
psyBNC
psyBNC has internal support for multiple servers. However, it could be a bit annoying to use, and some people just
use different users for connecting to different servers. You can manage this in a bit same way as with dircproxy, by
creating fake connections:
/SET -clear proxy_password
/SET -clear proxy_string
/NETWORK ADD -user networkuser IRCnet
/SERVER ADD -auto -network IRCnet fake.network 6667 ircpass
/NETWORK ADD -user oftcuser OFTC
/SERVER ADD -auto -network OFTC fake.oftc 6667 oftcpass
So, you'll specify the usernames with /NETWORK ADD command, and the user's password
with /SERVER ADD.
(NOTE: use /IRCNET with 0.8.9 and older.)
Irssi proxy
Irssi contains it's own proxy which you can build giving --with-proxy option to configure. You'll still need to run irssi
in a screen to use it though.
Irssi proxy is a bit different than most proxies, normally proxies create a new connection to IRC server when you
connect to it, but irssi proxy shares your existing IRC connection(s) to multiple clients. And even more clearly: You
can use only one IRC server connection to IRC with as many clients as you want. Can anyone figure out even more
easier ways to say this, so I wouldn't need to try to explain this thing for minutes every time? :)
Irssi proxy supports sharing multiple server connections in different ports, like you can share network in port 2777
and efnet in port 2778.
Usage in proxy side:
/LOAD proxy
/SET irssiproxy_password <password>
/SET irssiproxy_ports <network>=<port> ... (eg. IRCnet=2777 efnet=2778)
NOTE: you MUST add all the servers you are using to server and network lists with /SERVER
ADD and /NETWORK ADD. ..Except if you really don't want to for some reason, and you only
use one server connection, you may simply set:
/SET irssiproxy_ports *=2777
Usage in client side:
Just connect to the irssi proxy like it is a normal server with password specified in /SET irssiproxy_password. For
example:
/SERVER ADD -network IRCnet my.irssi-proxy.org 2777 secret
/SERVER ADD -network efnet my.irssi-proxy.org 2778 secret
Irssi proxy works fine with other IRC clients as well.
SOCKS
Irssi can be compiled with socks support (--with-socks option to configure), but I don't really know how it works, if at
all. /SET proxy settings don't have anything to do with socks however.
Others
IRC bouncers usually work like IRC servers, and want a password. You can give it with:
/SET proxy_password <password>
Irssi's defaults for connect strings are
/SET proxy_string CONNECT %s %d
/SET proxy_string_after
The proxy_string is sent before NICK/USER commands, the proxy_string_after is sent after
them. %s and %d can be used with both of them.
11. Irssi's settings
You probably don't like Irssi's default settings. I don't like them. But I'm still convinced that they're pretty good
defaults. Here's some of them you might want to change (the default value is shown):
Queries
/SET autocreate_own_query ON
Should new query window be created when you send message to someone (with /MSG).
/SET autocreate_query_level MSGS
New query window should be created when receiving messages with this level. MSGS, DCCMSGS and
NOTICES levels work currently. You can disable this with /SET -clear autocreate_query_level.
/SET autoclose_query 0
Query windows can be automatically closed after certain time of inactivity. Queries with unread messages
aren't closed and active window is neither never closed. The value is given in seconds.
Windows
/SET use_msgs_window OFF
Create messages window at startup. All private messages go to this window. This only makes sense if you've
disabled automatic query windows. Message window can also be created manually with /WINDOW LEVEL
MSGS, /WINDOW NAME (msgs).
/SET use_status_window ON
Create status window at startup. All messages that don't really have better place go here, like all /WHOIS
replies etc. Status window can also be created manually with /WINDOW LEVEL ALL -MSGS,/WINDOW NAME
(status).
/SET autocreate_windows ON
Should we create new windows for new window items or just place everything in one window
/SET autoclose_windows ON
Should window be automatically closed when the last item in them is removed (ie. /PART, /UNQUERY).
/SET reuse_unused_windows OFF
When finding where to place new window item (channel, query) Irssi first tries to use already existing empty
windows. If this is set ON, new window will always be created for all window items. This setting is ignored if
autoclose_windows is set ON.
/SET window_auto_change OFF
Should Irssi automatically change to automatically created windows - usually queries when someone sends
you a message. To prevent accidentally sending text meant to some other channel/nick, Irssi clears the input
buffer when changing the window. The text is still in scrollback buffer, you can get it back with pressing
arrow up key.
/SET print_active_channel OFF
When you keep more than one channel in same window, Irssi prints the messages coming to active channel
as <nick> text and other channels as <nick:channel> text. If this setting is set ON, the messages to active
channels are also printed in the latter way.
/SET window_history OFF
Should command history be kept separate for each window.
User information
/SET nick
Your nick name
/SET alternate_nick
Your alternate nick.
/SET user_name
Your username, if you have ident enabled this doesn't affect anything
/SET real_name
Your real name.
Server information
/SET skip_motd OFF
Should we hide server's MOTD (Message Of The Day).
/SET server_reconnect_time 300
Seconds to wait before connecting to same server again. Don't set this too low since it usually doesn't help
at all - if the host is down, the few extra minutes of waiting won't hurt much.
/SET lag_max_before_disconnect 300
Maximum server lag in seconds before disconnecting and trying to reconnect. This happens mostly only
when network breaks between you and IRC server.
Appearance
/SET timestamps ON
Show timestamps before each message.
/SET hide_text_style OFF
Hide all bolds, underlines, MIRC colors, etc.
/SET show_nickmode ON
Show the nick's mode before nick in channels, ie. ops have <@nick>, voices <+nick> and others< nick>
/SET show_nickmode_empty ON
If the nick doesn't have a mode, use one space. ie. ON: < nick>, OFF: <nick>
/SET show_quit_once OFF
Show quit message only once in some of the channel windows the nick was in instead of in all windows.
/SET lag_min_show 100
Show the server lag in status bar if it's bigger than this, the unit is 1/100 of seconds (ie. the default value of
100 = 1 second).
/SET indent 10
When lines are longer than screen width they have to be split to multiple lines. This specifies how much
space to put at the beginning of the line before the text begins. This can be overridden in text formats
with %| format.
/SET activity_hide_targets
If you don't want to see window activity in some certain channels or queries, list them here. For
example #boringchannel =bot1 =bot2. If any highlighted text or message for you appears in that window,
this setting is ignored and the activity is shown.
Nick completion
/SET completion_auto OFF
Automatically complete the nick if line begins with start of nick and the completion character. Learn to use
the tab-completion instead, it's a lot better ;)
/SET completion_char :
Completion character to use.
12. Statusbar
/STATUSBAR displays a list of statusbars:
Name
Type
Placement Position Visible
window
window bottom
0
always
window_inact
window bottom
1
inactive
prompt
root
bottom
100
always
topic
root
top
1
always
/STATUSBAR <name> prints the statusbar settings and it's items. /STATUSBAR <name>
ENABLE|DISABLEenables/disables the statusbar. /STATUSBAR <name> RESET resets the
statusbar to it's default settings, or if the statusbar was created by you, it will be removed.
Type can be window or root, meaning if the statusbar should be created for each split window, or just once.
Placement can be top or bottom. Position is a number, the higher the value the lower in screen it is. Visible can be
always, active or inactive. Active/inactive is useful only with split windows, one split window is active and the rest
are inactive. These settings can be changed with:
/STATUSBAR <name> TYPE window|root
/STATUSBAR <name> PLACEMENT top|bottom
/STATUSBAR <name> POSITION <num>
/STATUSBAR <name> VISIBLE always|active|inactive
When loading a new statusbar scripts, you'll need to also specify where you want to show it.
Statusbar items can be modified with:
/STATUSBAR <name> ADD [-before | -after <item>] [-priority #] [-alignment left|
right] <item>
/STATUSBAR <name> REMOVE <item>
The item name with statusbar scripts is usually same as the script's name. Script's
documentation should tell if this isn't the case. So, to add mail.pl before the window activity
item (see the list with /STATUSBAR window), use:/STATUSBAR window ADD -before act mail.