Context Navigation

source: doc/user-guide/commands.xml @ 61ae52c

Last change on this file since 61ae52c was e617b35, checked in by Wilmer van der Gaast <wilmer@…>, at 2006-10-15T15:34:57Z
Merging from main development tree.
Property mode set to `100644`
File size: 32.9 KB

Rev	Line
[b7d3cc34]	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>
[75a4b85]	13	Available actions: add, del, list, on, off and set. See <emphasis>help account <action></emphasis> for more information.
[b7d3cc34]	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">
[75a4b85]	28	<syntax>account add jabber <handle@server.tld> <password> [<servertag>]</syntax>
[b7d3cc34]	29
	30	<description>
	31	<para>
[ee5c355]	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.
[b7d3cc34]	33	</para>
	34
	35	<para>
[ee5c355]	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>).
[b7d3cc34]	37	</para>
	38	</description>
	39	</bitlbee-command>
	40
	41	<bitlbee-command name="msn">
[75a4b85]	42	<syntax>account add msn <handle@server.tld> <password></syntax>
[b7d3cc34]	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 <handle> <password> [<servername>]</syntax>
	53
	54	<description>
	55	<para>
	56	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>.
	57	</para>
	58	</description>
	59
	60	<ircexample>
	61	<ircline nick="wilmer">account add oscar 72696705 hobbelmeeuw login.icq.com</ircline>
	62	<ircline nick="root">Account successfully added</ircline>
	63	</ircexample>
	64	</bitlbee-command>
	65
	66	<bitlbee-command name="yahoo">
	67	<syntax>account add yahoo <handle> <password></syntax>
	68
	69	<description>
	70	<para>
	71	For Yahoo! connections there are no special arguments.
	72	</para>
	73	</description>
	74	</bitlbee-command>
	75
	76	</bitlbee-command>
	77
	78	<bitlbee-command name="del">
	79	<syntax>account del <account id></syntax>
	80
	81	<description>
	82	<para>
	83	This commands deletes an account from your account list. You should signoff the account before deleting it.
	84	</para>
	85
	86
	87	<para>
	88	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.
	89	</para>
	90	</description>
	91	</bitlbee-command>
	92
	93	<bitlbee-command name="on">
	94	<syntax>account on [<account id>]</syntax>
	95
	96	<description>
	97	<para>
[75a4b85]	98	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.
[b7d3cc34]	99	</para>
	100
	101	<para>
	102	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.
	103	</para>
	104	</description>
	105
	106	</bitlbee-command>
	107
	108	<bitlbee-command name="off">
	109	<syntax>account off [<account id>]</syntax>
	110
	111	<description>
	112	<para>
[75a4b85]	113	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.
[b7d3cc34]	114	</para>
	115
	116	<para>
	117	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.
	118	</para>
	119	</description>
	120	</bitlbee-command>
	121
	122	<bitlbee-command name="list">
	123	<syntax>account list</syntax>
	124
	125	<description>
	126	<para>
	127	This command gives you a list of all the accounts known by BitlBee, including the numbers you'll need for most account commands.
	128	</para>
	129	</description>
	130	</bitlbee-command>
[75a4b85]	131
	132	<bitlbee-command name="set">
	133	<syntax>account set <account id></syntax>
	134	<syntax>account set <account id>/<setting></syntax>
	135	<syntax>account set <account id>/<setting> <value></syntax>
	136
	137	<description>
	138	<para>
	139	This account 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 set <account id></emphasis>.
	140	</para>
	141
	142	<para>
	143	For more infomation about a setting, see <emphasis>help set <setting></emphasis>.
	144	</para>
	145
	146	<para>
	147	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.
	148	</para>
	149	</description>
	150	</bitlbee-command>
[b7d3cc34]	151	</bitlbee-command>
	152
	153	<bitlbee-command name="add">
	154	<short-description>Add a buddy to your contact list</short-description>
	155	<syntax>add <connection> <handle> [<nick>]</syntax>
[ea3a26d]	156	<syntax>add -tmp <connection> <handle> [<nick>]</syntax>
[b7d3cc34]	157
	158	<description>
	159	<para>
	160	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.
	161	</para>
	162
	163	<para>
	164	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.
	165	</para>
[ea3a26d]	166
	167	<para>
[64d1f45]	168	Adding -tmp 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.
[ea3a26d]	169	</para>
[b7d3cc34]	170	</description>
	171
	172	<ircexample>
	173	<ircline nick="ctrlsoft">add 3 gryp@jabber.org grijp</ircline>
[689a6e0]	174	<ircaction nick="grijp" hostmask="gryp@jabber.org">has joined <emphasis>&bitlbee</emphasis></ircaction>
[b7d3cc34]	175	</ircexample>
	176	</bitlbee-command>
	177
	178	<bitlbee-command name="info">
	179	<short-description>Request user information</short-description>
	180	<syntax>info <connection> <handle></syntax>
	181	<syntax>info <nick></syntax>
	182
	183	<description>
	184	<para>
	185	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.
	186	</para>
	187	</description>
	188
	189	<ircexample>
	190	<ircline nick="ctrlsoft">info 0 72696705</ircline>
	191	<ircline nick="root">User info - UIN: 72696705 Nick: Lintux First/Last name: Wilmer van der Gaast E-mail: lintux@lintux.cx</ircline>
	192	</ircexample>
	193
	194	</bitlbee-command>
	195
	196	<bitlbee-command name="remove">
	197	<short-description>Remove a buddy from your contact list</short-description>
	198	<syntax>remove <nick></syntax>
	199
	200	<description>
	201	<para>
	202	Removes the specified nick from your buddy list.
	203	</para>
	204	</description>
	205
	206	<ircexample>
	207	<ircline nick="ctrlsoft">remove gryp</ircline>
	208	<ircaction nick="gryp" hostmask="gryp@jabber.jabber.org">has quit <emphasis>[Leaving...]</emphasis></ircaction>
	209	</ircexample>
	210
	211	</bitlbee-command>
	212
	213	<bitlbee-command name="block">
	214	<short-description>Block someone</short-description>
	215	<syntax>block <nick></syntax>
	216	<syntax>block <connection> <handle></syntax>
[9b8efab]	217	<syntax>block <connection></syntax>
[b7d3cc34]	218
	219	<description>
	220	<para>
	221	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.
	222	</para>
[9b8efab]	223
	224	<para>
	225	When called with only a connection specification as an argument, the command displays the current block list for that connection.
	226	</para>
[b7d3cc34]	227	</description>
	228	</bitlbee-command>
	229
	230	<bitlbee-command name="allow">
	231	<short-description>Unblock someone</short-description>
	232	<syntax>allow <nick></syntax>
	233	<syntax>allow <connection> <handle></syntax>
	234
	235	<description>
	236	<para>
	237	Reverse of block. Unignores the specified user or user handle on specified connection.
	238	</para>
[9b8efab]	239
	240	<para>
	241	When called with only a connection specification as an argument, the command displays the current allow list for that connection.
	242	</para>
[b7d3cc34]	243	</description>
	244	</bitlbee-command>
	245
	246	<bitlbee-command name="set">
	247	<short-description>Miscellaneous settings</short-description>
	248	<syntax>set [<variable> [<value>]]</syntax>
	249
	250	<description>
	251
	252	<para>
	253	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.
	254	</para>
	255
	256	<para>
	257	To get more help information about a setting, try:
	258	</para>
	259
	260	</description>
	261
	262	<ircexample>
	263	<ircline nick="ctrlsoft">help set private</ircline>
	264	</ircexample>
	265
	266	</bitlbee-command>
	267
	268	<bitlbee-command name="help">
	269	<short-description>BitlBee help system</short-description>
	270
	271	<syntax>help [subject]</syntax>
	272
	273	<description>
	274	<para>
	275	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.
	276	</para>
	277	</description>
	278	</bitlbee-command>
	279
	280	<bitlbee-command name="save">
	281	<short-description>Save your account data</short-description>
	282	<syntax>save</syntax>
	283
	284	<description>
	285	<para>
	286	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... ;-)
	287	</para>
	288	</description>
	289	</bitlbee-command>
	290
[89a1809]	291	<bitlbee-setting name="auto_connect" type="boolean" scope="both">
	292	<default>true</default>
[b7d3cc34]	293
	294	<description>
	295	<para>
[75a4b85]	296	With this option enabled, when you identify BitlBee will automatically connect to your accounts, with this disabled it will not do this.
[b7d3cc34]	297	</para>
[75a4b85]	298
[b7d3cc34]	299	<para>
[75a4b85]	300	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!)
[b7d3cc34]	301	</para>
	302	</description>
	303	</bitlbee-setting>
	304
[89a1809]	305	<bitlbee-setting name="auto_reconnect" type="boolean" scope="both">
	306	<default>false</default>
[b7d3cc34]	307
	308	<description>
	309	<para>
[75a4b85]	310	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.
[b7d3cc34]	311	</para>
	312
	313	<para>
[75a4b85]	314	See also the <emphasis>auto_reconnect_delay</emphasis> setting.
[b7d3cc34]	315	</para>
[75a4b85]	316
[89a1809]	317	<para>
	318	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!)
	319	</para>
	320	</description>
[b7d3cc34]	321	</bitlbee-setting>
	322
[89a1809]	323	<bitlbee-setting name="auto_reconnect_delay" type="integer" scope="global">
[75a4b85]	324	<default>300</default>
[b7d3cc34]	325
	326	<description>
	327	<para>
[75a4b85]	328	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.
	329	</para>
	330
	331	<para>
	332	See also the <emphasis>auto_reconnect</emphasis> setting.
[b7d3cc34]	333	</para>
	334	</description>
	335	</bitlbee-setting>
	336
[89a1809]	337	<bitlbee-setting name="away_devoice" type="boolean" scope="global">
	338	<default>true</default>
[b7d3cc34]	339
	340	<description>
	341	<para>
[75a4b85]	342	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.
[b7d3cc34]	343	</para>
	344	</description>
	345	</bitlbee-setting>
	346
[89a1809]	347	<bitlbee-setting name="buddy_sendbuffer" type="boolean" scope="global">
	348	<default>false</default>
[b7d3cc34]	349
	350	<description>
	351	<para>
[75a4b85]	352	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.
	353	</para>
	354
	355	<para>
	356	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.
	357	</para>
	358
	359	<para>
	360	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.
[b7d3cc34]	361	</para>
	362	</description>
	363	</bitlbee-setting>
	364
[89a1809]	365	<bitlbee-setting name="buddy_sendbuffer_delay" type="integer" scope="global">
[75a4b85]	366	<default>200</default>
[b7d3cc34]	367
	368	<description>
	369
	370	<para>
[75a4b85]	371	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.
[b7d3cc34]	372	</para>
	373
	374	<para>
[75a4b85]	375	See also the <emphasis>buddy_sendbuffer</emphasis> setting.
[b7d3cc34]	376	</para>
	377	</description>
	378	</bitlbee-setting>
	379
[89a1809]	380	<bitlbee-setting name="charset" type="string" scope="global">
[75a4b85]	381	<default>iso8859-1</default>
	382	<possible-values>you can get a list of all possible values by doing 'iconv -l' in a shell</possible-values>
[b7d3cc34]	383
	384	<description>
	385	<para>
[75a4b85]	386	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.
	387	</para>
	388
	389	<para>
	390	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
[b7d3cc34]	391	</para>
	392	</description>
[75a4b85]	393
[b7d3cc34]	394	</bitlbee-setting>
	395
[89a1809]	396	<bitlbee-setting name="debug" type="boolean" scope="global">
	397	<default>false</default>
[b7d3cc34]	398
	399	<description>
	400	<para>
[75a4b85]	401	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.
[b7d3cc34]	402	</para>
[75a4b85]	403	</description>
	404	</bitlbee-setting>
	405
[89a1809]	406	<bitlbee-setting name="default_target" type="string" scope="global">
[75a4b85]	407	<default>root</default>
	408	<possible-values>root, last</possible-values>
[b7d3cc34]	409
[75a4b85]	410	<description>
[b7d3cc34]	411	<para>
[75a4b85]	412	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>.
[b7d3cc34]	413	</para>
	414	</description>
	415	</bitlbee-setting>
	416
[89a1809]	417	<bitlbee-setting name="display_name" type="string" scope="account">
[b7d3cc34]	418	<description>
	419	<para>
[75a4b85]	420	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.
[b7d3cc34]	421	</para>
	422	</description>
	423	</bitlbee-setting>
	424
[89a1809]	425	<bitlbee-setting name="display_namechanges" type="boolean" scope="global">
	426	<default>false</default>
[75a4b85]	427
[2529faf]	428	<description>
	429	<para>
	430	With this option enabled, root will inform you when someone in your buddy list changes his/her "friendly name".
	431	</para>
	432	</description>
[75a4b85]	433	</bitlbee-setting>
	434
[89a1809]	435	<bitlbee-setting name="handle_unknown" type="string" scope="global">
[b7d3cc34]	436	<default>root</default>
	437	<possible-values>root, add, add_private, add_channel, ignore</possible-values>
	438
	439	<description>
	440	<para>
	441	Messages from unknown users are echoed like this by default:
	442	</para>
	443
	444	<ircexample>
	445	<ircline nick="root">Unknown message from handle 3137137:</ircline>
	446	<ircline nick="root">j0000! 1 4m l33t h4x0r! kill me!</ircline>
	447	</ircexample>
	448
	449	<para>
	450	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.
	451	</para>
	452
	453	<note>
	454	<para>
	455	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.
	456	</para>
	457	</note>
	458	</description>
	459
	460	</bitlbee-setting>
	461
[89a1809]	462	<bitlbee-setting name="lcnicks" type="boolean" scope="global">
	463	<default>true</default>
[b7d3cc34]	464
	465	<description>
	466	<para>
[75a4b85]	467	Hereby you can change whether you want all lower case nick names or leave the case as it intended by your peer.
[b7d3cc34]	468	</para>
	469	</description>
[75a4b85]	470
[b7d3cc34]	471	</bitlbee-setting>
	472
[89a1809]	473	<bitlbee-setting name="ops" type="string" scope="global">
[75a4b85]	474	<default>both</default>
	475	<possible-values>both, root, user, none</possible-values>
[b7d3cc34]	476
	477	<description>
	478	<para>
[75a4b85]	479	Some people prefer themself and root to have operator status in &bitlbee, other people don't. You can change these states using this setting.
[b7d3cc34]	480	</para>
	481
	482	<para>
[75a4b85]	483	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.
[b7d3cc34]	484	</para>
	485	</description>
	486	</bitlbee-setting>
	487
[89a1809]	488	<bitlbee-setting name="password" type="string" scope="both">
[b7d3cc34]	489	<description>
	490	<para>
[75a4b85]	491	Use this global setting to change your "NickServ" password.
[b7d3cc34]	492	</para>
[75a4b85]	493
[b7d3cc34]	494	<para>
[75a4b85]	495	This setting is also available for all IM accounts to change the password BitlBee uses to connect to the service.
	496	</para>
	497
	498	<para>
	499	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.
[b7d3cc34]	500	</para>
	501	</description>
	502	</bitlbee-setting>
[75a4b85]	503
[89a1809]	504	<bitlbee-setting name="port" type="integer" scope="account">
[b7d3cc34]	505	<description>
	506	<para>
[75a4b85]	507	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.
[b7d3cc34]	508	</para>
[75a4b85]	509	</description>
	510	</bitlbee-setting>
	511
[ee5c355]	512	<bitlbee-setting name="priority" type="integer" scope="account">
	513	<default>0</default>
	514
	515	<description>
	516	<para>
	517	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).
	518	</para>
	519
	520	<para>
	521	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).
	522	</para>
	523	</description>
	524	</bitlbee-setting>
	525
[89a1809]	526	<bitlbee-setting name="private" type="boolean" scope="global">
	527	<default>true</default>
[b7d3cc34]	528
[75a4b85]	529	<description>
[b7d3cc34]	530	<para>
[75a4b85]	531	If value is true, messages from users will appear in separate query windows. If false, messages from users will appear in the control channel.
[b7d3cc34]	532	</para>
	533
	534	<para>
[75a4b85]	535	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.
[b7d3cc34]	536	</para>
	537	</description>
	538	</bitlbee-setting>
	539
[89a1809]	540	<bitlbee-setting name="query_order" type="string" scope="global">
[75a4b85]	541	<default>lifo</default>
	542	<possible-values>lifo, fifo</possible-values>
[834ff44]	543
[b7d3cc34]	544	<description>
	545	<para>
[75a4b85]	546	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.
[b7d3cc34]	547	</para>
	548
	549	<para>
[75a4b85]	550	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).
[b7d3cc34]	551	</para>
	552	</description>
[75a4b85]	553	</bitlbee-setting>
[b7d3cc34]	554
[89a1809]	555	<bitlbee-setting name="resource" type="string" scope="account">
[75a4b85]	556	<default>BitlBee</default>
	557
	558	<description>
	559	<para>
	560	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.
	561	</para>
	562	</description>
[b7d3cc34]	563	</bitlbee-setting>
	564
[ee5c355]	565	<bitlbee-setting name="resource_select" type="string" scope="account">
	566	<default>priority</default>
	567	<possible-values>priority, time</possible-values>
	568
	569	<description>
	570	<para>
	571	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.
	572	</para>
	573
	574	<para>
	575	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>time</emphasis>, messages will be delivered to the resource that was last used to send you a message (or the resource that most recently connected).
	576	</para>
	577	</description>
	578	</bitlbee-setting>
	579
[89a1809]	580	<bitlbee-setting name="save_on_quit" type="boolean" scope="global">
	581	<default>true</default>
[b7d3cc34]	582
	583	<description>
	584	<para>
[75a4b85]	585	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.
[b7d3cc34]	586	</para>
	587	</description>
[75a4b85]	588	</bitlbee-setting>
[b7d3cc34]	589
[89a1809]	590	<bitlbee-setting name="server" type="string" scope="account">
[75a4b85]	591	<description>
	592	<para>
	593	Can be set for Jabber- and OSCAR-connections. For OSCAR, this must be set to <emphasis>login.icq.com</emphasis> if it's an ICQ connection, or <emphasis>login.oscar.aol.com</emphasis> if it's an AIM connection. For Jabber, you have to set this if the servername isn't equal to the part after the @ in the Jabber handle.
	594	</para>
	595	</description>
[b7d3cc34]	596	</bitlbee-setting>
	597
[89a1809]	598	<bitlbee-setting name="ssl" type="boolean" scope="account">
	599	<default>false</default>
[b7d3cc34]	600
[75a4b85]	601	<description>
	602	<para>
	603	Currently only available for Jabber connections. Set this to true if the server accepts SSL connections.
	604	</para>
	605	</description>
[b7d3cc34]	606	</bitlbee-setting>
	607
[89a1809]	608	<bitlbee-setting name="strip_html" type="boolean" scope="global">
	609	<default>true</default>
[75a4b85]	610
[b7d3cc34]	611	<description>
	612	<para>
[75a4b85]	613	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.
	614	</para>
	615	<para>
	616	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.
[b7d3cc34]	617	</para>
	618	</description>
	619	</bitlbee-setting>
	620
[ee5c355]	621	<bitlbee-setting name="tls" type="boolean" scope="account">
	622	<default>try</default>
	623
	624	<description>
	625	<para>
	626	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.
	627	</para>
	628
	629	<para>
	630	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.
	631	</para>
	632	</description>
	633	</bitlbee-setting>
	634
[89a1809]	635	<bitlbee-setting name="to_char" type="string" scope="global">
[75a4b85]	636	<default>": "</default>
[b7d3cc34]	637
	638	<description>
	639	<para>
[75a4b85]	640	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>.
[b7d3cc34]	641	</para>
	642
	643	<para>
[75a4b85]	644	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.
[b7d3cc34]	645	</para>
	646	</description>
	647	</bitlbee-setting>
	648
[89a1809]	649	<bitlbee-setting name="typing_notice" type="boolean" scope="global">
	650	<default>false</default>
[b7d3cc34]	651
	652	<description>
	653	<para>
[75a4b85]	654	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. ;-)
[b7d3cc34]	655	</para>
	656	</description>
	657	</bitlbee-setting>
	658
[846cec61]	659	<bitlbee-setting name="web_aware" type="string" scope="account">
	660	<default>false</default>
	661
	662	<description>
	663	<para>
	664	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.
	665	</para>
	666
	667	<para>
	668	Unless you really intend to use this feature somewhere (on forums or maybe a website), it's probably better to keep this setting disabled.
	669	</para>
	670	</description>
	671	</bitlbee-setting>
	672
[b7d3cc34]	673	<bitlbee-command name="rename">
	674	<short-description>Rename (renick) a buddy</short-description>
	675	<syntax>rename <oldnick> <newnick></syntax>
	676
	677	<description>
	678	<para>
	679	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).
	680	</para>
	681	</description>
	682
	683	<ircexample>
	684	<ircline nick="itsme">rename itsme_ you</ircline>
	685	<ircaction nick="itsme_">is now known as <emphasis>you</emphasis></ircaction>
	686	</ircexample>
	687
	688	</bitlbee-command>
	689
	690	<bitlbee-command name="yes">
	691	<short-description>Accept a request</short-description>
	692	<syntax>yes [<number>]</syntax>
	693
	694	<description>
	695	<para>
	696	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.
	697	</para>
	698
	699	<para>
	700	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.
	701	</para>
	702	</description>
	703
	704	</bitlbee-command>
	705
	706	<bitlbee-command name="no">
	707	<short-description>Deny a request</short-description>
	708	<syntax>no [<number>]</syntax>
	709
	710	<description>
	711	<para>
	712	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.
	713	</para>
	714
	715	<para>
	716	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.
	717	</para>
	718	</description>
	719	</bitlbee-command>
	720
	721	<bitlbee-command name="qlist">
	722	<short-description>List all the unanswered questions root asked</short-description>
	723	<syntax>qlist</syntax>
	724
	725	<description>
	726	<para>
	727	This gives you a list of all the unanswered questions from root.
	728	</para>
	729	</description>
	730
	731	</bitlbee-command>
	732
	733	<bitlbee-command name="register">
	734	<short-description>Register yourself</short-description>
	735	<syntax>register <password></syntax>
	736
	737	<description>
	738	<para>
	739	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.
	740	</para>
	741
	742	<para>
	743	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.. ;-)
	744	</para>
	745
	746	<para>
[1be54a9]	747	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.
[b7d3cc34]	748	</para>
	749	</description>
	750
	751	</bitlbee-command>
	752
	753	<bitlbee-command name="identify">
	754	<syntax>identify <password></syntax>
	755	<short-description>Identify yourself with your password</short-description>
	756
	757	<description>
	758	<para>
	759	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.
	760	</para>
	761
	762	<para>
	763	Once you're registered, you can change your password using <emphasis>set password <password></emphasis>.
	764	</para>
	765	</description>
	766	</bitlbee-command>
	767
	768	<bitlbee-command name="drop">
	769	<syntax>drop <password></syntax>
	770	<short-description>Drop your account</short-description>
	771
	772	<description>
	773	<para>
	774	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.
	775	</para>
	776	</description>
	777	</bitlbee-command>
	778
	779	<bitlbee-command name="blist">
	780	<syntax>blist [all\|online\|offline\|away]</syntax>
	781	<short-description>List all the buddies in your contact list</short-description>
	782
	783	<description>
	784	<para>
	785	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.
	786	</para>
	787	</description>
	788
	789	</bitlbee-command>
	790
	791	<bitlbee-command name="nick">
	792	<short-description>Change friendly name, nick</short-description>
	793	<syntax>nick <connection> [<new nick>]</syntax>
	794	<syntax>nick</syntax>
	795
	796	<description>
	797	<para>
	798	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.
	799	</para>
[0aaca60]	800
	801	<para>
	802	It is recommended to use the per-account <emphasis>display_name</emphasis> setting to read and change this information. The <emphasis>nick</emphasis> command is deprecated.
	803	</para>
[b7d3cc34]	804	</description>
	805
	806	<ircexample>
	807	<ircline nick="wouter">nick 1 "Wouter Paesen"</ircline>
	808	<ircline nick="root">Setting your name on connection 1 to `Wouter Paesen'</ircline>
	809	</ircexample>
	810
	811	</bitlbee-command>
	812
	813	<bitlbee-command name="import_buddies">
	814	<short-description>Copy local buddy list to server (normally only needed when upgrading)</short-description>
	815	<syntax>import_buddies <connection> [clear]</syntax>
	816
	817	<description>
	818	<para>
	819	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.
	820	</para>
	821
	822	<para>
	823	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.
	824	</para>
	825
	826	<para>
	827	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.
	828	</para>
	829
	830	<para>
	831	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.
	832	</para>
	833	</description>
	834
	835	</bitlbee-command>
	836	</chapter>

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

Download in other formats: