1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
|
<h2>FAQ</h2>
<h3>Q: Why doesn't irssi display colors even when ircii etc. displays them?</h3>
<p>A: They force ANSI colors even if terminal doesn't support them. By
default, irssi uses colors only if terminfo/termcap so says. The correct
way to fix this would be to change your TERM environment to a value where
colors work, like xterm-color or color_xterm (eg. <code>TERM=xterm-color
irssi</code>). If this doesn't help, then use the evil way of <code>/SET
term_force_colors ON</code>.</p>
<h3>Q: How do I easily write text to channel that starts with '/' character?</h3>
<p>A: <code>/ /text</code></p>
<h3>Q: Why doesn't irssi update my realname (or whatever) after I change it
with <code>/SET realname</code> and reconnect with <code>/RECONNECT</code>
or <code>/SERVER</code>?</h3>
<p>A: Irssi is trying to be too smart. This will be fixed in future, but for
now you should use <code>/DISCONNECT</code> and <code>/CONNECT</code>.</p>
<h3>Q: I connected to some server which isn't responding but now irssi tries
to connect back to it all the time! How can I stop it?</h3>
<p>A: Two ways. The "good way" to do it is with <code>/DISCONNECT</code>.
Check the server tags first with <code>/SERVER</code> without giving it any
parameters, reconnections are those that have tag starting with "recon"
text. So most probably you're going to do <code>/DISCONNECT recon-1</code>.
The other way is to remove all the reconnections with
<code>/RMRECONNS</code>, easier but may remove some connections you actually
wanted to reconnect (if you used multiple servers..).</p>
<h3>Q: How do I add seconds to timestamp?</h3>
<p>A: <code>/FORMAT timestamp {timestamp %%H:%%M:%%S}</code> - and remember
to add the trailing space :)</p>
<h3>Q: Why does irssi say "Irssi: Channel not fully synchronized yet, try
again after a while" when I try to use /BAN etc?</h3>
<p>A: Possibly a bug in irssi, or ircd you're using does something that
irssi didn't really notice. The new code should make this happen far less
often than before, but one known reason for this is when irssi doesn't
notice that you were unable to join some channel. Currently however I don't
know of any such events irssi doesn't know about.</p>
<p>Anyway, if this does happen, do <code>/RAWLOG SAVE ~/rawlog</code> soon
after joining to channel, and either try to figure out yourself why irssi
didn't get reply to WHO request, or send the whole log to cras@irssi.org. Note
that the rawlog is by default only 200 lines and it may not be enough to
show all needed information, so you might want to do <code>/SET rawlog_lines
1000</code> or so.</p>
<p><code>MODE +b</code> still works fine though.</p>
<h3>Q: Where's the GUI version?</h3>
<p>A: Read
<a href="http://irssi.org/?page=about">http://irssi.org/?page=about</a></p>
<h3>Q: How do I autorejoin channels after being kicked?</h3>
<p>A: That's evil and you shouldn't do it. If you get kicked, you should stay
out, at least until the channel forgot you existed :) Most channels I've
joined just ban you if you autorejoin after kick. If you're joined to
channels who kick people for fun, try changing channels or something.</p>
<p>Anyway, if you REALLY want to do that, and you understand that you're doing
evilness, you can use the autorejoin.pl script that comes with irssi. You'll
still need to specify the channels you wish to rejoin with <code>/SET
autorejoin_channels #chan1 #chan2 ...</code></p>
<h3>Q: How do I announce that I'm away/back in all channels I've joined? Or
how do I change my nick when setting myself away/back?</h3>
<p>A: That's even worse than autorejoin. Who could possibly care every time
you come and go? Many channels will kick you for using this, and I for example
have added several ignores so I'd never need to see these messages. Learn to
use <code>/AWAY</code> command properly and tell it's existence to people
who don't know about it. <code>/WII yournick</code> shows your away reason
much better for people who actually want to know if you're there or not.</p>
<p>You can script these behaviours if you really wish to of course. But
currently there's no public scripts for either of these, and the only way
I'm going to add such to irssi.org is if the script contains a setting to
specify which specific channels the announcement is sent.</p>
<h3>Q: Why does irssi autojoin on invite by default?</h3>
<p>A: The setting is /SET join_auto_chans_on_invite - it's not the same
as regular autojoin-on-invite, which irssi doesn't even have. The only
channels that are joined on invite, are the ones you've added to config
with /CHANNEL ADD -auto. This is very useful with +i channels when you
need to first send an invite request to bot, or if you get accidentally
kicked from channel, the kicker can invite you back immediately.</p>
<p>I don't see any bad side effects with this feature, so it's ON by
default. I guess someone could start kicking/inviting you all the time
but server connection shouldn't drop because of that, and you shouldn't
join channels whose operators are that evil.</p>
<h3>Q: How to make UTF-8 support work with irssi?</h3>
<p>A: xterm -u8, screen -U, /SET term_type utf-8</p>
<h3>Q: Will there be /DETACH-like feature?</h3>
<p>A: Maybe. Detach code already is there, attach is just missing :) But I
don't have much interest in coding it, and
<a href="http://www.gnu.org/software/screen/screen.html">screen</a> works
just fine so why bother?</p>
<h3>Q: How do I run scripts automatically at startup?</h3>
<p>A: Put them into <code>~/.irssi/scripts/autorun/</code> directory. Or
better would be if you placed them in <code>~/.irssi/scripts/</code> and
created symlinks to autorun directory (eg. <code>cd
~/.irssi/scripts/autorun/ ; ln -s ../script.pl .</code>)</p>
<h3>Q: How do I easily edit existing topic?</h3>
<p>A: /TOPIC <tab></p>
<h3>Q: How can I have /WHOIS replies to active window?</h3>
<p>A: Currently there's no other way than to close the status window, or at
least do <code>/WINDOW LEVEL -CRAP</code> in it, but that would make a lot
other messages show up in active window too. I don't have many good ideas
how this could be easily fixed inside irssi (no, kludging it to only work
with whois isn't a "fix") - it'd be possible to create a script do this
though but currently it doesn't exist.</p>
<h3>Q: How do i add the active network to the statusbar</h3>
<p>A: Modify the window-line in statusbar section in config file to
<code>window = "{sb $winref:$tag/$T{sbmode $M}}";</code></p>
|
