Context Navigation

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

Last change on this file since f32d557 was 9b8efab, checked in by Wilmer van der Gaast <wilmer@…>, at 2006-03-21T08:38:15Z
Updated documentation for the new block/allow syntax. Yes, it's slightly ambiguous now, but it shouldn't cause problems.
Property mode set to `100644`
File size: 25.9 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 <action> [<arguments>]</syntax>
9
10	<description>
11
12	<para>
13	Available actions: add, del, list, on, off. See <emphasis>help account <action></emphasis> for more information.
14	</para>
15
16	</description>
17
18	<bitlbee-command name="add">
19	<syntax>account add <protocol> <username> <password> [<server>]</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) and Yahoo. For more information about adding an account, see <emphasis>help account add <protocol></emphasis>.
24	</para>
25	</description>
26
27	<bitlbee-command name="jabber">
28	<syntax>account add jabber <handle> <password> [<servertag>]</syntax>
29
30	<description>
31	<para>
32	Note that the servertag argument is optional. You only have to use it if the part after the @ in your handle isn't the hostname of your Jabber server, or if you want to use SSL/connect to a non-standard port number. The format is simple: [<servername>[:<portnumber>][:ssl]]. For example, this is how you can connect to Google Talk:
33	</para>
34	</description>
35
36	<ircexample>
37	<ircline nick="wilmer">account add jabber example@gmail.com hobbelmeeuw talk.google.com:5223:ssl</ircline>
38	<ircline nick="root">Account successfully added</ircline>
39	</ircexample>
40
41	<description>
42	<para>
43	Note that Google talk is SSL-only, but officially reachable over both port 5222 and 5223. However, for some people only port 5222 works, for some people only 5223. This is something you'll have to try out.
44	</para>
45	</description>
46	</bitlbee-command>
47
48	<bitlbee-command name="msn">
49	<syntax>account add msn <handle> <password></syntax>
50
51	<description>
52	<para>
53	For MSN connections there are no special arguments.
54	</para>
55	</description>
56	</bitlbee-command>
57
58	<bitlbee-command name="oscar">
59	<syntax>account add oscar <handle> <password> [<servername>]</syntax>
60
61	<description>
62	<para>
63	Specifying a server is required for OSCAR, since OSCAR can be used for both ICQ- and AIM-connections. Although these days it's supposed to be possible to connect to ICQ via AIM-servers and vice versa, we like to stick with this separation for now. For ICQ connections, the servername is <emphasis>login.icq.com</emphasis>, for AIM connections it's <emphasis>login.oscar.aol.com</emphasis>.
64	</para>
65	</description>
66
67	<ircexample>
68	<ircline nick="wilmer">account add oscar 72696705 hobbelmeeuw login.icq.com</ircline>
69	<ircline nick="root">Account successfully added</ircline>
70	</ircexample>
71	</bitlbee-command>
72
73	<bitlbee-command name="yahoo">
74	<syntax>account add yahoo <handle> <password></syntax>
75
76	<description>
77	<para>
78	For Yahoo! connections there are no special arguments.
79	</para>
80	</description>
81	</bitlbee-command>
82
83	</bitlbee-command>
84
85	<bitlbee-command name="del">
86	<syntax>account del <account id></syntax>
87
88	<description>
89	<para>
90	This commands deletes an account from your account list. You should signoff the account before deleting it.
91	</para>
92
93
94	<para>
95	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.
96	</para>
97	</description>
98	</bitlbee-command>
99
100	<bitlbee-command name="on">
101	<syntax>account on [<account id>]</syntax>
102
103	<description>
104	<para>
105	This command will try to log into the specified account. If no account is specified, BitlBee will log into all the accounts. (Including accounts awaiting a reconnection)
106	</para>
107
108	<para>
109	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.
110	</para>
111	</description>
112
113	</bitlbee-command>
114
115	<bitlbee-command name="off">
116	<syntax>account off [<account id>]</syntax>
117
118	<description>
119	<para>
120	This command disconnects the connection for the specified account. If no account is specified, BitlBee will deactivate all active accounts. (Including accounts awaiting a reconnection)
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	</bitlbee-command>
128
129	<bitlbee-command name="list">
130	<syntax>account list</syntax>
131
132	<description>
133	<para>
134	This command gives you a list of all the accounts known by BitlBee, including the numbers you'll need for most account commands.
135	</para>
136	</description>
137	</bitlbee-command>
138	</bitlbee-command>
139
140	<bitlbee-command name="add">
141	<short-description>Add a buddy to your contact list</short-description>
142	<syntax>add <connection> <handle> [<nick>]</syntax>
143
144	<description>
145	<para>
146	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.
147	</para>
148
149	<para>
150	If you want, you can also tell BitlBee what nick to give the new contact. Of course you can also use the <emphasis>rename</emphasis> command for that, but sometimes this might be more convenient.
151	</para>
152	</description>
153
154	<ircexample>
155	<ircline nick="ctrlsoft">add 3 gryp@jabber.org grijp</ircline>
156	<ircaction nick="grijp" hostmask="gryp@jabber.org">has joined <emphasis>&bitlbee</emphasis></ircaction>
157	</ircexample>
158	</bitlbee-command>
159
160	<bitlbee-command name="info">
161	<short-description>Request user information</short-description>
162	<syntax>info <connection> <handle></syntax>
163	<syntax>info <nick></syntax>
164
165	<description>
166	<para>
167	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.
168	</para>
169	</description>
170
171	<ircexample>
172	<ircline nick="ctrlsoft">info 0 72696705</ircline>
173	<ircline nick="root">User info - UIN: 72696705 Nick: Lintux First/Last name: Wilmer van der Gaast E-mail: lintux@lintux.cx</ircline>
174	</ircexample>
175
176	</bitlbee-command>
177
178	<bitlbee-command name="remove">
179	<short-description>Remove a buddy from your contact list</short-description>
180	<syntax>remove <nick></syntax>
181
182	<description>
183	<para>
184	Removes the specified nick from your buddy list.
185	</para>
186	</description>
187
188	<ircexample>
189	<ircline nick="ctrlsoft">remove gryp</ircline>
190	<ircaction nick="gryp" hostmask="gryp@jabber.jabber.org">has quit <emphasis>[Leaving...]</emphasis></ircaction>
191	</ircexample>
192
193	</bitlbee-command>
194
195	<bitlbee-command name="block">
196	<short-description>Block someone</short-description>
197	<syntax>block <nick></syntax>
198	<syntax>block <connection> <handle></syntax>
199	<syntax>block <connection></syntax>
200
201	<description>
202	<para>
203	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.
204	</para>
205
206	<para>
207	When called with only a connection specification as an argument, the command displays the current block list for that connection.
208	</para>
209	</description>
210	</bitlbee-command>
211
212	<bitlbee-command name="allow">
213	<short-description>Unblock someone</short-description>
214	<syntax>allow <nick></syntax>
215	<syntax>allow <connection> <handle></syntax>
216
217	<description>
218	<para>
219	Reverse of block. Unignores the specified user or user handle on specified connection.
220	</para>
221
222	<para>
223	When called with only a connection specification as an argument, the command displays the current allow list for that connection.
224	</para>
225	</description>
226	</bitlbee-command>
227
228	<bitlbee-command name="set">
229	<short-description>Miscellaneous settings</short-description>
230	<syntax>set [<variable> [<value>]]</syntax>
231
232	<description>
233
234	<para>
235	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.
236	</para>
237
238	<para>
239	To get more help information about a setting, try:
240	</para>
241
242	</description>
243
244	<ircexample>
245	<ircline nick="ctrlsoft">help set private</ircline>
246	</ircexample>
247
248	</bitlbee-command>
249
250	<bitlbee-command name="help">
251	<short-description>BitlBee help system</short-description>
252
253	<syntax>help [subject]</syntax>
254
255	<description>
256	<para>
257	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.
258	</para>
259	</description>
260	</bitlbee-command>
261
262	<bitlbee-command name="save">
263	<short-description>Save your account data</short-description>
264	<syntax>save</syntax>
265
266	<description>
267	<para>
268	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... ;-)
269	</para>
270	</description>
271	</bitlbee-command>
272
273	<bitlbee-setting name="charset" type="string">
274	<default>iso8859-1</default>
275	<possible-values>you can get a list of all possible values by doing 'iconv -l' in a shell</possible-values>
276
277	<description>
278	<para>
279	The charset setting enables you to use different character sets in BitlBee. These get converted to UTF-8 before sending and from UTF-8 when receiving.
280	</para>
281
282	<para>
283	If you don't know what's the best value for this, at least iso8859-1 is the best choice for most Western countries. You can try to find what works best for you on http://czyborra.com/charsets/iso8859.html
284	</para>
285	</description>
286
287	</bitlbee-setting>
288
289	<bitlbee-setting name="private" type="boolean">
290	<default>True</default>
291
292	<description>
293
294	<para>
295	If value is true, messages from users will appear in separate query windows. If false, messages from users will appear in the control channel.
296	</para>
297
298	<para>
299	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.
300	</para>
301	</description>
302	</bitlbee-setting>
303
304	<bitlbee-setting name="save_on_quit" type="boolean">
305	<default>True</default>
306
307	<description>
308	<para>
309	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.
310	</para>
311	</description>
312	</bitlbee-setting>
313
314	<bitlbee-setting name="strip_html" type="boolean">
315	<default>True</default>
316
317	<description>
318	<para>
319	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.
320	</para>
321	<para>
322	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.
323	</para>
324	</description>
325	</bitlbee-setting>
326
327	<bitlbee-setting name="debug" type="boolean">
328	<default>False</default>
329
330	<description>
331	<para>
332	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.
333	</para>
334	</description>
335	</bitlbee-setting>
336
337	<bitlbee-setting name="to_char" type="string">
338	<default>": "</default>
339
340	<description>
341
342	<para>
343	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>.
344	</para>
345
346	<para>
347	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.
348	</para>
349	</description>
350	</bitlbee-setting>
351
352	<bitlbee-setting name="typing_notice" type="boolean">
353	<default>False</default>
354
355	<description>
356	<para>
357	Sends you a /notice when a user starts typing a message (if the protocol supports it, MSN for example). This is a bug, not a feature. (But please don't report it.. ;-) You don't want to use it. Really. In fact the typing-notification is just one of the least useful 'innovations' ever. It's just there because some guy will probably ask me about it anyway. ;-)
358	</para>
359	</description>
360	</bitlbee-setting>
361
362	<bitlbee-setting name="ops" type="string">
363	<default>both</default>
364	<possible-values>both, root, user, none</possible-values>
365
366	<description>
367	<para>
368	Some people prefer themself and root to have operator status in &bitlbee, other people don't. You can change these states using this setting.
369	</para>
370
371	<para>
372	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.
373	</para>
374	</description>
375	</bitlbee-setting>
376
377	<bitlbee-setting name="away_devoice" type="boolean">
378	<default>True</default>
379
380	<description>
381	<para>
382	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.
383	</para>
384	</description>
385	</bitlbee-setting>
386
387	<bitlbee-setting name="handle_unknown" type="string">
388	<default>root</default>
389	<possible-values>root, add, add_private, add_channel, ignore</possible-values>
390
391	<description>
392	<para>
393	Messages from unknown users are echoed like this by default:
394	</para>
395
396	<ircexample>
397	<ircline nick="root">Unknown message from handle 3137137:</ircline>
398	<ircline nick="root">j0000! 1 4m l33t h4x0r! kill me!</ircline>
399	</ircexample>
400
401	<para>
402	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.
403	</para>
404
405	<note>
406	<para>
407	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.
408	</para>
409	</note>
410	</description>
411
412	</bitlbee-setting>
413
414	<bitlbee-setting name="auto_connect" type="boolean">
415	<default>True</default>
416
417	<description>
418	<para>
419	With this option enabled, when you identify BitlBee will automatically connect to your accounts, with this disabled it will not do this.
420	</para>
421	</description>
422	</bitlbee-setting>
423
424	<bitlbee-setting name="auto_reconnect" type="boolean">
425	<default>False</default>
426
427	<description>
428	<para>
429	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.
430	</para>
431
432	<para>
433	See also the <emphasis>auto_reconnect_delay</emphasis> setting.
434	</para>
435	</description>
436
437	</bitlbee-setting>
438
439	<bitlbee-setting name="auto_reconnect_delay" type="integer">
440	<default>300</default>
441
442	<description>
443
444	<para>
445	Tell BitlBee after how many seconds it should attempt to bring an IM-connection back up after a crash. It's not a good idea to set this value very low, it will cause too much useless traffic when an IM-server is down for a few hours.
446	</para>
447
448	<para>
449	See also the <emphasis>auto_reconnect</emphasis> setting.
450	</para>
451	</description>
452	</bitlbee-setting>
453
454	<bitlbee-setting name="buddy_sendbuffer" type="boolean">
455	<default>False</default>
456
457	<description>
458
459	<para>
460	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.
461	</para>
462
463	<para>
464	Using the <emphasis>buddy_sendbuffer_delay</emphasis> setting you can specify the number of seconds BitlBee should wait for more data before the complete message is sent.
465	</para>
466
467	<para>
468	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.
469	</para>
470	</description>
471
472	</bitlbee-setting>
473
474	<bitlbee-setting name="buddy_sendbuffer_delay" type="integer">
475	<default>200</default>
476
477	<description>
478
479	<para>
480	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.
481	</para>
482
483	<para>
484	See also the <emphasis>buddy_sendbuffer</emphasis> setting.
485	</para>
486	</description>
487
488	</bitlbee-setting>
489
490	<bitlbee-setting name="default_target" type="string">
491	<default>root</default>
492	<possible-values>root, last</possible-values>
493
494	<description>
495	<para>
496	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>.
497	</para>
498	</description>
499
500	</bitlbee-setting>
501
502	<bitlbee-setting name="display_namechanges" type="boolean">
503	<default>False</default>
504
505	<para>
506	With this option enabled, root will inform you when someone in your buddy list changes his/her "friendly name".
507	</para>
508	</bitlbee-setting>
509
510	<bitlbee-setting name="password" type="string">
511	<description>
512	<para>
513	Use this setting to change your "NickServ" password.
514	</para>
515	</description>
516	</bitlbee-setting>
517
518	<bitlbee-setting name="query_order" type="string">
519	<default>lifo</default>
520	<possible-values>lifo, fifo</possible-values>
521
522	<description>
523	<para>
524	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.
525	</para>
526
527	<para>
528	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).
529	</para>
530	</description>
531	</bitlbee-setting>
532
533	<bitlbee-setting name="lcnicks" type="boolean">
534	<default>True</default>
535
536	<description>
537	<para>
538	Hereby you can change whether you want all lower case nick names or leave the case as it intended by your peer.
539	</para>
540	</description>
541
542	</bitlbee-setting>
543
544	<bitlbee-command name="rename">
545	<short-description>Rename (renick) a buddy</short-description>
546	<syntax>rename <oldnick> <newnick></syntax>
547
548	<description>
549	<para>
550	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).
551	</para>
552	</description>
553
554	<ircexample>
555	<ircline nick="itsme">rename itsme_ you</ircline>
556	<ircaction nick="itsme_">is now known as <emphasis>you</emphasis></ircaction>
557	</ircexample>
558
559	</bitlbee-command>
560
561	<bitlbee-command name="yes">
562	<short-description>Accept a request</short-description>
563	<syntax>yes [<number>]</syntax>
564
565	<description>
566	<para>
567	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.
568	</para>
569
570	<para>
571	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.
572	</para>
573	</description>
574
575	</bitlbee-command>
576
577	<bitlbee-command name="no">
578	<short-description>Deny a request</short-description>
579	<syntax>no [<number>]</syntax>
580
581	<description>
582	<para>
583	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.
584	</para>
585
586	<para>
587	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.
588	</para>
589	</description>
590	</bitlbee-command>
591
592	<bitlbee-command name="qlist">
593	<short-description>List all the unanswered questions root asked</short-description>
594	<syntax>qlist</syntax>
595
596	<description>
597	<para>
598	This gives you a list of all the unanswered questions from root.
599	</para>
600	</description>
601
602	</bitlbee-command>
603
604	<bitlbee-command name="register">
605	<short-description>Register yourself</short-description>
606	<syntax>register <password></syntax>
607
608	<description>
609	<para>
610	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.
611	</para>
612
613	<para>
614	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.. ;-)
615	</para>
616
617	<para>
618	To identify yourself in later sessions, you can use the <emphasis>identify</emphasis> command.
619	</para>
620	</description>
621
622	</bitlbee-command>
623
624	<bitlbee-command name="identify">
625	<syntax>identify <password></syntax>
626	<short-description>Identify yourself with your password</short-description>
627
628	<description>
629	<para>
630	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.
631	</para>
632
633	<para>
634	Once you're registered, you can change your password using <emphasis>set password <password></emphasis>.
635	</para>
636	</description>
637	</bitlbee-command>
638
639	<bitlbee-command name="drop">
640	<syntax>drop <password></syntax>
641	<short-description>Drop your account</short-description>
642
643	<description>
644	<para>
645	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.
646	</para>
647	</description>
648	</bitlbee-command>
649
650	<bitlbee-command name="blist">
651	<syntax>blist [all\|online\|offline\|away]</syntax>
652	<short-description>List all the buddies in your contact list</short-description>
653
654	<description>
655	<para>
656	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.
657	</para>
658	</description>
659
660	</bitlbee-command>
661
662	<bitlbee-command name="nick">
663	<short-description>Change friendly name, nick</short-description>
664	<syntax>nick <connection> [<new nick>]</syntax>
665	<syntax>nick</syntax>
666
667	<description>
668	<para>
669	This command allows to set the friendly name of an im account. If no new name is specified the command will report the current name. When the name contains spaces, don't forget to quote the whole nick in double quotes. Currently this command is only supported by the MSN protocol.
670	</para>
671	</description>
672
673	<ircexample>
674	<ircline nick="wouter">nick 1 "Wouter Paesen"</ircline>
675	<ircline nick="root">Setting your name on connection 1 to `Wouter Paesen'</ircline>
676	</ircexample>
677
678	</bitlbee-command>
679
680	<bitlbee-command name="import_buddies">
681	<short-description>Copy local buddy list to server (normally only needed when upgrading)</short-description>
682	<syntax>import_buddies <connection> [clear]</syntax>
683
684	<description>
685	<para>
686	This command copies the locally stored buddy list to the server. This command exists for upgrading purposes. Previous versions of BitlBee didn't support server-side buddy lists for ICQ, so the list was stored locally.
687	</para>
688
689	<para>
690	Since version 0.91 however, server-side contact lists are supported for all protocols, so the local list is now ignored. When upgrading from an older BitlBee to version 0.91, you might need this command to get your buddy list back.
691	</para>
692
693	<para>
694	The only argument this command needs is your ICQ account identification. If your serverside buddy list contains some old buddies you don't want anymore, you can pass <emphasis>clear</emphasis> as a second argument.
695	</para>
696
697	<para>
698	After giving this command, you have to wait for a while before all the adds are handled, because of ICQ's rate limiting. If your buddy list is very large and the ICQ server starts complaining, you might have to reconnect and enter this command again.
699	</para>
700	</description>
701
702	</bitlbee-command>
703	</chapter>

Note: See TracBrowser for help on using the repository browser.

Download in other formats: