Context Navigation

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

Last change on this file since fd9fa52 was 903a2fc, checked in by Sven Moritz Hallberg <sm@…>, at 2008-02-16T16:24:38Z
remove (broken) 'otr forget key' command again
Property mode set to `100644`
File size: 41.2 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">
[30ce1ce]	19	<syntax>account add <protocol> <username> <password></syntax>
[b7d3cc34]	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">
[30ce1ce]	28	<syntax>account add jabber <handle@server.tld> <password></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">
[30ce1ce]	52	<syntax>account add oscar <handle> <password></syntax>
[b7d3cc34]	53
	54	<description>
	55	<para>
[30ce1ce]	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.
[b7d3cc34]	57	</para>
	58	</description>
	59
	60	<ircexample>
[30ce1ce]	61	<ircline nick="wilmer">account add oscar 72696705 hobbelmeeuw</ircline>
[b7d3cc34]	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>
[cd428e4]	136	<syntax>account set -del <account id>/<setting></syntax>
[75a4b85]	137
	138	<description>
	139	<para>
	140	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>.
	141	</para>
	142
	143	<para>
[cd428e4]	144	For more infomation about a setting, see <emphasis>help set <setting></emphasis>. For details about the syntax of this command, see <emphasis>help set</emphasis>.
[75a4b85]	145	</para>
	146
	147	<para>
	148	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.
	149	</para>
	150	</description>
	151	</bitlbee-command>
[b7d3cc34]	152	</bitlbee-command>
	153
	154	<bitlbee-command name="add">
	155	<short-description>Add a buddy to your contact list</short-description>
	156	<syntax>add <connection> <handle> [<nick>]</syntax>
[ea3a26d]	157	<syntax>add -tmp <connection> <handle> [<nick>]</syntax>
[b7d3cc34]	158
	159	<description>
	160	<para>
	161	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.
	162	</para>
	163
	164	<para>
	165	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.
	166	</para>
[ea3a26d]	167
	168	<para>
[64d1f45]	169	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]	170	</para>
[b7d3cc34]	171	</description>
	172
	173	<ircexample>
	174	<ircline nick="ctrlsoft">add 3 gryp@jabber.org grijp</ircline>
[689a6e0]	175	<ircaction nick="grijp" hostmask="gryp@jabber.org">has joined <emphasis>&bitlbee</emphasis></ircaction>
[b7d3cc34]	176	</ircexample>
	177	</bitlbee-command>
	178
	179	<bitlbee-command name="info">
	180	<short-description>Request user information</short-description>
	181	<syntax>info <connection> <handle></syntax>
	182	<syntax>info <nick></syntax>
	183
	184	<description>
	185	<para>
	186	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.
	187	</para>
	188	</description>
	189
	190	<ircexample>
	191	<ircline nick="ctrlsoft">info 0 72696705</ircline>
	192	<ircline nick="root">User info - UIN: 72696705 Nick: Lintux First/Last name: Wilmer van der Gaast E-mail: lintux@lintux.cx</ircline>
	193	</ircexample>
	194
	195	</bitlbee-command>
	196
	197	<bitlbee-command name="remove">
	198	<short-description>Remove a buddy from your contact list</short-description>
	199	<syntax>remove <nick></syntax>
	200
	201	<description>
	202	<para>
	203	Removes the specified nick from your buddy list.
	204	</para>
	205	</description>
	206
	207	<ircexample>
	208	<ircline nick="ctrlsoft">remove gryp</ircline>
	209	<ircaction nick="gryp" hostmask="gryp@jabber.jabber.org">has quit <emphasis>[Leaving...]</emphasis></ircaction>
	210	</ircexample>
	211
	212	</bitlbee-command>
	213
	214	<bitlbee-command name="block">
	215	<short-description>Block someone</short-description>
	216	<syntax>block <nick></syntax>
	217	<syntax>block <connection> <handle></syntax>
[9b8efab]	218	<syntax>block <connection></syntax>
[b7d3cc34]	219
	220	<description>
	221	<para>
	222	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.
	223	</para>
[9b8efab]	224
	225	<para>
	226	When called with only a connection specification as an argument, the command displays the current block list for that connection.
	227	</para>
[b7d3cc34]	228	</description>
	229	</bitlbee-command>
	230
	231	<bitlbee-command name="allow">
	232	<short-description>Unblock someone</short-description>
	233	<syntax>allow <nick></syntax>
	234	<syntax>allow <connection> <handle></syntax>
	235
	236	<description>
	237	<para>
	238	Reverse of block. Unignores the specified user or user handle on specified connection.
	239	</para>
[9b8efab]	240
	241	<para>
	242	When called with only a connection specification as an argument, the command displays the current allow list for that connection.
	243	</para>
[b7d3cc34]	244	</description>
	245	</bitlbee-command>
[f5ac0fb]	246
	247	<bitlbee-command name="otr">
	248	<short-description>Off-the-Record encryption control</short-description>
	249	<syntax>otr <subcommand> [<arguments>]</syntax>
	250
	251	<description>
	252
	253	<para>
	254	Available subcommands: connect, disconnect, smp, trust, info, keygen, and forget. See <emphasis>help otr <subcommand></emphasis> for more information.
	255	</para>
	256
	257	</description>
	258
	259	<bitlbee-command name="connect">
	260	<syntax>otr connect <nick></syntax>
	261
	262	<description>
	263
	264	<para>
	265	Attempts to establish an encrypted connection with the specified user by sending a magic string.
	266	</para>
	267
	268	</description>
	269
	270	</bitlbee-command>
	271
	272	<bitlbee-command name="disconnect">
	273	<syntax>otr disconnect <nick></syntax>
	274
	275	<description>
	276
	277	<para>
	278	Resets the connection with the specified user to cleartext.
	279	</para>
	280
	281	</description>
	282
	283	</bitlbee-command>
	284
	285	<bitlbee-command name="smp">
	286	<syntax>otr smp <nick> <secret></syntax>
	287
	288	<description>
	289
	290	<para>
	291	Attempts to authenticate the given user's active fingerprint via the Socialist Millionaires' Protocol.
	292	</para>
	293
	294	<para>
	295	If an SMP challenge has already been received from the given user, responds with the specified secret. Otherwise, a challenge for the secret will be sent. If the protocol succeeds (i.e. both parties gave the same secret), the fingerprint will be trusted.
	296	</para>
	297
	298	</description>
	299
	300	</bitlbee-command>
	301
	302	<bitlbee-command name="trust">
	303	<syntax>otr trust <nick> <fp1> <fp2> <fp3> <fp4> <fp5></syntax>
	304
	305	<description>
	306
	307	<para>
	308	Manually affirms trust in the specified fingerprint, given as five blocks of precisely eight (hexadecimal) digits each.
	309	</para>
	310
	311	</description>
	312
	313	</bitlbee-command>
	314
	315	<bitlbee-command name="info">
	316	<syntax>otr info</syntax>
	317	<syntax>otr info <nick></syntax>
	318
	319	<description>
	320
	321	<para>
	322	Shows information about the OTR state. The first form lists our private keys and current OTR contexts. The second form displays information about the connection with a given user, including the list of their known fingerprints.
	323	</para>
	324
	325	</description>
	326
	327	</bitlbee-command>
	328
	329	<bitlbee-command name="keygen">
	330	<syntax>otr keygen <account-no></syntax>
	331
	332	<description>
	333
	334	<para>
	335	Generates a new OTR private key for the given account.
	336	</para>
	337
	338	</description>
	339
	340	</bitlbee-command>
	341
	342	<bitlbee-command name="forget">
	343	<syntax>otr forget <thing> <arguments></syntax>
	344
	345	<description>
	346
	347	<para>
[903a2fc]	348	Forgets some part of our OTR userstate. Available things: fingerprint and context. See <emphasis>help otr forget <thing></emphasis> for more information.
[f5ac0fb]	349	</para>
	350
	351	</description>
	352
	353	<bitlbee-command name="fingerprint">
	354	<syntax>otr forget fingerprint <nick> <fingerprint></syntax>
	355
	356	<description>
	357
	358	<para>
	359	Drops the specified fingerprint from the given user's OTR connection context. It is allowed to specify only a (unique) prefix of the desired fingerprint.
	360	</para>
	361
	362	</description>
	363
	364	</bitlbee-command>
	365
	366	<bitlbee-command name="context">
	367	<syntax>otr forget context <nick></syntax>
	368
	369	<description>
	370
	371	<para>
	372	Forgets the entire OTR context associated with the given user. This includes current message and protocol states, as well as any fingerprints for that user.
	373	</para>
	374
	375	</description>
	376
	377	</bitlbee-command>
	378
	379	</bitlbee-command>
	380
	381	</bitlbee-command>
[b7d3cc34]	382
	383	<bitlbee-command name="set">
	384	<short-description>Miscellaneous settings</short-description>
[cd428e4]	385	<syntax>set</syntax>
	386	<syntax>set <variable></syntax>
	387	<syntax>set <variable> <value></syntax>
	388	<syntax>set -del <variable></syntax>
[b7d3cc34]	389
	390	<description>
	391
	392	<para>
[cd428e4]	393	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.
[b7d3cc34]	394	</para>
	395
	396	<para>
	397	To get more help information about a setting, try:
	398	</para>
	399
	400	</description>
	401
	402	<ircexample>
	403	<ircline nick="ctrlsoft">help set private</ircline>
	404	</ircexample>
	405
	406	</bitlbee-command>
	407
	408	<bitlbee-command name="help">
	409	<short-description>BitlBee help system</short-description>
	410
	411	<syntax>help [subject]</syntax>
	412
	413	<description>
	414	<para>
	415	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.
	416	</para>
	417	</description>
	418	</bitlbee-command>
	419
	420	<bitlbee-command name="save">
	421	<short-description>Save your account data</short-description>
	422	<syntax>save</syntax>
	423
	424	<description>
	425	<para>
	426	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... ;-)
	427	</para>
	428	</description>
	429	</bitlbee-command>
	430
[89a1809]	431	<bitlbee-setting name="auto_connect" type="boolean" scope="both">
	432	<default>true</default>
[b7d3cc34]	433
	434	<description>
	435	<para>
[75a4b85]	436	With this option enabled, when you identify BitlBee will automatically connect to your accounts, with this disabled it will not do this.
[b7d3cc34]	437	</para>
[75a4b85]	438
[b7d3cc34]	439	<para>
[75a4b85]	440	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]	441	</para>
	442	</description>
	443	</bitlbee-setting>
	444
[89a1809]	445	<bitlbee-setting name="auto_reconnect" type="boolean" scope="both">
	446	<default>false</default>
[b7d3cc34]	447
	448	<description>
	449	<para>
[75a4b85]	450	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]	451	</para>
	452
	453	<para>
[75a4b85]	454	See also the <emphasis>auto_reconnect_delay</emphasis> setting.
[b7d3cc34]	455	</para>
[75a4b85]	456
[89a1809]	457	<para>
	458	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!)
	459	</para>
	460	</description>
[b7d3cc34]	461	</bitlbee-setting>
	462
[89a1809]	463	<bitlbee-setting name="auto_reconnect_delay" type="integer" scope="global">
[75a4b85]	464	<default>300</default>
[b7d3cc34]	465
	466	<description>
	467	<para>
[75a4b85]	468	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.
	469	</para>
	470
	471	<para>
	472	See also the <emphasis>auto_reconnect</emphasis> setting.
[b7d3cc34]	473	</para>
	474	</description>
	475	</bitlbee-setting>
	476
[89a1809]	477	<bitlbee-setting name="away_devoice" type="boolean" scope="global">
	478	<default>true</default>
[b7d3cc34]	479
	480	<description>
	481	<para>
[75a4b85]	482	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]	483	</para>
	484	</description>
	485	</bitlbee-setting>
	486
[89a1809]	487	<bitlbee-setting name="buddy_sendbuffer" type="boolean" scope="global">
	488	<default>false</default>
[b7d3cc34]	489
	490	<description>
	491	<para>
[75a4b85]	492	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.
	493	</para>
	494
	495	<para>
	496	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.
	497	</para>
	498
	499	<para>
	500	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]	501	</para>
	502	</description>
	503	</bitlbee-setting>
	504
[89a1809]	505	<bitlbee-setting name="buddy_sendbuffer_delay" type="integer" scope="global">
[75a4b85]	506	<default>200</default>
[b7d3cc34]	507
	508	<description>
	509
	510	<para>
[75a4b85]	511	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]	512	</para>
	513
	514	<para>
[75a4b85]	515	See also the <emphasis>buddy_sendbuffer</emphasis> setting.
[b7d3cc34]	516	</para>
	517	</description>
	518	</bitlbee-setting>
	519
[89a1809]	520	<bitlbee-setting name="charset" type="string" scope="global">
[75a4b85]	521	<default>iso8859-1</default>
	522	<possible-values>you can get a list of all possible values by doing 'iconv -l' in a shell</possible-values>
[b7d3cc34]	523
	524	<description>
	525	<para>
[75a4b85]	526	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.
	527	</para>
	528
	529	<para>
	530	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]	531	</para>
	532	</description>
[75a4b85]	533
[b7d3cc34]	534	</bitlbee-setting>
	535
[1c18ce1]	536	<bitlbee-setting name="color_encrypted" type="boolean" scope="global">
	537	<default>true</default>
	538
	539	<description>
	540	<para>
	541	If set to true, BitlBee will color incoming encrypted messages according to their fingerprint trust level: untrusted=red, trusted=green.
	542	</para>
	543	</description>
	544
	545	</bitlbee-setting>
	546
[89a1809]	547	<bitlbee-setting name="debug" type="boolean" scope="global">
	548	<default>false</default>
[b7d3cc34]	549
	550	<description>
	551	<para>
[75a4b85]	552	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]	553	</para>
[75a4b85]	554	</description>
	555	</bitlbee-setting>
	556
[89a1809]	557	<bitlbee-setting name="default_target" type="string" scope="global">
[75a4b85]	558	<default>root</default>
	559	<possible-values>root, last</possible-values>
[b7d3cc34]	560
[75a4b85]	561	<description>
[b7d3cc34]	562	<para>
[75a4b85]	563	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]	564	</para>
	565	</description>
	566	</bitlbee-setting>
	567
[89a1809]	568	<bitlbee-setting name="display_name" type="string" scope="account">
[b7d3cc34]	569	<description>
	570	<para>
[75a4b85]	571	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]	572	</para>
	573	</description>
	574	</bitlbee-setting>
	575
[89a1809]	576	<bitlbee-setting name="display_namechanges" type="boolean" scope="global">
	577	<default>false</default>
[75a4b85]	578
[2529faf]	579	<description>
	580	<para>
	581	With this option enabled, root will inform you when someone in your buddy list changes his/her "friendly name".
	582	</para>
	583	</description>
[75a4b85]	584	</bitlbee-setting>
	585
[89a1809]	586	<bitlbee-setting name="handle_unknown" type="string" scope="global">
[b7d3cc34]	587	<default>root</default>
	588	<possible-values>root, add, add_private, add_channel, ignore</possible-values>
	589
	590	<description>
	591	<para>
	592	Messages from unknown users are echoed like this by default:
	593	</para>
	594
	595	<ircexample>
	596	<ircline nick="root">Unknown message from handle 3137137:</ircline>
	597	<ircline nick="root">j0000! 1 4m l33t h4x0r! kill me!</ircline>
	598	</ircexample>
	599
	600	<para>
	601	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.
	602	</para>
	603
	604	<note>
	605	<para>
	606	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.
	607	</para>
	608	</note>
	609	</description>
	610
	611	</bitlbee-setting>
	612
[1c18ce1]	613	<bitlbee-setting name="halfop_buddies" type="string" scope="global">
	614	<default>encrypted</default>
	615	<possible-values>encrypted, trusted, notaway, false</possible-values>
	616
	617	<description>
	618	<para>
	619	Specifies under which circumstances BitlBee should give the "halfop" mode flag (+h) to buddies.
	620	</para>
	621
	622	<para>
	623	If "false", the flag is never set. On "notaway", the flag is removed for users marked as "away" and set for all others. On "encrypted", the flag is set for users with whom we have an encrypted connection. On "trusted", it is set only for encrypted connections using a trusted key.
	624	</para>
	625	</description>
	626
	627	</bitlbee-setting>
	628
[89a1809]	629	<bitlbee-setting name="lcnicks" type="boolean" scope="global">
	630	<default>true</default>
[b7d3cc34]	631
	632	<description>
	633	<para>
[75a4b85]	634	Hereby you can change whether you want all lower case nick names or leave the case as it intended by your peer.
[b7d3cc34]	635	</para>
	636	</description>
[75a4b85]	637
[b7d3cc34]	638	</bitlbee-setting>
	639
[1febf5c]	640	<bitlbee-setting name="mail_notifications" type="boolean" scope="account">
	641	<default>false</default>
	642
	643	<description>
	644	<para>
	645	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.
	646	</para>
	647	</description>
	648
	649	</bitlbee-setting>
	650
[1c18ce1]	651	<bitlbee-setting name="op_buddies" type="string" scope="global">
	652	<default>trusted</default>
	653	<possible-values>encrypted, trusted, notaway, false</possible-values>
[b7d3cc34]	654
	655	<description>
	656	<para>
[1c18ce1]	657	Specifies under which circumstances BitlBee should give the "op" mode flag (+o) to buddies.
	658	</para>
	659
	660	<para>
	661	If "false", the flag is never set. On "notaway", the flag is removed for users marked as "away" and set for all others. On "encrypted", the flag is set for users with whom we have an encrypted connection. On "trusted", it is set only for encrypted connections using a trusted key.
[b7d3cc34]	662	</para>
[1c18ce1]	663	</description>
	664
	665	</bitlbee-setting>
[b7d3cc34]	666
[1c18ce1]	667	<bitlbee-setting name="op_root" type="bool" scope="global">
	668	<default>true</default>
	669
	670	<description>
[b7d3cc34]	671	<para>
[1c18ce1]	672	Some people prefer themself and root to have operator status in &bitlbee, other people don't. You can set the desired state for root using this setting.
	673	</para>
	674	</description>
	675	</bitlbee-setting>
	676
	677	<bitlbee-setting name="op_user" type="bool" scope="global">
	678	<default>true</default>
	679
	680	<description>
	681	<para>
	682	Some people prefer themself and root to have operator status in &bitlbee, other people don't. You can set the desired state for yourself using this setting.
	683	</para>
	684	</description>
	685	</bitlbee-setting>
	686
	687	<bitlbee-setting name="otr_policy" type="string" scope="global">
	688	<default>opportunistic</default>
	689	<possible-values>never, opportunistic, manual, always</possible-values>
	690
	691	<description>
	692	<para>
	693	This setting controls the policy for establishing Off-the-Record connections.
	694	</para>
	695	<para>
	696	A value of "never" effectively disables the OTR subsystem. In "opportunistic" mode, a magic whitespace pattern will be appended to the first message sent to any user. If the peer is also running opportunistic OTR, an encrypted connection will be set up automatically. On "manual", on the other hand, OTR connections must be established explicitly using <emphasis>otr connect</emphasis>. Finally, the setting "always" enforces encrypted communication by causing BitlBee to refuse to send any cleartext messages at all.
[b7d3cc34]	697	</para>
	698	</description>
	699	</bitlbee-setting>
	700
[89a1809]	701	<bitlbee-setting name="password" type="string" scope="both">
[b7d3cc34]	702	<description>
	703	<para>
[75a4b85]	704	Use this global setting to change your "NickServ" password.
[b7d3cc34]	705	</para>
[75a4b85]	706
[b7d3cc34]	707	<para>
[75a4b85]	708	This setting is also available for all IM accounts to change the password BitlBee uses to connect to the service.
	709	</para>
	710
	711	<para>
	712	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]	713	</para>
	714	</description>
	715	</bitlbee-setting>
[75a4b85]	716
[89a1809]	717	<bitlbee-setting name="port" type="integer" scope="account">
[b7d3cc34]	718	<description>
	719	<para>
[75a4b85]	720	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]	721	</para>
[75a4b85]	722	</description>
	723	</bitlbee-setting>
	724
[ee5c355]	725	<bitlbee-setting name="priority" type="integer" scope="account">
	726	<default>0</default>
	727
	728	<description>
	729	<para>
	730	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).
	731	</para>
	732
	733	<para>
	734	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).
	735	</para>
	736	</description>
	737	</bitlbee-setting>
	738
[89a1809]	739	<bitlbee-setting name="private" type="boolean" scope="global">
	740	<default>true</default>
[b7d3cc34]	741
[75a4b85]	742	<description>
[b7d3cc34]	743	<para>
[75a4b85]	744	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]	745	</para>
	746
	747	<para>
[75a4b85]	748	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]	749	</para>
	750	</description>
	751	</bitlbee-setting>
	752
[89a1809]	753	<bitlbee-setting name="query_order" type="string" scope="global">
[75a4b85]	754	<default>lifo</default>
	755	<possible-values>lifo, fifo</possible-values>
[834ff44]	756
[b7d3cc34]	757	<description>
	758	<para>
[75a4b85]	759	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]	760	</para>
	761
	762	<para>
[75a4b85]	763	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]	764	</para>
	765	</description>
[75a4b85]	766	</bitlbee-setting>
[b7d3cc34]	767
[89a1809]	768	<bitlbee-setting name="resource" type="string" scope="account">
[75a4b85]	769	<default>BitlBee</default>
	770
	771	<description>
	772	<para>
	773	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.
	774	</para>
	775	</description>
[b7d3cc34]	776	</bitlbee-setting>
	777
[ee5c355]	778	<bitlbee-setting name="resource_select" type="string" scope="account">
	779	<default>priority</default>
	780	<possible-values>priority, time</possible-values>
	781
	782	<description>
	783	<para>
	784	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.
	785	</para>
	786
	787	<para>
	788	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).
	789	</para>
	790	</description>
	791	</bitlbee-setting>
	792
[89a1809]	793	<bitlbee-setting name="save_on_quit" type="boolean" scope="global">
	794	<default>true</default>
[b7d3cc34]	795
	796	<description>
	797	<para>
[75a4b85]	798	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]	799	</para>
	800	</description>
[75a4b85]	801	</bitlbee-setting>
[b7d3cc34]	802
[89a1809]	803	<bitlbee-setting name="server" type="string" scope="account">
[75a4b85]	804	<description>
	805	<para>
[30ce1ce]	806	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.
[75a4b85]	807	</para>
	808	</description>
[b7d3cc34]	809	</bitlbee-setting>
[1186382]	810
	811	<bitlbee-setting name="simulate_netsplit" type="boolean" scope="global">
	812	<default>true</default>
	813
	814	<description>
	815	<para>
	816	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.
	817	</para>
	818	</description>
	819	</bitlbee-setting>
[b7d3cc34]	820
[89a1809]	821	<bitlbee-setting name="ssl" type="boolean" scope="account">
	822	<default>false</default>
[b7d3cc34]	823
[75a4b85]	824	<description>
	825	<para>
	826	Currently only available for Jabber connections. Set this to true if the server accepts SSL connections.
	827	</para>
	828	</description>
[b7d3cc34]	829	</bitlbee-setting>
	830
[89a1809]	831	<bitlbee-setting name="strip_html" type="boolean" scope="global">
	832	<default>true</default>
[75a4b85]	833
[b7d3cc34]	834	<description>
	835	<para>
[75a4b85]	836	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.
	837	</para>
	838	<para>
	839	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]	840	</para>
	841	</description>
	842	</bitlbee-setting>
	843
[ee5c355]	844	<bitlbee-setting name="tls" type="boolean" scope="account">
	845	<default>try</default>
	846
	847	<description>
	848	<para>
	849	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.
	850	</para>
	851
	852	<para>
	853	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.
	854	</para>
	855	</description>
	856	</bitlbee-setting>
	857
[89a1809]	858	<bitlbee-setting name="to_char" type="string" scope="global">
[75a4b85]	859	<default>": "</default>
[b7d3cc34]	860
	861	<description>
	862	<para>
[75a4b85]	863	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]	864	</para>
	865
	866	<para>
[75a4b85]	867	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]	868	</para>
	869	</description>
	870	</bitlbee-setting>
	871
[89a1809]	872	<bitlbee-setting name="typing_notice" type="boolean" scope="global">
	873	<default>false</default>
[b7d3cc34]	874
	875	<description>
	876	<para>
[75a4b85]	877	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]	878	</para>
	879	</description>
	880	</bitlbee-setting>
	881
[1c18ce1]	882	<bitlbee-setting name="voice_buddies" type="string" scope="global">
	883	<default>trusted</default>
	884	<possible-values>encrypted, trusted, notaway, false</possible-values>
	885
	886	<description>
	887	<para>
	888	Specifies under which circumstances BitlBee should give the "voice" mode flag (+v) to buddies.
	889	</para>
	890
	891	<para>
	892	If "false", the flag is never set. On "notaway", the flag is removed for users marked as "away" and set for all others. On "encrypted", the flag is set for users with whom we have an encrypted connection. On "trusted", it is set only for encrypted connections using a trusted key.
	893	</para>
	894	</description>
	895
	896	</bitlbee-setting>
	897
[846cec61]	898	<bitlbee-setting name="web_aware" type="string" scope="account">
	899	<default>false</default>
	900
	901	<description>
	902	<para>
	903	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.
	904	</para>
	905
	906	<para>
	907	Unless you really intend to use this feature somewhere (on forums or maybe a website), it's probably better to keep this setting disabled.
	908	</para>
	909	</description>
	910	</bitlbee-setting>
	911
[a6df0b5]	912	<bitlbee-setting name="xmlconsole" type="boolean" scope="account">
	913	<default>false</default>
	914
	915	<description>
	916	<para>
	917	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.
	918	</para>
	919	<para>
	920	If you want to enable this XML console permanently (and at login time already), you can set this setting.
	921	</para>
	922	</description>
	923	</bitlbee-setting>
	924
[b7d3cc34]	925	<bitlbee-command name="rename">
	926	<short-description>Rename (renick) a buddy</short-description>
	927	<syntax>rename <oldnick> <newnick></syntax>
	928
	929	<description>
	930	<para>
	931	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).
	932	</para>
	933	</description>
	934
	935	<ircexample>
	936	<ircline nick="itsme">rename itsme_ you</ircline>
	937	<ircaction nick="itsme_">is now known as <emphasis>you</emphasis></ircaction>
	938	</ircexample>
	939
	940	</bitlbee-command>
	941
	942	<bitlbee-command name="yes">
	943	<short-description>Accept a request</short-description>
	944	<syntax>yes [<number>]</syntax>
	945
	946	<description>
	947	<para>
	948	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.
	949	</para>
	950
	951	<para>
	952	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.
	953	</para>
	954	</description>
	955
	956	</bitlbee-command>
	957
	958	<bitlbee-command name="no">
	959	<short-description>Deny a request</short-description>
	960	<syntax>no [<number>]</syntax>
	961
	962	<description>
	963	<para>
	964	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.
	965	</para>
	966
	967	<para>
	968	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.
	969	</para>
	970	</description>
	971	</bitlbee-command>
	972
	973	<bitlbee-command name="qlist">
	974	<short-description>List all the unanswered questions root asked</short-description>
	975	<syntax>qlist</syntax>
	976
	977	<description>
	978	<para>
	979	This gives you a list of all the unanswered questions from root.
	980	</para>
	981	</description>
	982
	983	</bitlbee-command>
	984
	985	<bitlbee-command name="register">
	986	<short-description>Register yourself</short-description>
	987	<syntax>register <password></syntax>
	988
	989	<description>
	990	<para>
	991	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.
	992	</para>
	993
	994	<para>
	995	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.. ;-)
	996	</para>
	997
	998	<para>
[1be54a9]	999	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]	1000	</para>
	1001	</description>
	1002
	1003	</bitlbee-command>
	1004
	1005	<bitlbee-command name="identify">
	1006	<syntax>identify <password></syntax>
	1007	<short-description>Identify yourself with your password</short-description>
	1008
	1009	<description>
	1010	<para>
	1011	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.
	1012	</para>
	1013
	1014	<para>
	1015	Once you're registered, you can change your password using <emphasis>set password <password></emphasis>.
	1016	</para>
	1017	</description>
	1018	</bitlbee-command>
	1019
	1020	<bitlbee-command name="drop">
	1021	<syntax>drop <password></syntax>
	1022	<short-description>Drop your account</short-description>
	1023
	1024	<description>
	1025	<para>
	1026	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.
	1027	</para>
	1028	</description>
	1029	</bitlbee-command>
	1030
	1031	<bitlbee-command name="blist">
	1032	<syntax>blist [all\|online\|offline\|away]</syntax>
	1033	<short-description>List all the buddies in your contact list</short-description>
	1034
	1035	<description>
	1036	<para>
	1037	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.
	1038	</para>
	1039	</description>
	1040
	1041	</bitlbee-command>
	1042
	1043	<bitlbee-command name="nick">
	1044	<short-description>Change friendly name, nick</short-description>
	1045	<syntax>nick <connection> [<new nick>]</syntax>
	1046	<syntax>nick</syntax>
	1047
	1048	<description>
	1049	<para>
	1050	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.
	1051	</para>
[0aaca60]	1052
	1053	<para>
	1054	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.
	1055	</para>
[b7d3cc34]	1056	</description>
	1057
	1058	<ircexample>
	1059	<ircline nick="wouter">nick 1 "Wouter Paesen"</ircline>
	1060	<ircline nick="root">Setting your name on connection 1 to `Wouter Paesen'</ircline>
	1061	</ircexample>
	1062
	1063	</bitlbee-command>
	1064
[f7b44f2]	1065	<bitlbee-command name="join_chat">
	1066	<short-description>Join a named groupchat/conference room</short-description>
[3933853]	1067	<syntax>join_chat <connection> <room name> [<channel name>] [<room nickname>] [<password>]</syntax>
[b7d3cc34]	1068
	1069	<description>
	1070	<para>
[f7b44f2]	1071	On most IM-networks groupchats can be started using the /join command. (<emphasis>/join #foo</emphasis> to start a chatroom with you and <emphasis>foo</emphasis>) This doesn't work with names groupchats though (which exist on Jabber networks and AIM, for example), instead you can use this command.
[b7d3cc34]	1072	</para>
	1073
	1074	<para>
[f7b44f2]	1075	The first two arguments are required. <emphasis>room name</emphasis> is the name of the chatroom on the IM-network. <emphasis>channel name</emphasis> is the IRC channel name BitlBee should map this to. <emphasis>room nickname</emphasis> is the nickname you want to have in this channel. If you don't give these options, BitlBee will do the right guesses.
[b7d3cc34]	1076	</para>
	1077
	1078	<para>
[f7b44f2]	1079	The following command will join you to the chatroom called <emphasis>bitlbee@conference.bitlbee.org</emphasis>. The channel will be called <emphasis>&bitlbee-help</emphasis> because <emphasis>&bitlbee</emphasis> will already be in use. Your nickname will be <emphasis>help-me</emphasis>.
[b7d3cc34]	1080	</para>
	1081	</description>
	1082
[f7b44f2]	1083	<ircexample>
	1084	<ircline nick="wilmer">join_chat jabber bitlbee@conference.bitlbee.org &bitlbee-help help-me</ircline>
	1085	</ircexample>
	1086
[b7d3cc34]	1087	</bitlbee-command>
	1088	</chapter>

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

Download in other formats: