source: doc/user-guide/commands.xml @ db2cef1

Last change on this file since db2cef1 was db2cef1, checked in by Wilmer van der Gaast <wilmer@…>, at 2010-07-13T00:09:40Z

Document this complex new beast.
  • Property mode set to 100644
File size: 54.3 KB
Line 
1<chapter id="commands">
2        <title>Bitlbee commands</title>
3
4        <command-list/>
5
6        <bitlbee-command name="account">
7                <short-description>IM-account list maintenance</short-description>
8                <syntax>account [&lt;account id&gt;] &lt;action&gt; [&lt;arguments&gt;]</syntax>
9
10                <description>
11
12                        <para>
13                                Available actions: add, del, list, on, off and set. See <emphasis>help account &lt;action&gt;</emphasis> for more information.
14                        </para>
15
16                </description>
17
18                <bitlbee-command name="add">
19                        <syntax>account add &lt;protocol&gt; &lt;username&gt; &lt;password&gt;</syntax>
20
21                        <description>
22                                <para>
23                                        Adds an account on the given server with the specified protocol, username and password to the account list. Supported protocols right now are: Jabber, MSN, OSCAR (AIM/ICQ), Yahoo and Twitter. For more information about adding an account, see <emphasis>help account add &lt;protocol&gt;</emphasis>.
24                                </para>
25                        </description>
26                       
27                        <bitlbee-command name="jabber">
28                                <syntax>account add jabber &lt;handle@server.tld&gt; &lt;password&gt;</syntax>
29
30                                <description>
31                                        <para>
32                                                The handle should be a full handle, including the domain name. You can specify a servername if necessary. Normally BitlBee doesn't need this though, since it's able to find out the server by doing DNS SRV lookups.
33                                        </para>
34
35                                        <para>
36                                                In previous versions it was also possible to specify port numbers and/or SSL in the server tag. This is deprecated and should now be done using the <emphasis>account set</emphasis> command. This also applies to specifying a resource in the handle (like <emphasis>wilmer@bitlbee.org/work</emphasis>).
37                                        </para>
38                                </description>
39                        </bitlbee-command>
40
41                        <bitlbee-command name="msn">
42                                <syntax>account add msn &lt;handle@server.tld&gt; &lt;password&gt;</syntax>
43
44                                <description>
45                                        <para>
46                                                For MSN connections there are no special arguments.
47                                        </para>
48                                </description>
49                        </bitlbee-command>
50                       
51                        <bitlbee-command name="oscar">
52                                <syntax>account add oscar &lt;handle&gt; &lt;password&gt;</syntax>
53
54                                <description>
55                                        <para>
56                                                OSCAR is the protocol used to connect to AIM and/or ICQ. The servers will automatically detect if you're using a numeric or non-numeric username so there's no need to tell which network you want to connect to.
57                                        </para>
58                                </description>
59
60                                <ircexample>
61                                        <ircline nick="wilmer">account add oscar 72696705 hobbelmeeuw</ircline>
62                                        <ircline nick="root">Account successfully added</ircline>
63                                </ircexample>
64                        </bitlbee-command>
65                       
66                        <bitlbee-command name="twitter">
67                                <syntax>account add twitter &lt;handle&gt; &lt;password&gt;</syntax>
68
69                                <description>
70                                        <para>
71                                                This module gives you simple access to Twitter. Although it uses the Twitter API, only Twitter itself is supported at the moment.
72                                        </para>
73                                       
74                                        <para>
75                                                By default all your Twitter contacts will come from a contact called twitter_(yourusername). You can change this behaviour using the <emphasis>mode</emphasis> setting (see <emphasis>help set mode</emphasis>).
76                                        </para>
77                                       
78                                        <para>
79                                                To send tweets yourself, send them to the twitter_(yourusername) contact, or just write in the groupchat channel if you enabled that option.
80                                        </para>
81
82                                        <para>
83                                                Since Twitter now requires OAuth authentication, you should not enter your Twitter password into BitlBee. Just type a bogus password. The first time you log in, BitlBee will start OAuth authentication. (See <emphasis>help set oauth</emphasis>.)
84                                        </para>
85                                </description>
86                        </bitlbee-command>
87
88                        <bitlbee-command name="yahoo">
89                                <syntax>account add yahoo &lt;handle&gt; &lt;password&gt;</syntax>
90
91                                <description>
92                                        <para>
93                                                For Yahoo! connections there are no special arguments.
94                                        </para>
95                                </description>
96                        </bitlbee-command>
97
98                </bitlbee-command>
99
100                <bitlbee-command name="del">
101                        <syntax>account &lt;account id&gt; del</syntax>
102
103                        <description>
104                                <para>
105                                        This commands deletes an account from your account list. You should signoff the account before deleting it.
106                                </para>
107
108
109                                <para>
110                                        The account ID can be a number (see <emphasis>account list</emphasis>), the protocol name or (part of) the screenname, as long as it matches only one connection.
111                                </para>
112                        </description>
113                </bitlbee-command>
114
115                <bitlbee-command name="on">
116                        <syntax>account [&lt;account id&gt;] on</syntax>
117
118                        <description>
119                                <para>
120                                        This command will try to log into the specified account. If no account is specified, BitlBee will log into all the accounts that have the auto_connect flag set.
121                                </para>
122
123                                <para>
124                                        The account ID can be a number (see <emphasis>account list</emphasis>), the protocol name or (part of) the screenname, as long as it matches only one connection.
125                                </para>
126                        </description>
127
128                </bitlbee-command>
129
130                <bitlbee-command name="off">
131                        <syntax>account [&lt;account id&gt;] off</syntax>
132
133                        <description>
134                                <para>
135                                        This command disconnects the connection for the specified account. If no account is specified, BitlBee will deactivate all active accounts and cancel all pending reconnects.
136                                </para>
137
138                                <para>
139                                        The account ID can be a number (see <emphasis>account list</emphasis>), the protocol name or (part of) the screenname, as long as it matches only one connection.
140                                </para>
141                        </description>
142                </bitlbee-command>
143
144                <bitlbee-command name="list">
145                        <syntax>account list</syntax>
146
147                        <description>
148                                <para>
149                                        This command gives you a list of all the accounts known by BitlBee.
150                                </para>
151                        </description>
152                </bitlbee-command>
153
154                <bitlbee-command name="set">
155                        <syntax>account &lt;account id&gt; set</syntax>
156                        <syntax>account &lt;account id&gt; set &lt;setting&gt;</syntax>
157                        <syntax>account &lt;account id&gt; set &lt;setting&gt; &lt;value&gt;</syntax>
158                        <syntax>account &lt;account id&gt; set -del &lt;setting&gt;</syntax>
159
160                        <description>
161                                <para>
162                                        This command can be used to change various settings for IM accounts. For all protocols, this command can be used to change the handle or the password BitlBee uses to log in and if it should be logged in automatically. Some protocols have additional settings. You can see the settings available for a connection by typing <emphasis>account &lt;account id&gt; set</emphasis>.
163                                </para>
164                               
165                                <para>
166                                        For more infomation about a setting, see <emphasis>help set &lt;setting&gt;</emphasis>.
167                                </para>
168                               
169                                <para>
170                                        The account ID can be a number (see <emphasis>account list</emphasis>), the protocol name or (part of) the screenname, as long as it matches only one connection.
171                                </para>
172                        </description>
173                </bitlbee-command>
174        </bitlbee-command>
175
176        <bitlbee-command name="channel">
177                <short-description>Channel list maintenance</short-description>
178                <syntax>channel [&lt;account id&gt;] &lt;action&gt; [&lt;arguments&gt;]</syntax>
179
180                <description>
181                        <para>
182                                Available actions: del, list, set. See <emphasis>help chat &lt;action&gt;</emphasis> for more information.
183                        </para>
184                       
185                        <para>
186                                There is no <emphasis>channel add</emphasis> command. To create a new channel, just use the IRC <emphasis>/join</emphasis> command. See also <emphasis>help channels</emphasis> and <emphasis>help groupchats</emphasis>.
187                        </para>
188                </description>
189
190                <bitlbee-command name="del">
191                        <syntax>channel &lt;channel id&gt; del</syntax>
192
193                        <description>
194                                <para>
195                                        Remove a channel and forget all its settings. You can only remove channels you're not currently in, and can't remove the main control channel. (You can, however, leave it.)
196                                </para>
197                        </description>
198
199                </bitlbee-command>
200
201                <bitlbee-command name="list">
202                        <syntax>channel list</syntax>
203
204                        <description>
205                                <para>
206                                        This command gives you a list of all the channels you configured.
207                                </para>
208                        </description>
209
210                </bitlbee-command>
211
212                <bitlbee-command name="set">
213                        <syntax>channel &lt;channel id&gt; set</syntax>
214                        <syntax>channel &lt;channel id&gt; set &lt;setting&gt;</syntax>
215                        <syntax>channel &lt;channel id&gt; set &lt;setting&gt; &lt;value&gt;</syntax>
216                        <syntax>channel &lt;channel id&gt; set -del &lt;setting&gt;</syntax>
217
218                        <description>
219                                <para>
220                                        This command can be used to change various settings for channels. Different channel types support different settings. You can see the settings available for a channel by typing <emphasis>channel &lt;channel id&gt; set</emphasis>.
221                                </para>
222                               
223                                <para>
224                                        For more infomation about a setting, see <emphasis>help set &lt;setting&gt;</emphasis>.
225                                </para>
226                               
227                                <para>
228                                        The channel ID can be a number (see <emphasis>channel list</emphasis>), or (part of) its name, as long as it matches only one channel.
229                                </para>
230                        </description>
231                </bitlbee-command>
232
233        </bitlbee-command>
234
235        <bitlbee-command name="chat">
236                <short-description>Chatroom list maintenance</short-description>
237                <syntax>chat &lt;action&gt; [&lt;arguments&gt;]</syntax>
238
239                <description>
240
241                        <para>
242                                Available actions: add, with. See <emphasis>help chat &lt;action&gt;</emphasis> for more information.
243                        </para>
244
245                </description>
246
247                <bitlbee-command name="add">
248                        <syntax>chat add &lt;account&gt; &lt;room&gt; [&lt;channel&gt;]</syntax>
249
250                        <description>
251                                <para>
252                                        Add a chatroom to the list of chatrooms you're interested in. BitlBee needs this list to map room names to a proper IRC channel name.
253                                </para>
254
255                                <para>
256                                        After adding a room to your list, you can simply use the IRC /join command to enter the room. Also, you can tell BitlBee to automatically join the room when you log in. (See <emphasis>chat set</emphasis>)
257                                </para>
258
259                                <para>
260                                        Password-protected rooms work exactly like on IRC, by passing the password as an extra argument to /join.
261                                </para>
262                        </description>
263
264                </bitlbee-command>
265
266                <bitlbee-command name="with">
267                        <syntax>chat with &lt;nickname&gt;</syntax>
268
269                        <description>
270                                <para>
271                                        While most <emphasis>chat</emphasis> subcommands are about named chatrooms, this command can be used to open an unnamed groupchat with one or more persons. This command is what <emphasis>/join #nickname</emphasis> used to do in older BitlBee versions.
272                                </para>
273                        </description>
274                </bitlbee-command>
275        </bitlbee-command>
276
277        <bitlbee-command name="add">
278                <short-description>Add a buddy to your contact list</short-description>
279                <syntax>add &lt;connection&gt; &lt;handle&gt; [&lt;nick&gt;]</syntax>
280                <syntax>add -tmp &lt;connection&gt; &lt;handle&gt; [&lt;nick&gt;]</syntax>
281
282                <description>
283                        <para>
284                                Adds the given buddy at the specified connection to your buddy list. The account ID can be a number (see <emphasis>account list</emphasis>), the protocol name or (part of) the screenname, as long as it matches only one connection.
285                        </para>
286
287                        <para>
288                                If you want, you can also tell BitlBee what nick to give the new contact. The -tmp option adds the buddy to the internal BitlBee structures only, not to the real contact list (like done by <emphasis>set handle_unknown add</emphasis>). This allows you to talk to people who are not in your contact list. This normally won't show you any presence notifications.
289                        </para>
290                </description>
291
292                <ircexample>
293                        <ircline nick="ctrlsoft">add 3 gryp@jabber.org grijp</ircline>
294                        <ircaction nick="grijp" hostmask="gryp@jabber.org">has joined <emphasis>&amp;bitlbee</emphasis></ircaction>
295                </ircexample>
296        </bitlbee-command>
297
298        <bitlbee-command name="info">
299                <short-description>Request user information</short-description>
300                <syntax>info &lt;connection&gt; &lt;handle&gt;</syntax>
301                <syntax>info &lt;nick&gt;</syntax>
302
303                <description>
304                        <para>
305                                Requests IM-network-specific information about the specified user. The amount of information you'll get differs per protocol. For some protocols (ATM Yahoo! and MSN) it'll give you an URL which you can visit with a normal web browser to get the information.
306                        </para>
307                </description>
308
309                <ircexample>
310                        <ircline nick="ctrlsoft">info 0 72696705</ircline>
311                        <ircline nick="root">User info - UIN: 72696705   Nick: Lintux   First/Last name: Wilmer van der Gaast   E-mail: lintux@lintux.cx</ircline>
312                </ircexample>
313
314        </bitlbee-command>
315
316        <bitlbee-command name="remove">
317                <short-description>Remove a buddy from your contact list</short-description>
318                <syntax>remove &lt;nick&gt;</syntax>
319
320                <description>
321                        <para>
322                                Removes the specified nick from your buddy list.
323                        </para>
324                </description>
325
326                <ircexample>
327                        <ircline nick="ctrlsoft">remove gryp</ircline>
328                        <ircaction nick="gryp" hostmask="gryp@jabber.jabber.org">has quit <emphasis>[Leaving...]</emphasis></ircaction>
329                </ircexample>
330
331        </bitlbee-command>
332
333        <bitlbee-command name="block">
334                <short-description>Block someone</short-description>
335                <syntax>block &lt;nick&gt;</syntax>
336                <syntax>block &lt;connection&gt; &lt;handle&gt;</syntax>
337                <syntax>block &lt;connection&gt;</syntax>
338
339                <description>
340                        <para>
341                                Puts the specified user on your ignore list. Either specify the user's nick when you have him/her in your contact list or a connection number and a user handle.
342                        </para>
343                       
344                        <para>
345                                When called with only a connection specification as an argument, the command displays the current block list for that connection.
346                        </para>
347                </description>
348        </bitlbee-command>
349
350        <bitlbee-command name="allow">
351                <short-description>Unblock someone</short-description>
352                <syntax>allow &lt;nick&gt;</syntax>
353                <syntax>allow &lt;connection&gt; &lt;handle&gt;</syntax>
354
355                <description>
356                        <para>
357                                Reverse of block. Unignores the specified user or user handle on specified connection.
358                        </para>
359                       
360                        <para>
361                                When called with only a connection specification as an argument, the command displays the current allow list for that connection.
362                        </para>
363                </description>
364        </bitlbee-command>
365
366        <bitlbee-command name="set">
367                <short-description>Miscellaneous settings</short-description>
368                <syntax>set</syntax>
369                <syntax>set &lt;variable&gt;</syntax>
370                <syntax>set &lt;variable&gt; &lt;value&gt;</syntax>
371                <syntax>set -del &lt;variable&gt;</syntax>
372
373                <description>
374
375                        <para>
376                                Without any arguments, this command lists all the set variables. You can also specify a single argument, a variable name, to get that variable's value. To change this value, specify the new value as the second argument. With <emphasis>-del</emphasis> you can reset a setting to its default value.
377                        </para>
378
379                        <para>
380                                To get more help information about a setting, try:
381                        </para>
382
383                </description>
384
385                <ircexample>
386                        <ircline nick="ctrlsoft">help set private</ircline>
387                </ircexample>
388
389        </bitlbee-command>
390
391        <bitlbee-command name="help">
392                <short-description>BitlBee help system</short-description>
393
394                <syntax>help [subject]</syntax>
395
396                <description>
397                        <para>
398                                This command gives you the help information you're reading right now. If you don't give any arguments, it'll give a short help index.
399                        </para>
400                </description>
401        </bitlbee-command>
402
403        <bitlbee-command name="save">
404                <short-description>Save your account data</short-description>
405                <syntax>save</syntax>
406
407                <description>
408                        <para>
409                                This command saves all your nicks and accounts immediately. Handy if you have the autosave functionality disabled, or if you don't trust the program's stability... ;-)
410                        </para>
411                </description>
412        </bitlbee-command>
413
414        <bitlbee-setting name="account" type="string" scope="channel">
415
416                <description>
417                        <para>
418                                For control channels with <emphasis>fill_by</emphasis> set to <emphasis>account</emphasis>: Set this setting to the account id (numeric, or part of the username) of the account containing the contacts you want to see in this channel.
419                        </para>
420                </description>
421        </bitlbee-setting>
422
423        <bitlbee-setting name="allow_takeover" type="boolean" scope="global">
424                <default>true</default>
425
426                <description>
427                        <para>
428                                When you're already connected to a BitlBee server and you connect (and identify) again, BitlBee will offer to migrate your existing session to the new connection. If for whatever reason you don't want this, you can disable this setting.
429                        </para>
430                </description>
431        </bitlbee-setting>
432
433        <bitlbee-setting name="auto_connect" type="boolean" scope="both">
434                <default>true</default>
435
436                <description>
437                        <para>
438                                With this option enabled, when you identify BitlBee will automatically connect to your accounts, with this disabled it will not do this.
439                        </para>
440                       
441                        <para>
442                                This setting can also be changed for specific accounts using the <emphasis>account set</emphasis> command. (However, these values will be ignored if the global <emphasis>auto_connect</emphasis> setting is disabled!)
443                        </para>
444                </description>
445        </bitlbee-setting>
446
447        <bitlbee-setting name="auto_join" type="boolean" scope="channel">
448                <default>false</default>
449
450                <description>
451                        <para>
452                                With this option enabled, BitlBee will automatically join this channel when you log in.
453                        </para>
454                </description>
455        </bitlbee-setting>
456
457        <bitlbee-setting name="auto_reconnect" type="boolean" scope="both">
458                <default>true</default>
459
460                <description>
461                        <para>
462                                If an IM-connections breaks, you're supposed to bring it back up yourself. Having BitlBee do this automatically might not always be a good idea, for several reasons. If you want the connections to be restored automatically, you can enable this setting.
463                        </para>
464
465                        <para>
466                                See also the <emphasis>auto_reconnect_delay</emphasis> setting.
467                        </para>
468
469                        <para>
470                                This setting can also be changed for specific accounts using the <emphasis>account set</emphasis> command. (However, these values will be ignored if the global <emphasis>auto_reconnect</emphasis> setting is disabled!)
471                        </para>
472                </description>
473        </bitlbee-setting>
474
475        <bitlbee-setting name="auto_reconnect_delay" type="string" scope="global">
476                <default>5*3&lt;900</default>
477
478                <description>
479                        <para>
480                                Tell BitlBee after how many seconds it should attempt to bring a broken IM-connection back up.
481                        </para>
482
483                        <para>
484                                This can be one integer, for a constant delay. One can also set it to something like &quot;10*10&quot;, which means wait for ten seconds on the first reconnect, multiply it by ten on every failure. Once successfully connected, this delay is re-set to the initial value. With &lt; you can give a maximum delay.
485                        </para>
486
487                        <para>
488                                See also the <emphasis>auto_reconnect</emphasis> setting.
489                        </para>
490                </description>
491        </bitlbee-setting>
492
493        <bitlbee-setting name="away" type="string" scope="both">
494                <description>
495                        <para>
496                                To mark yourself as away, it is recommended to just use <emphasis>/away</emphasis>, like on normal IRC networks. If you want to mark yourself as away on only one IM network, you can use this per-account setting.
497                        </para>
498
499                        <para>
500                                You can set it to any value and BitlBee will try to map it to the most appropriate away state for every open IM connection, or set it as a free-form away message where possible.
501                        </para>
502
503                        <para>
504                                Any per-account away setting will override globally set away states. To un-set the setting, use <emphasis>set -del away</emphasis>.
505                        </para>
506                </description>
507        </bitlbee-setting>
508
509        <bitlbee-setting name="away_devoice" type="boolean" scope="global">
510                <default>true</default>
511
512                <description>
513                        <para>
514                                With this option enabled, the root user devoices people when they go away (just away, not offline) and gives the voice back when they come back. You might dislike the voice-floods you'll get if your contact list is huge, so this option can be disabled.
515                        </para>
516                </description>
517        </bitlbee-setting>
518
519        <bitlbee-setting name="away_reply_timeout" type="integer" scope="global">
520                <default>3600</default>
521
522                <description>
523                        <para>
524                                Most IRC servers send a user's away message every time s/he gets a private message, to inform the sender that they may not get a response immediately. With this setting set to 0, BitlBee will also behave like this.
525                        </para>
526
527                        <para>
528                                Since not all IRC clients do an excellent job at suppressing these messages, this setting lets BitlBee do it instead. BitlBee will wait this many seconds (or until the away state/message changes) before re-informing you that the person's away.
529                        </para>
530                </description>
531        </bitlbee-setting>
532
533        <bitlbee-setting name="charset" type="string" scope="global">
534                <default>utf-8</default>
535                <possible-values>you can get a list of all possible values by doing 'iconv -l' in a shell</possible-values>
536
537                <description>
538                        <para>
539                                This setting tells BitlBee what your IRC client sends and expects. It should be equal to the charset setting of your IRC client if you want to be able to send and receive non-ASCII text properly.
540                        </para>
541
542                        <para>
543                                Most systems use UTF-8 these days. On older systems, an iso8859 charset may work better. For example, iso8859-1 is the best choice for most Western countries. You can try to find what works best for you on http://www.unicodecharacter.com/charsets/iso8859.html
544                        </para>
545                </description>
546
547        </bitlbee-setting>
548
549        <bitlbee-setting name="control_channel" type="string" scope="global">
550                <default>&amp;bitlbee</default>
551
552                <description>
553                        <para>
554                                Normally the control channel where you can see all your contacts is called "&amp;bitlbee". If you don't like this name, you can rename it to anything else using the <emphasis>rename</emphasis> command, or by changing this setting.
555                        </para>
556                </description>
557        </bitlbee-setting>
558
559        <bitlbee-setting name="chat_type" type="string" scope="channel">
560                <default>groupchat</default>
561                <possible-values>groupchat, room</possible-values>
562
563                <description>
564                        <para>
565                                There are two kinds of chat channels: simple groupchats (basically normal IM chats with more than two participants) and names chatrooms, more similar to IRC channels.
566                        </para>
567                       
568                        <para>
569                                BitlBee supports both types. With this setting set to <emphasis>groupchat</emphasis> (the default), you can just invite people into the room and start talking.
570                        </para>
571                       
572                        <para>
573                                For setting up named chatrooms, it's currently easier to just use the <emphasis>chat add</emphasis> command.
574                        </para>
575                </description>
576        </bitlbee-setting>
577
578        <bitlbee-setting name="debug" type="boolean" scope="global">
579                <default>false</default>
580
581                <description>
582                        <para>
583                                Some debugging messages can be sent to the control channel if you wish. They're probably not really useful for you, unless you're doing some development on BitlBee.
584                        </para>
585                </description>
586        </bitlbee-setting>
587
588        <bitlbee-setting name="default_target" type="string" scope="global">
589                <default>root</default>
590                <possible-values>root, last</possible-values>
591
592                <description>
593                        <para>
594                                With this value set to <emphasis>root</emphasis>, lines written in the control channel without any nickname in front of them will be interpreted as commands. If you want BitlBee to send those lines to the last person you addressed in the control channel, set this to <emphasis>last</emphasis>.
595                        </para>
596                </description>
597        </bitlbee-setting>
598
599        <bitlbee-setting name="display_name" type="string" scope="account">
600                <description>
601                        <para>
602                                Currently only available for MSN connections. This setting allows you to read and change your "friendly name" for this connection. Since this is a server-side setting, it can't be changed when the account is off-line.
603                        </para>
604                </description>
605        </bitlbee-setting>
606
607        <bitlbee-setting name="display_namechanges" type="boolean" scope="global">
608                <default>false</default>
609
610                <description>
611                        <para>
612                                With this option enabled, root will inform you when someone in your buddy list changes his/her "friendly name".
613                        </para>
614                </description>
615        </bitlbee-setting>
616
617        <bitlbee-setting name="display_timestamps" type="boolean" scope="global">
618                <default>true</default>
619
620                <description>
621                        <para>
622                                When incoming messages are old (i.e. offline messages and channel backlogs), BitlBee will prepend them with a timestamp. If you find them ugly or useless, you can use this setting to hide them.
623                        </para>
624                </description>
625        </bitlbee-setting>
626
627        <bitlbee-setting name="fill_by" type="string" scope="channel">
628                <default>all</default>
629                <possible-values>all, group, account, protocol</possible-values>
630
631                <description>
632                        <para>
633                                For control channels only: This setting determines which contacts the channel gets populated with.
634                        </para>
635
636                        <para>
637                                By default, control channels will contain all your contacts. You instead select contacts by buddy group, IM account or IM protocol.
638                        </para>
639                       
640                        <para>
641                                Change this setting and the corresponding <emphasis>account</emphasis>/<emphasis>group</emphasis>/<emphasis>protocol</emphasis> setting to set up this selection.
642                        </para>
643                       
644                        <para>
645                                Note that, when creating a new channel, BitlBee will try to preconfigure the channel for you, based on the channel name. See <emphasis>help channels</emphasis>.
646                        </para>
647                </description>
648        </bitlbee-setting>
649
650        <bitlbee-setting name="group" type="string" scope="channel">
651
652                <description>
653                        <para>
654                                For control channels with <emphasis>fill_by</emphasis> set to <emphasis>group</emphasis>: Set this setting to the name of the group containing the contacts you want to see in this channel.
655                        </para>
656                </description>
657        </bitlbee-setting>
658
659        <bitlbee-setting name="handle_unknown" type="string" scope="global">
660                <default>add_channel</default>
661                <possible-values>root, add, add_private, add_channel, ignore</possible-values>
662
663                <description>
664                        <para>
665                                Messages from unknown users are echoed like this by default:
666                        </para>
667
668                        <ircexample>
669                                <ircline nick="root">Unknown message from handle 3137137:</ircline>
670                                <ircline nick="root">j0000! 1 4m l33t h4x0r! kill me!</ircline>
671                        </ircexample>
672
673                        <para>
674                                If you want this lame user to be added automatically, you can set this setting to "add". If you prefer to ignore messages from people you don't know, you can set this one to "ignore". "add_private" and "add_channel" are like add, but you can use them to make messages from unknown buddies appear in the channel instead of a query window.
675                        </para>
676
677                        <note>
678                                <para>
679                                        Auto-added users aren't added to your real contact list. This is because you don't want the user to get authorization requests. So when you restart BitlBee, the auto-added user will be gone. If you want to keep the person in your buddy-list, you have to fixate the add using the <emphasis>add</emphasis> command.
680                                </para>
681                        </note>
682                </description>
683
684        </bitlbee-setting>
685
686        <bitlbee-setting name="ignore_auth_requests" type="boolean" scope="account">
687                <default>false</default>
688
689                <description>
690                        <para>
691                                Only supported by OSCAR so far, you can use this setting to ignore ICQ authorization requests, which are hardly used for legitimate (i.e. non-spam) reasons anymore.
692                        </para>
693                </description>
694
695        </bitlbee-setting>
696
697        <bitlbee-setting name="lcnicks" type="boolean" scope="global">
698                <default>true</default>
699
700                <description>
701                        <para>
702                                Hereby you can change whether you want all lower case nick names or leave the case as it intended by your peer.
703                        </para>
704                </description>
705
706        </bitlbee-setting>
707
708        <bitlbee-setting name="local_display_name" type="boolean" scope="account">
709                <default>false</default>
710
711                <description>
712                        <para>
713                                Mostly meant to work around a bug in MSN servers (forgetting the display name set by the user), this setting tells BitlBee to store your display name locally and set this name on the MSN servers when connecting.
714                        </para>
715                </description>
716
717        </bitlbee-setting>
718
719        <bitlbee-setting name="mail_notifications" type="boolean" scope="account">
720                <default>false</default>
721
722                <description>
723                        <para>
724                                Some protocols (MSN, Yahoo!) can notify via IM about new e-mail. Since most people use their Hotmail/Yahoo! addresses as a spam-box, this is disabled default. If you want these notifications, you can enable this setting.
725                        </para>
726                </description>
727
728        </bitlbee-setting>
729
730        <bitlbee-setting name="message_length" type="integer" scope="account">
731                <default>140</default>
732
733                <description>
734                        <para>
735                                Since Twitter rejects messages longer than 140 characters, BitlBee can count message length and emit a warning instead of waiting for Twitter to reject it.
736                        </para>
737
738                        <para>
739                                You can change this limit here but this won't disable length checks on Twitter's side. You can also set it to 0 to disable the check in case you believe BitlBee doesn't count the characters correctly.
740                        </para>
741                </description>
742
743        </bitlbee-setting>
744
745        <bitlbee-setting name="mode" type="string" scope="account">
746                <possible-values>one, many, chat</possible-values>
747                <default>one</default>
748
749                <description>
750                        <para>
751                                By default, everything from the Twitter module will come from one nick, twitter_(yourusername). If you prefer to have individual nicks for everyone, you can set this setting to "many" instead.
752                        </para>
753                       
754                        <para>
755                                If you prefer to have all your Twitter things in a separate channel, you can set this setting to "chat".
756                        </para>
757                       
758                        <para>
759                                In the last two modes, you can send direct messages by /msg'ing your contacts directly. Note, however, that incoming DMs are not fetched yet.
760                        </para>
761                </description>
762
763        </bitlbee-setting>
764
765        <bitlbee-setting name="nick" type="string" scope="chat">
766                <description>
767                        <para>
768                                You can use this option to set your nickname in a chatroom. You won't see this nickname yourself, but other people in the room will. By default, BitlBee will use your username as the chatroom nickname.
769                        </para>
770                </description>
771        </bitlbee-setting>
772
773        <bitlbee-setting name="nick_format" type="string" scope="both">
774                <default>%-@nick</default>
775
776                <description>
777                        <para>
778                                By default, BitlBee tries to derive sensible nicknames for all your contacts from their IM handles. In some cases, IM modules (ICQ for example) will provide a nickname suggestion, which will then be used instead. This setting lets you change this behaviour.
779                        </para>
780
781                        <para>
782                                Whenever this setting is set for an account, it will be used for all its contacts. If it's not set, the global value will be used.
783                        </para>
784
785                        <para>
786                                It's easier to describe this setting using a few examples:
787                        </para>
788
789                        <para>
790                                FB-%full_name will make all nicknames start with "FB-", followed by the person's full name. For example you can set this format for your Facebook account so all Facebook contacts are clearly marked.
791                        </para>
792
793                        <para>
794                                [%group]%-@nick will make all nicknames start with the group the contact is in between square brackets, followed by the nickname suggestions from the IM module if available, or otherwise the handle. Because of the "-@" part, everything from the first @ will be stripped.
795                        </para>
796
797                        <para>
798                                See <emphasis>help nick_format</emphasis> for more information.
799                        </para>
800                </description>
801        </bitlbee-setting>
802
803        <bitlbee-setting name="nick_source" type="string" scope="account">
804                <default>handle</default>
805                <possible-values>handle, full_name, first_name</possible-values>
806
807                <description>
808                        <para>
809                                By default, BitlBee generates a nickname for every contact by taking its handle and chopping off everything after the @. In some cases, this gives very inconvenient nicknames. The Facebook XMPP server is a good example, as all Facebook XMPP handles are numeric.
810                        </para>
811
812                        <para>
813                                With this setting set to <emphasis>full_name</emphasis>, the person's full name is used to generate a nickname. Or if you don't like long nicknames, set this setting to <emphasis>first_name</emphasis> instead and only the first word will be used. Note that the full name can be full of non-ASCII characters which will be stripped off.
814                        </para>
815                </description>
816        </bitlbee-setting>
817
818        <bitlbee-setting name="oauth" type="boolean" scope="account">
819                <default>true</default>
820
821                <description>
822                        <para>
823                                This enables OAuth authentication for Twitter accounts. From June 2010 this will be mandatory.
824                        </para>
825
826                        <para>
827                                With OAuth enabled, you shouldn't tell BitlBee your Twitter password. Just add your account with a bogus password and type <emphasis>account on</emphasis>. BitlBee will then give you a URL to authenticate with Twitter. If this succeeds, Twitter will return a PIN code which you can give back to BitlBee to finish the process.
828                        </para>
829
830                        <para>
831                                The resulting access token will be saved permanently, so you have to do this only once.
832                        </para>
833                </description>
834
835        </bitlbee-setting>
836
837        <bitlbee-setting name="ops" type="string" scope="global">
838                <default>both</default>
839                <possible-values>both, root, user, none</possible-values>
840
841                <description>
842                        <para>
843                                Some people prefer themself and root to have operator status in &amp;bitlbee, other people don't. You can change these states using this setting.
844                        </para>
845
846                        <para>
847                                The value "both" means both user and root get ops. "root" means, well, just root. "user" means just the user. "none" means nobody will get operator status.
848                        </para>
849                </description>
850        </bitlbee-setting>
851
852        <bitlbee-setting name="password" type="string" scope="both">
853                <description>
854                        <para>
855                                Use this global setting to change your "NickServ" password.
856                        </para>
857                       
858                        <para>
859                                This setting is also available for all IM accounts to change the password BitlBee uses to connect to the service.
860                        </para>
861                       
862                        <para>
863                                Note that BitlBee will always say this setting is empty. This doesn't mean there is no password, it just means that, for security reasons, BitlBee stores passwords somewhere else so they can't just be retrieved in plain text.
864                        </para>
865                </description>
866        </bitlbee-setting>
867
868        <bitlbee-setting name="paste_buffer" type="boolean" scope="global">
869                <default>false</default>
870
871                <description>
872                        <para>
873                                By default, when you send a message to someone, BitlBee forwards this message to the user immediately. When you paste a large number of lines, the lines will be sent in separate messages, which might not be very nice to read. If you enable this setting, BitlBee will buffer your messages and wait for more data.
874                        </para>
875
876                        <para>
877                                Using the <emphasis>paste_buffer_delay</emphasis> setting you can specify the number of seconds BitlBee should wait for more data before the complete message is sent.
878                        </para>
879
880                        <para>
881                                Please note that if you remove a buddy from your list (or if the connection to that user drops) and there's still data in the buffer, this data will be lost. BitlBee will not try to send the message to the user in those cases.
882                        </para>
883                </description>
884        </bitlbee-setting>
885
886        <bitlbee-setting name="paste_buffer_delay" type="integer" scope="global">
887                <default>200</default>
888
889                <description>
890
891                        <para>
892                                Tell BitlBee after how many (mili)seconds a buffered message should be sent. Values greater than 5 will be interpreted as miliseconds, 5 and lower as seconds.
893                        </para>
894
895                        <para>
896                                See also the <emphasis>paste_buffer</emphasis> setting.
897                        </para>
898                </description>
899        </bitlbee-setting>
900       
901        <bitlbee-setting name="port" type="integer" scope="account">
902                <description>
903                        <para>
904                                Currently only available for Jabber connections. Specifies the port number to connect to. Usually this should be set to 5222, or 5223 for SSL-connections.
905                        </para>
906                </description>
907        </bitlbee-setting>
908
909        <bitlbee-setting name="priority" type="integer" scope="account">
910                <default>0</default>
911
912                <description>
913                        <para>
914                                Can be set for Jabber connections. When connecting to one account from multiple places, this priority value will help the server to determine where to deliver incoming messages (that aren't addressed to a specific resource already).
915                        </para>
916
917                        <para>
918                                According to RFC 3921 servers will always deliver messages to the server with the highest priority value. Mmessages will not be delivered to resources with a negative priority setting (and should be saved as an off-line message if all available resources have a negative priority value).
919                        </para>
920                </description>
921        </bitlbee-setting>
922
923        <bitlbee-setting name="private" type="boolean" scope="global">
924                <default>true</default>
925
926                <description>
927                        <para>
928                                If value is true, messages from users will appear in separate query windows. If false, messages from users will appear in the control channel.
929                        </para>
930
931                        <para>
932                                This setting is remembered (during one session) per-user, this setting only changes the default state. This option takes effect as soon as you reconnect.
933                        </para>
934                </description>
935        </bitlbee-setting>
936
937        <bitlbee-setting name="protocol" type="string" scope="channel">
938
939                <description>
940                        <para>
941                                For control channels with <emphasis>fill_by</emphasis> set to <emphasis>protocol</emphasis>: Set this setting to the name of the IM protocol of all contacts you want to see in this channel.
942                        </para>
943                </description>
944        </bitlbee-setting>
945
946        <bitlbee-setting name="query_order" type="string" scope="global">
947                <default>lifo</default>
948                <possible-values>lifo, fifo</possible-values>
949
950                <description>
951                        <para>
952                                This changes the order in which the questions from root (usually authorization requests from buddies) should be answered. When set to <emphasis>lifo</emphasis>, BitlBee immediately displays all new questions and they should be answered in reverse order. When this is set to <emphasis>fifo</emphasis>, BitlBee displays the first question which comes in and caches all the others until you answer the first one.
953                        </para>
954
955                        <para>
956                                Although the <emphasis>fifo</emphasis> setting might sound more logical (and used to be the default behaviour in older BitlBee versions), it turned out not to be very convenient for many users when they missed the first question (and never received the next ones).
957                        </para>
958                </description>
959        </bitlbee-setting>
960
961        <bitlbee-setting name="resource" type="string" scope="account">
962                <default>BitlBee</default>
963
964                <description>
965                        <para>
966                                Can be set for Jabber connections. You can use this to connect to your Jabber account from multiple clients at once, with every client using a different resource string.
967                        </para>
968                </description>
969        </bitlbee-setting>
970
971        <bitlbee-setting name="resource_select" type="string" scope="account">
972                <default>activity</default>
973                <possible-values>priority, activity</possible-values>
974
975                <description>
976                        <para>
977                                Because the IRC interface makes it pretty hard to specify the resource to talk to (when a buddy is online through different resources), this setting was added.
978                        </para>
979
980                        <para>
981                                Normally it's set to <emphasis>priority</emphasis> which means messages will always be delivered to the buddy's resource with the highest priority. If the setting is set to <emphasis>activity</emphasis>, messages will be delivered to the resource that was last used to send you a message (or the resource that most recently connected).
982                        </para>
983                </description>
984        </bitlbee-setting>
985
986        <bitlbee-setting name="root_nick" type="string" scope="global">
987                <default>root</default>
988
989                <description>
990                        <para>
991                                Normally the "bot" that takes all your BitlBee commands is called "root". If you don't like this name, you can rename it to anything else using the <emphasis>rename</emphasis> command, or by changing this setting.
992                        </para>
993                </description>
994        </bitlbee-setting>
995
996        <bitlbee-setting name="save_on_quit" type="boolean" scope="global">
997                <default>true</default>
998
999                <description>
1000                        <para>
1001                                If enabled causes BitlBee to save all current settings and account details when user disconnects. This is enabled by default, and these days there's not really a reason to have it disabled anymore.
1002                        </para>
1003                </description>
1004        </bitlbee-setting>
1005
1006        <bitlbee-setting name="server" type="string" scope="account">
1007                <description>
1008                        <para>
1009                                Can be set for Jabber- and OSCAR-connections. For Jabber, you might have to set this if the servername isn't equal to the part after the @ in the Jabber handle. For OSCAR this shouldn't be necessary anymore in recent BitlBee versions.
1010                        </para>
1011                </description>
1012        </bitlbee-setting>
1013
1014        <bitlbee-setting name="show_offline" type="boolean" scope="global">
1015                <default>false</default>
1016
1017                <description>
1018                        <para>
1019                                If enabled causes BitlBee to also show offline users in Channel. Online-users will get op, away-users voice and offline users none of both. This option takes effect as soon as you reconnect.
1020                        </para>
1021                </description>
1022        </bitlbee-setting>
1023
1024        <bitlbee-setting name="simulate_netsplit" type="boolean" scope="global">
1025                <default>true</default>
1026
1027                <description>
1028                        <para>
1029                                Some IRC clients parse quit messages sent by the IRC server to see if someone really left or just disappeared because of a netsplit. By default, BitlBee tries to simulate netsplit-like quit messages to keep the control channel window clean. If you don't like this (or if your IRC client doesn't support this) you can disable this setting.
1030                        </para>
1031                </description>
1032        </bitlbee-setting>
1033
1034        <bitlbee-setting name="ssl" type="boolean" scope="account">
1035                <default>false</default>
1036
1037                <description>
1038                        <para>
1039                                Currently only available for Jabber connections. Set this to true if the server accepts SSL connections.
1040                        </para>
1041                </description>
1042        </bitlbee-setting>
1043
1044        <bitlbee-setting name="status" type="string" scope="both">
1045                <description>
1046                        <para>
1047                                Certain protocols (like Jabber/XMPP) support status messages, similar to away messages. They can be used to indicate things like your location or activity, without showing up as away/busy.
1048                        </para>
1049
1050                        <para>
1051                                This setting can be used to set such a message. It will be available as a per-account setting for protocols that support it, and also as a global setting (which will then automatically be used for all protocols that support it).
1052                        </para>
1053
1054                        <para>
1055                                Away states set using <emphasis>/away</emphasis> or the <emphasis>away</emphasis> setting will override this setting. To un-set the setting, use <emphasis>set -del status</emphasis>.
1056                        </para>
1057                </description>
1058        </bitlbee-setting>
1059
1060        <bitlbee-setting name="strip_html" type="boolean" scope="global">
1061                <default>true</default>
1062
1063                <description>
1064                        <para>
1065                                Determines what BitlBee should do with HTML in messages. Normally this is turned on and HTML will be stripped from messages, if BitlBee thinks there is HTML.
1066                        </para>
1067                        <para>
1068                                If BitlBee fails to detect this sometimes (most likely in AIM messages over an ICQ connection), you can set this setting to <emphasis>always</emphasis>, but this might sometimes accidentally strip non-HTML things too.
1069                        </para>
1070                </description>
1071        </bitlbee-setting>
1072
1073        <bitlbee-setting name="switchboard_keepalives" type="boolean" scope="account">
1074                <default>false</default>
1075
1076                <description>
1077                        <para>
1078                                Turn on this flag if you have difficulties talking to offline/invisible contacts.
1079                        </para>
1080                       
1081                        <para>
1082                                With this setting enabled, BitlBee will send keepalives to MSN switchboards with offline/invisible contacts every twenty seconds. This should keep the server and client on the other side from shutting it down.
1083                        </para>
1084                       
1085                        <para>
1086                                This is useful because BitlBee doesn't support MSN offline messages yet and the MSN servers won't let the user reopen switchboards to offline users. Once offline messaging is supported, this flag might be removed.
1087                        </para>
1088                </description>
1089        </bitlbee-setting>
1090
1091        <bitlbee-setting name="timezone" type="string" scope="global">
1092                <default>local</default>
1093                <possible-values>local, utc, gmt, timezone-spec</possible-values>
1094
1095                <description>
1096                        <para>
1097                                If message timestamps are available for offline messages or chatroom backlogs, BitlBee will display them as part of the message. By default it will use the local timezone. If you're not in the same timezone as the BitlBee server, you can adjust the timestamps using this setting.
1098                        </para>
1099
1100                        <para>
1101                                Values local/utc/gmt should be self-explanatory. timezone-spec is a time offset in hours:minutes, for example: -8 for Pacific Standard Time, +2 for Central European Summer Time, +5:30 for Indian Standard Time.
1102                        </para>
1103                </description>
1104        </bitlbee-setting>
1105
1106        <bitlbee-setting name="tls" type="boolean" scope="account">
1107                <default>try</default>
1108
1109                <description>
1110                        <para>
1111                                Newer Jabber servers allow clients to convert a plain-text session to a TLS/SSL-encrypted session. Normally (with this setting set to <emphasis>try</emphasis>) BitlBee will do this, if possible.
1112                        </para>
1113
1114                        <para>
1115                                If you want to force BitlBee to use TLS sessions only (and to give up if that doesn't seem to be possible) you can set this setting to <emphasis>true</emphasis>. Set it to <emphasis>false</emphasis> if you want the session to remain plain-text.
1116                        </para>
1117                </description>
1118        </bitlbee-setting>
1119
1120        <bitlbee-setting name="to_char" type="string" scope="global">
1121                <default>": "</default>
1122
1123                <description>
1124                        <para>
1125                                It's customary that messages meant for one specific person on an IRC channel are prepended by his/her alias followed by a colon ':'. BitlBee does this by default. If you prefer a different character, you can set it using <emphasis>set to_char</emphasis>.
1126                        </para>
1127
1128                        <para>
1129                                Please note that this setting is only used for incoming messages. For outgoing messages you can use ':' (colon) or ',' to separate the destination nick from the message, and this is not configurable.
1130                        </para>
1131                </description>
1132        </bitlbee-setting>
1133
1134        <bitlbee-setting name="translate_to_nicks" type="boolean" scope="channel">
1135                <default>true</default>
1136
1137                <description>
1138                        <para>
1139                                IRC's nickname namespace is quite limited compared to most IM protocols. Not any non-ASCII characters are allowed, in fact nicknames have to be mostly alpha-numeric. Also, BitlBee has to add underscores sometimes to avoid nickname collisions.
1140                        </para>
1141
1142                        <para>
1143                                While normally the BitlBee user is the only one seeing these names, they may be exposed to other chatroom participants for example when addressing someone in the channel (with or without tab completion). By default BitlBee will translate these stripped nicknames back to the original nick. If you don't want this, disable this setting.
1144                        </para>
1145                </description>
1146        </bitlbee-setting>
1147
1148        <bitlbee-setting name="type" type="string" scope="channel">
1149                <default>control</default>
1150                <possible-values>control, chat</possible-values>
1151
1152                <description>
1153                        <para>
1154                                BitlBee supports two kinds of channels: control channels (usually with a name starting with a &amp;) and chatroom channels (name usually starts with a #).
1155                        </para>
1156
1157                        <para>
1158                                See <emphasis>help channels</emphasis> for a full description of channel types in BitlBee.
1159                        </para>
1160                </description>
1161        </bitlbee-setting>
1162
1163        <bitlbee-setting name="typing_notice" type="boolean" scope="global">
1164                <default>false</default>
1165
1166                <description>
1167                        <para>
1168                                Sends you a /notice when a user starts typing a message (if supported by the IM protocol and the user's client). To use this, you most likely want to use a script in your IRC client to show this information in a more sensible way.
1169                        </para>
1170                </description>
1171        </bitlbee-setting>
1172
1173        <bitlbee-setting name="user_agent" type="string" scope="account">
1174                <default>BitlBee</default>
1175
1176                <description>
1177                        <para>
1178                                Some Jabber servers are configured to only allow a few (or even just one) kinds of XMPP clients to connect to them.
1179                        </para>
1180                       
1181                        <para>
1182                                You can change this setting to make BitlBee present itself as a different client, so that you can still connect to these servers.
1183                        </para>
1184                </description>
1185        </bitlbee-setting>
1186
1187        <bitlbee-setting name="web_aware" type="string" scope="account">
1188                <default>false</default>
1189
1190                <description>
1191                        <para>
1192                                ICQ allows people to see if you're on-line via a CGI-script. (http://status.icq.com/online.gif?icq=UIN) This can be nice to put on your website, but it seems that spammers also use it to see if you're online without having to add you to their contact list. So to prevent ICQ spamming, recent versions of BitlBee disable this feature by default.
1193                        </para>
1194
1195                        <para>
1196                                Unless you really intend to use this feature somewhere (on forums or maybe a website), it's probably better to keep this setting disabled.
1197                        </para>
1198                </description>
1199        </bitlbee-setting>
1200
1201        <bitlbee-setting name="xmlconsole" type="boolean" scope="account">
1202                <default>false</default>
1203
1204                <description>
1205                        <para>
1206                                The Jabber module allows you to add a buddy <emphasis>xmlconsole</emphasis> to your contact list, which will then show you the raw XMPP stream between you and the server. You can also send XMPP packets to this buddy, which will then be sent to the server.
1207                        </para>
1208                        <para>
1209                                If you want to enable this XML console permanently (and at login time already), you can set this setting.
1210                        </para>
1211                </description>
1212        </bitlbee-setting>
1213
1214        <bitlbee-command name="rename">
1215                <short-description>Rename (renick) a buddy</short-description>
1216                <syntax>rename &lt;oldnick&gt; &lt;newnick&gt;</syntax>
1217
1218                <description>
1219                        <para>
1220                                Renick a user in your buddy list. Very useful, in fact just very important, if you got a lot of people with stupid account names (or hard ICQ numbers).
1221                        </para>
1222                </description>
1223
1224                <ircexample>
1225                        <ircline nick="itsme">rename itsme_ you</ircline>
1226                        <ircaction nick="itsme_">is now known as <emphasis>you</emphasis></ircaction>
1227                </ircexample>
1228
1229        </bitlbee-command>
1230
1231        <bitlbee-command name="yes">
1232                <short-description>Accept a request</short-description>
1233                <syntax>yes [&lt;number&gt;]</syntax>
1234
1235                <description>
1236                        <para>
1237                                Sometimes an IM-module might want to ask you a question. (Accept this user as your buddy or not?) To accept a question, use the <emphasis>yes</emphasis> command.
1238                        </para>
1239
1240                        <para>
1241                                By default, this answers the first unanswered question. You can also specify a different question as an argument. You can use the <emphasis>qlist</emphasis> command for a list of questions.
1242                        </para>
1243                </description>
1244
1245        </bitlbee-command>
1246
1247        <bitlbee-command name="no">
1248                <short-description>Deny a request</short-description>
1249                <syntax>no [&lt;number&gt;]</syntax>
1250
1251                <description>
1252                        <para>
1253                                Sometimes an IM-module might want to ask you a question. (Accept this user as your buddy or not?) To reject a question, use the <emphasis>no</emphasis> command.
1254                        </para>
1255
1256                        <para>
1257                                By default, this answers the first unanswered question. You can also specify a different question as an argument. You can use the <emphasis>qlist</emphasis> command for a list of questions.
1258                        </para>
1259                </description>
1260        </bitlbee-command>
1261
1262        <bitlbee-command name="qlist">
1263                <short-description>List all the unanswered questions root asked</short-description>
1264                <syntax>qlist</syntax>
1265
1266                <description>
1267                        <para>
1268                                This gives you a list of all the unanswered questions from root.
1269                        </para>
1270                </description>
1271
1272        </bitlbee-command>
1273
1274        <bitlbee-command name="register">
1275                <short-description>Register yourself</short-description>
1276                <syntax>register &lt;password&gt;</syntax>
1277
1278                <description>
1279                        <para>
1280                                BitlBee can save your settings so you won't have to enter all your IM passwords every time you log in. If you want the Bee to save your settings, use the <emphasis>register</emphasis> command.
1281                        </para>
1282
1283                        <para>
1284                                Please do pick a secure password, don't just use your nick as your password. Please note that IRC is not an encrypted protocol, so the passwords still go over the network in plaintext. Evil people with evil sniffers will read it all. (So don't use your root password.. ;-)
1285                        </para>
1286
1287                        <para>
1288                                To identify yourself in later sessions, you can use the <emphasis>identify</emphasis> command. To change your password later, you can use the <emphasis>set password</emphasis> command.
1289                        </para>
1290                </description>
1291
1292        </bitlbee-command>
1293
1294        <bitlbee-command name="identify">
1295                <syntax>identify [-noload|-force] &lt;password&gt;</syntax>
1296                <short-description>Identify yourself with your password</short-description>
1297
1298                <description>
1299                        <para>
1300                                BitlBee saves all your settings (contacts, accounts, passwords) on-server. To prevent other users from just logging in as you and getting this information, you'll have to identify yourself with your password. You can register this password using the <emphasis>register</emphasis> command.
1301                        </para>
1302
1303                        <para>
1304                                Once you're registered, you can change your password using <emphasis>set password &lt;password&gt;</emphasis>.
1305                        </para>
1306
1307                        <para>
1308                                The <emphasis>-noload</emphasis> and <emphasis>-force</emphasis> flags can be used to identify when you're logged into some IM accounts already. <emphasis>-force</emphasis> will let you identify yourself and load all saved accounts (and keep the accounts you're logged into already).
1309                        </para>
1310                       
1311                        <para>
1312                                <emphasis>-noload</emphasis> will log you in but not load any accounts and settings saved under your current nickname. These will be overwritten once you save your settings (i.e. when you disconnect).
1313                        </para>
1314                </description>
1315        </bitlbee-command>
1316
1317        <bitlbee-command name="drop">
1318                <syntax>drop &lt;password&gt;</syntax>
1319                <short-description>Drop your account</short-description>
1320
1321                <description>
1322                        <para>
1323                                Drop your BitlBee registration. Your account files will be removed and your password will be forgotten. For obvious security reasons, you have to specify your NickServ password to make this command work.
1324                        </para>
1325                </description>
1326        </bitlbee-command>
1327
1328        <bitlbee-command name="blist">
1329                <syntax>blist [all|online|offline|away]</syntax>
1330                <short-description>List all the buddies in your contact list</short-description>
1331
1332                <description>
1333                        <para>
1334                                You can get a better readable buddy list using the <emphasis>blist</emphasis> command. If you want a complete list (including the offline users) you can use the <emphasis>all</emphasis> argument.
1335                        </para>
1336                </description>
1337
1338        </bitlbee-command>
1339
1340        <bitlbee-command name="nick">
1341                <short-description>Change friendly name, nick</short-description>
1342                <syntax>nick &lt;connection&gt; [&lt;new nick&gt;]</syntax>
1343                <syntax>nick &lt;connection&gt;</syntax>
1344
1345                <description>
1346                        <para>
1347                                Deprecated: Use the per-account <emphasis>display_name</emphasis> setting to read and change this information.
1348                        </para>
1349                </description>
1350
1351                <ircexample>
1352                        <ircline nick="wouter">account 1 set display_name "The majestik møøse"</ircline>
1353                        <ircline nick="root">display_name = `The majestik møøse'</ircline>
1354                </ircexample>
1355
1356        </bitlbee-command>
1357       
1358        <bitlbee-command name="transfers">
1359                <short-description>Monitor, cancel, or reject file transfers</short-description>
1360                <syntax>transfers [&lt;cancel&gt; id | &lt;reject&gt;]</syntax>
1361               
1362                <description>
1363                        <para>
1364                                Without parameters the currently pending file transfers and their status will be listed. Available actions are <emphasis>cancel</emphasis> and <emphasis>reject</emphasis>. See <emphasis>help transfers &lt;action&gt;</emphasis> for more information.
1365                        </para>
1366
1367                        <ircexample>
1368                                <ircline nick="ulim">transfers</ircline>
1369                        </ircexample>
1370                </description>
1371               
1372                <bitlbee-command name="cancel">
1373                        <short-description>Cancels the file transfer with the given id</short-description>
1374                        <syntax>transfers &lt;cancel&gt; id</syntax>
1375
1376                        <description>
1377                                <para>Cancels the file transfer with the given id</para>
1378                        </description>
1379
1380                        <ircexample>
1381                                <ircline nick="ulim">transfers cancel 1</ircline>
1382                                <ircline nick="root">Canceling file transfer for test</ircline>
1383                        </ircexample>
1384                </bitlbee-command>
1385
1386                <bitlbee-command name="reject">
1387                        <short-description>Rejects all incoming transfers</short-description>
1388                        <syntax>transfers &lt;reject&gt;</syntax>
1389
1390                        <description>
1391                                <para>Rejects all incoming (not already transferring) file transfers. Since you probably have only one incoming transfer at a time, no id is neccessary. Or is it?</para>
1392                        </description>
1393
1394                        <ircexample>
1395                                <ircline nick="ulim">transfers reject</ircline>
1396                        </ircexample>
1397                </bitlbee-command>
1398        </bitlbee-command>
1399       
1400</chapter>
Note: See TracBrowser for help on using the repository browser.