version wilmer@gaast.net-20051106182318-bcd0c40510635707 690 4ae17964fb30bfae8443685ec863cd3f279cb7fd
wilmer@gaast.net-20051106182318-bcd0c40510635707 <chapter id="commands">
wilmer@gaast.net-20051106182318-bcd0c40510635707 	<title>Bitlbee commands</title>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 	<command-list/>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 	<bitlbee-command name="account">
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<short-description>IM-account list maintenance</short-description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<syntax>account &lt;action&gt; [&lt;arguments&gt;]</syntax>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				Available actions: add, del, list, on, off. See <emphasis>help account &lt;action&gt;</emphasis> for more information.
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		</description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<bitlbee-command name="add">
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<syntax>account add &lt;protocol&gt; &lt;username&gt; &lt;password&gt; [&lt;server&gt;]</syntax>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 					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 &lt;protocol&gt;</emphasis>.
wilmer@gaast.net-20051106182318-bcd0c40510635707 				</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<bitlbee-command name="jabber">
wilmer@gaast.net-20051106182318-bcd0c40510635707 				<syntax>account add jabber &lt;handle&gt; &lt;password&gt; [&lt;servertag&gt;]</syntax>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 				<description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 					<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 						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: [&lt;servername&gt;[:&lt;portnumber&gt;][:ssl]]. For example, this is how you can connect to Google Talk:
wilmer@gaast.net-20051106182318-bcd0c40510635707 					</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				</description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 				<ircexample>
wilmer@gaast.net-20051106182318-bcd0c40510635707 					<ircline nick="wilmer">account add jabber example@gmail.com hobbelmeeuw talk.google.com:5223:ssl</ircline>
wilmer@gaast.net-20051106182318-bcd0c40510635707 					<ircline nick="root">Account successfully added</ircline>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				</ircexample>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 				<description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 					<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 						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.
wilmer@gaast.net-20051106182318-bcd0c40510635707 					</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				</description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</bitlbee-command>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<bitlbee-command name="msn">
wilmer@gaast.net-20051106182318-bcd0c40510635707 				<syntax>account add msn &lt;handle&gt; &lt;password&gt;</syntax>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 				<description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 					<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 						For MSN connections there are no special arguments.
wilmer@gaast.net-20051106182318-bcd0c40510635707 					</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				</description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</bitlbee-command>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<bitlbee-command name="oscar">
wilmer@gaast.net-20051106182318-bcd0c40510635707 				<syntax>account add oscar &lt;handle&gt; &lt;password&gt; [&lt;servername&gt;]</syntax>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 				<description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 					<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 						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>.
wilmer@gaast.net-20051106182318-bcd0c40510635707 					</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				</description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 				<ircexample>
wilmer@gaast.net-20051106182318-bcd0c40510635707 					<ircline nick="wilmer">account add oscar 72696705 hobbelmeeuw login.icq.com</ircline>
wilmer@gaast.net-20051106182318-bcd0c40510635707 					<ircline nick="root">Account successfully added</ircline>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				</ircexample>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</bitlbee-command>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<bitlbee-command name="yahoo">
wilmer@gaast.net-20051106182318-bcd0c40510635707 				<syntax>account add yahoo &lt;handle&gt; &lt;password&gt;</syntax>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 				<description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 					<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 						For Yahoo! connections there are no special arguments.
wilmer@gaast.net-20051106182318-bcd0c40510635707 					</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				</description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</bitlbee-command>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		</bitlbee-command>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<bitlbee-command name="del">
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<syntax>account del &lt;account id&gt;</syntax>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 					This commands deletes an account from your account list. You should signoff the account before deleting it.
wilmer@gaast.net-20051106182318-bcd0c40510635707 				</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 				<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 					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.
wilmer@gaast.net-20051106182318-bcd0c40510635707 				</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		</bitlbee-command>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<bitlbee-command name="on">
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<syntax>account on [&lt;account id&gt;]</syntax>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 					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)
wilmer@gaast.net-20051106182318-bcd0c40510635707 				</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 				<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 					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.
wilmer@gaast.net-20051106182318-bcd0c40510635707 				</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		</bitlbee-command>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<bitlbee-command name="off">
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<syntax>account off [&lt;account id&gt;]</syntax>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 					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)
wilmer@gaast.net-20051106182318-bcd0c40510635707 				</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 				<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 					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.
wilmer@gaast.net-20051106182318-bcd0c40510635707 				</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		</bitlbee-command>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<bitlbee-command name="list">
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<syntax>account list</syntax>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 					This command gives you a list of all the accounts known by BitlBee, including the numbers you'll need for most account commands.
wilmer@gaast.net-20051106182318-bcd0c40510635707 				</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		</bitlbee-command>
wilmer@gaast.net-20051106182318-bcd0c40510635707 	</bitlbee-command>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 	<bitlbee-command name="add">
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<short-description>Add a buddy to your contact list</short-description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<syntax>add &lt;connection&gt; &lt;handle&gt; [&lt;nick&gt;]</syntax>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				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.
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				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.
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		</description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<ircexample>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<ircline nick="ctrlsoft">add 3 gryp@jabber.org grijp</ircline>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<ircaction nick="grijp" hostmask="gryp@jabber.org">has joined <emphasis>#bitlbee</emphasis></ircaction>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		</ircexample>
wilmer@gaast.net-20051106182318-bcd0c40510635707 	</bitlbee-command>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 	<bitlbee-command name="info">
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<short-description>Request user information</short-description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<syntax>info &lt;connection&gt; &lt;handle&gt;</syntax>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<syntax>info &lt;nick&gt;</syntax>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				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.
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		</description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<ircexample>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<ircline nick="ctrlsoft">info 0 72696705</ircline>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<ircline nick="root">User info - UIN: 72696705   Nick: Lintux   First/Last name: Wilmer van der Gaast   E-mail: lintux@lintux.cx</ircline>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		</ircexample>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 	</bitlbee-command>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 	<bitlbee-command name="remove">
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<short-description>Remove a buddy from your contact list</short-description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<syntax>remove &lt;nick&gt;</syntax>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				Removes the specified nick from your buddy list. 
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		</description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<ircexample>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<ircline nick="ctrlsoft">remove gryp</ircline>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<ircaction nick="gryp" hostmask="gryp@jabber.jabber.org">has quit <emphasis>[Leaving...]</emphasis></ircaction>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		</ircexample>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 	</bitlbee-command>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 	<bitlbee-command name="block">
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<short-description>Block someone</short-description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<syntax>block &lt;nick&gt;</syntax>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<syntax>block &lt;connection&gt; &lt;handle&gt;</syntax>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				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.
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		</description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 	</bitlbee-command>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 	<bitlbee-command name="allow">
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<short-description>Unblock someone</short-description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<syntax>allow &lt;nick&gt;</syntax>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<syntax>allow &lt;connection&gt; &lt;handle&gt;</syntax>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				Reverse of block. Unignores the specified user or user handle on specified connection.
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		</description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 	</bitlbee-command>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 	<bitlbee-command name="set">
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<short-description>Miscellaneous settings</short-description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<syntax>set [&lt;variable&gt; [&lt;value&gt;]]</syntax>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				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.
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				To get more help information about a setting, try:
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		</description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<ircexample>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<ircline nick="ctrlsoft">help set private</ircline>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		</ircexample>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 	</bitlbee-command>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 	<bitlbee-command name="help">
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<short-description>BitlBee help system</short-description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<syntax>help [subject]</syntax>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				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.
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		</description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 	</bitlbee-command>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 	<bitlbee-command name="save">
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<short-description>Save your account data</short-description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<syntax>save</syntax>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				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... ;-)
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		</description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 	</bitlbee-command>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 	<bitlbee-setting name="charset" type="string">
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<default>iso8859-1</default>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<possible-values>you can get a list of all possible values by doing 'iconv -l' in a shell</possible-values>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				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.
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				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
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		</description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 	</bitlbee-setting>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 	<bitlbee-setting name="private" type="boolean">
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<default>True</default>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				If value is true, messages from users will appear in separate query windows. If false, messages from users will appear in the control channel.
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				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.
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		</description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 	</bitlbee-setting>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 	<bitlbee-setting name="save_on_quit" type="boolean">
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<default>True</default>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				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.
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		</description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 	</bitlbee-setting>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 	<bitlbee-setting name="html" type="string">
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<default>nostrip</default>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<possible-values>strip, nostrip</possible-values>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				Determines what BitlBee should do with HTML in messages. If set to nostrip, HTML in messages will not be touched. If set to strip, all HTML will be stripped from messages. Unfortunately this sometimes strips too much.
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		</description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 	</bitlbee-setting>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 	<bitlbee-setting name="debug" type="boolean">
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<default>False</default>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				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.
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		</description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 	</bitlbee-setting>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 	<bitlbee-setting name="to_char" type="string">
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<default>": "</default>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				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>.
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				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.
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		</description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 	</bitlbee-setting>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 	<bitlbee-setting name="typing_notice" type="boolean">
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<default>False</default>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				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. ;-)
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		</description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 	</bitlbee-setting>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 	<bitlbee-setting name="ops" type="string">
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<default>both</default>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<possible-values>both, root, user, none</possible-values>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				Some people prefer themself and root to have operator status in #bitlbee, other people don't. You can change these states using this setting.
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				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.
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		</description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 	</bitlbee-setting>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 	<bitlbee-setting name="away_devoice" type="boolean">
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<default>True</default>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				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.
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		</description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 	</bitlbee-setting>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 	<bitlbee-setting name="handle_unknown" type="string">
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<default>root</default>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<possible-values>root, add, add_private, add_channel, ignore</possible-values>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				Messages from unknown users are echoed like this by default:
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<ircexample>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				<ircline nick="root">Unknown message from handle 3137137:</ircline>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				<ircline nick="root">j0000! 1 4m l33t h4x0r! kill me!</ircline>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</ircexample>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				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.
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<note>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 					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.
wilmer@gaast.net-20051106182318-bcd0c40510635707 				</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</note>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		</description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 	</bitlbee-setting>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 	<bitlbee-setting name="auto_connect" type="boolean">
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<default>True</default>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				With this option enabled, when you identify BitlBee will automatically connect to your accounts, with this disabled it will not do this.
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		</description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 	</bitlbee-setting>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 	<bitlbee-setting name="auto_reconnect" type="boolean">
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<default>False</default>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				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.
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				See also the <emphasis>auto_reconnect_delay</emphasis> setting.
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		</description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 	</bitlbee-setting>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 	<bitlbee-setting name="auto_reconnect_delay" type="integer">
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<default>300</default>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				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.
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				See also the <emphasis>auto_reconnect</emphasis> setting.
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		</description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 	</bitlbee-setting>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 	<bitlbee-setting name="buddy_sendbuffer" type="boolean">
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<default>False</default>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				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.
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				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.
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				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.
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		</description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 	</bitlbee-setting>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 	<bitlbee-setting name="buddy_sendbuffer_delay" type="integer">
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				Tell BitlBee after how many seconds a buffered message should be sent.
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				See also the <emphasis>buddy_sendbuffer</emphasis> setting.
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		</description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 	</bitlbee-setting>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 	<bitlbee-setting name="default_target" type="string">
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<default>root</default>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<possible-values>root, last</possible-values>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				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>.
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		</description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 	</bitlbee-setting>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 	<bitlbee-setting name="display_namechanges" type="boolean">
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<default>False</default>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			With this option enabled, root will inform you when someone in your buddy list changes his/her "friendly name".
wilmer@gaast.net-20051106182318-bcd0c40510635707 		</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 	</bitlbee-setting>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 	<bitlbee-setting name="password" type="string">
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				Use this setting to change your "NickServ" password.
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		</description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 	</bitlbee-setting>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 	<bitlbee-setting name="query_order" type="string">
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<default>lifo</default>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<possible-values>lifo, fifo</possible-values>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				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.
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				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).
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		</description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 	</bitlbee-setting>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 	<bitlbee-setting name="lcnicks" type="boolean">
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<default>True</default>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				Hereby you can change whether you want all lower case nick names or leave the case as it intended by your peer.
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		</description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 	</bitlbee-setting>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 	<bitlbee-command name="rename">
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<short-description>Rename (renick) a buddy</short-description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<syntax>rename &lt;oldnick&gt; &lt;newnick&gt;</syntax>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				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).
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		</description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<ircexample>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<ircline nick="itsme">rename itsme_ you</ircline>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<ircaction nick="itsme_">is now known as <emphasis>you</emphasis></ircaction>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		</ircexample>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 	</bitlbee-command>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 	<bitlbee-command name="yes">
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<short-description>Accept a request</short-description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<syntax>yes [&lt;number&gt;]</syntax>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				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.
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				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.
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		</description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 	</bitlbee-command>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 	<bitlbee-command name="no">
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<short-description>Deny a request</short-description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<syntax>no [&lt;number&gt;]</syntax>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				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.
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				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.
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		</description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 	</bitlbee-command>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 	<bitlbee-command name="qlist">
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<short-description>List all the unanswered questions root asked</short-description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<syntax>qlist</syntax>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				This gives you a list of all the unanswered questions from root.
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		</description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 	</bitlbee-command>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 	<bitlbee-command name="register">
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<short-description>Register yourself</short-description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<syntax>register &lt;password&gt;</syntax>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				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.
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				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.. ;-)
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				To identify yourself in later sessions, you can use the <emphasis>identify</emphasis> command.
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		</description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 	</bitlbee-command>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 	<bitlbee-command name="identify">
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<syntax>identify &lt;password&gt;</syntax>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<short-description>Identify yourself with your password</short-description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				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.
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				Once you're registered, you can change your password using <emphasis>set password &lt;password&gt;</emphasis>.
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		</description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 	</bitlbee-command>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 	<bitlbee-command name="drop">
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<syntax>drop &lt;password&gt;</syntax>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<short-description>Drop your account</short-description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				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.
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		</description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 	</bitlbee-command>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 	<bitlbee-command name="blist">
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<syntax>blist [all|online|offline|away]</syntax>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<short-description>List all the buddies in your contact list</short-description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				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.
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		</description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 	</bitlbee-command>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 	<bitlbee-command name="nick">
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<short-description>Change friendly name, nick</short-description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<syntax>nick &lt;connection&gt; [&lt;new nick&gt;]</syntax>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<syntax>nick</syntax>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				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.
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		</description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<ircexample>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<ircline nick="wouter">nick 1 "Wouter Paesen"</ircline>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<ircline nick="root">Setting your name on connection 1 to `Wouter Paesen'</ircline>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		</ircexample>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 	</bitlbee-command>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 	<bitlbee-command name="import_buddies">
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<short-description>Copy local buddy list to server (normally only needed when upgrading)</short-description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<syntax>import_buddies &lt;connection&gt; [clear]</syntax>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				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.
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				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.
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				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.
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				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.
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		</description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 	</bitlbee-command>
wilmer@gaast.net-20051106182318-bcd0c40510635707 </chapter>
end wilmer@gaast.net-20051106182318-bcd0c40510635707
version wilmer@gaast.net-20051117143759-31e9a8975222ab4c 7 92b7296287bc5c271dc06e1a286db53418bbb832
463,467,6
wilmer@gaast.net-20051117143759-31e9a8975222ab4c 		<default>200</default>
wilmer@gaast.net-20051117143759-31e9a8975222ab4c 
wilmer@gaast.net-20051117143759-31e9a8975222ab4c 		<description>
wilmer@gaast.net-20051117143759-31e9a8975222ab4c 
wilmer@gaast.net-20051117143759-31e9a8975222ab4c 			<para>
wilmer@gaast.net-20051117143759-31e9a8975222ab4c 				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.
end wilmer@gaast.net-20051117143759-31e9a8975222ab4c
version wilmer@Jona.local-20051118124158-a9c89572ac86fe1a 10 25f6e511c1e1a16ae5bfb1683f0dc449f6445a09
304,311,9
wilmer@Jona.local-20051118124158-a9c89572ac86fe1a 	<bitlbee-setting name="strip_html" type="boolean">
wilmer@Jona.local-20051118124158-a9c89572ac86fe1a 		<default>True</default>
wilmer@Jona.local-20051118124158-a9c89572ac86fe1a 
wilmer@Jona.local-20051118124158-a9c89572ac86fe1a 		<description>
wilmer@Jona.local-20051118124158-a9c89572ac86fe1a 			<para>
wilmer@Jona.local-20051118124158-a9c89572ac86fe1a 				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.
wilmer@Jona.local-20051118124158-a9c89572ac86fe1a 			</para>
wilmer@Jona.local-20051118124158-a9c89572ac86fe1a 			<para>
wilmer@Jona.local-20051118124158-a9c89572ac86fe1a 				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.
end wilmer@Jona.local-20051118124158-a9c89572ac86fe1a
version wilmer@gaast.net-20051121115348-47a35a345605739b 4 b9be04faf0dcac6fbfccbf5f0999a3afa07131f2
155,156,1
wilmer@gaast.net-20051121115348-47a35a345605739b 			<ircaction nick="grijp" hostmask="gryp@jabber.org">has joined <emphasis>&amp;bitlbee</emphasis></ircaction>
358,359,1
wilmer@gaast.net-20051121115348-47a35a345605739b 				Some people prefer themself and root to have operator status in &amp;bitlbee, other people don't. You can change these states using this setting.
end wilmer@gaast.net-20051121115348-47a35a345605739b
version wilmer@gaast.net-20060321083815-684d54bbabb1a447 12 45bc8cf2f30713f32aec4292e059a0e7db234bee
198,198,1
wilmer@gaast.net-20060321083815-684d54bbabb1a447 		<syntax>block &lt;connection&gt;</syntax>
202,202,4
wilmer@gaast.net-20060321083815-684d54bbabb1a447 			</para>
wilmer@gaast.net-20060321083815-684d54bbabb1a447 			
wilmer@gaast.net-20060321083815-684d54bbabb1a447 			<para>
wilmer@gaast.net-20060321083815-684d54bbabb1a447 				When called with only a connection specification as an argument, the command displays the current block list for that connection.
215,215,4
wilmer@gaast.net-20060321083815-684d54bbabb1a447 			
wilmer@gaast.net-20060321083815-684d54bbabb1a447 			<para>
wilmer@gaast.net-20060321083815-684d54bbabb1a447 				When called with only a connection specification as an argument, the command displays the current allow list for that connection.
wilmer@gaast.net-20060321083815-684d54bbabb1a447 			</para>
end wilmer@gaast.net-20060321083815-684d54bbabb1a447
version wilmer@gaast.net-20060505161250-78e1921a80cd8ecb 2 97d2cc79614fc2e405d332b419aa25c4fcba8303
617,618,1
wilmer@gaast.net-20060505161250-78e1921a80cd8ecb 				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.
end wilmer@gaast.net-20060505161250-78e1921a80cd8ecb
version wilmer@gaast.net-20060505163157-64ae5472a4bc7f0e 7 154f89f6e1b5a5b9ccd72ed0881024912749e520
142,142,1
wilmer@gaast.net-20060505163157-64ae5472a4bc7f0e 		<syntax>add -tmp &lt;connection&gt; &lt;handle&gt; [&lt;nick&gt;]</syntax>
150,150,4
wilmer@gaast.net-20060505163157-64ae5472a4bc7f0e 			</para>
wilmer@gaast.net-20060505163157-64ae5472a4bc7f0e 			
wilmer@gaast.net-20060505163157-64ae5472a4bc7f0e 			<para>
wilmer@gaast.net-20060505163157-64ae5472a4bc7f0e 				Adding -tmp only adds the buddy to the internal BitlBee structures, not to the real contact list (like done by <emphasis>set handle_unknown add</emphasis>). This allows you to talk to people outside your contact list.
end wilmer@gaast.net-20060505163157-64ae5472a4bc7f0e
version wilmer@gaast.net-20060507112246-bc6c29dcaf50ed57 2 4c0b4be9e77dd0ee7269d5a03f7ed6d173a91c00
154,155,1
wilmer@gaast.net-20060507112246-bc6c29dcaf50ed57 				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.
end wilmer@gaast.net-20060507112246-bc6c29dcaf50ed57
version wilmer@gaast.net-20060714092548-d62da2798df02866 278 11400298d2e06de89d13340f3ef65de9bc0dfdfb
12,13,1
wilmer@gaast.net-20060714092548-d62da2798df02866 				Available actions: add, del, list, on, off and set. See <emphasis>help account &lt;action&gt;</emphasis> for more information.
27,28,1
wilmer@gaast.net-20060714092548-d62da2798df02866 				<syntax>account add jabber &lt;handle@server.tld&gt; &lt;password&gt; [&lt;servertag&gt;]</syntax>
31,32,7
wilmer@gaast.net-20060714092548-d62da2798df02866 						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: [&lt;servername&gt;[:&lt;portnumber&gt;][:ssl]].
wilmer@gaast.net-20060714092548-d62da2798df02866 					</para>
wilmer@gaast.net-20060714092548-d62da2798df02866 				</description>
wilmer@gaast.net-20060714092548-d62da2798df02866 
wilmer@gaast.net-20060714092548-d62da2798df02866 				<description>
wilmer@gaast.net-20060714092548-d62da2798df02866 					<para>
wilmer@gaast.net-20060714092548-d62da2798df02866 						Google Talk uses the Jabber protocol. Please note that Google talk is SSL-only, but officially reachable over both port 5222 and 5223. Usually BitlBee users have to connect via port 5223, for example like this:
39,45,0
48,49,1
wilmer@gaast.net-20060714092548-d62da2798df02866 				<syntax>account add msn &lt;handle@server.tld&gt; &lt;password&gt;</syntax>
104,105,1
wilmer@gaast.net-20060714092548-d62da2798df02866 					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.
119,120,1
wilmer@gaast.net-20060714092548-d62da2798df02866 					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.
134,134,20
wilmer@gaast.net-20060714092548-d62da2798df02866 				</para>
wilmer@gaast.net-20060714092548-d62da2798df02866 			</description>
wilmer@gaast.net-20060714092548-d62da2798df02866 		</bitlbee-command>
wilmer@gaast.net-20060714092548-d62da2798df02866 
wilmer@gaast.net-20060714092548-d62da2798df02866 		<bitlbee-command name="set">
wilmer@gaast.net-20060714092548-d62da2798df02866 			<syntax>account set &lt;account id&gt;</syntax>
wilmer@gaast.net-20060714092548-d62da2798df02866 			<syntax>account set &lt;account id&gt;/&lt;setting&gt;</syntax>
wilmer@gaast.net-20060714092548-d62da2798df02866 			<syntax>account set &lt;account id&gt;/&lt;setting&gt; &lt;value&gt;</syntax>
wilmer@gaast.net-20060714092548-d62da2798df02866 
wilmer@gaast.net-20060714092548-d62da2798df02866 			<description>
wilmer@gaast.net-20060714092548-d62da2798df02866 				<para>
wilmer@gaast.net-20060714092548-d62da2798df02866 					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 &lt;account id&gt;</emphasis>.
wilmer@gaast.net-20060714092548-d62da2798df02866 				</para>
wilmer@gaast.net-20060714092548-d62da2798df02866 				
wilmer@gaast.net-20060714092548-d62da2798df02866 				<para>
wilmer@gaast.net-20060714092548-d62da2798df02866 					For more infomation about a setting, see <emphasis>help set &lt;setting&gt;</emphasis>.
wilmer@gaast.net-20060714092548-d62da2798df02866 				</para>
wilmer@gaast.net-20060714092548-d62da2798df02866 				
wilmer@gaast.net-20060714092548-d62da2798df02866 				<para>
wilmer@gaast.net-20060714092548-d62da2798df02866 					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.
277,277,86
wilmer@gaast.net-20060714092548-d62da2798df02866 	<bitlbee-setting name="auto_connect" type="boolean">
wilmer@gaast.net-20060714092548-d62da2798df02866 		<default>True</default>
wilmer@gaast.net-20060714092548-d62da2798df02866 
wilmer@gaast.net-20060714092548-d62da2798df02866 		<description>
wilmer@gaast.net-20060714092548-d62da2798df02866 			<para>
wilmer@gaast.net-20060714092548-d62da2798df02866 				With this option enabled, when you identify BitlBee will automatically connect to your accounts, with this disabled it will not do this.
wilmer@gaast.net-20060714092548-d62da2798df02866 			</para>
wilmer@gaast.net-20060714092548-d62da2798df02866 			
wilmer@gaast.net-20060714092548-d62da2798df02866 			<para>
wilmer@gaast.net-20060714092548-d62da2798df02866 				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!)
wilmer@gaast.net-20060714092548-d62da2798df02866 			</para>
wilmer@gaast.net-20060714092548-d62da2798df02866 		</description>
wilmer@gaast.net-20060714092548-d62da2798df02866 	</bitlbee-setting>
wilmer@gaast.net-20060714092548-d62da2798df02866 
wilmer@gaast.net-20060714092548-d62da2798df02866 	<bitlbee-setting name="auto_reconnect" type="boolean">
wilmer@gaast.net-20060714092548-d62da2798df02866 		<default>False</default>
wilmer@gaast.net-20060714092548-d62da2798df02866 
wilmer@gaast.net-20060714092548-d62da2798df02866 		<description>
wilmer@gaast.net-20060714092548-d62da2798df02866 			<para>
wilmer@gaast.net-20060714092548-d62da2798df02866 				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.
wilmer@gaast.net-20060714092548-d62da2798df02866 			</para>
wilmer@gaast.net-20060714092548-d62da2798df02866 
wilmer@gaast.net-20060714092548-d62da2798df02866 			<para>
wilmer@gaast.net-20060714092548-d62da2798df02866 				See also the <emphasis>auto_reconnect_delay</emphasis> setting.
wilmer@gaast.net-20060714092548-d62da2798df02866 			</para>
wilmer@gaast.net-20060714092548-d62da2798df02866 		</description>
wilmer@gaast.net-20060714092548-d62da2798df02866 
wilmer@gaast.net-20060714092548-d62da2798df02866 	</bitlbee-setting>
wilmer@gaast.net-20060714092548-d62da2798df02866 
wilmer@gaast.net-20060714092548-d62da2798df02866 	<bitlbee-setting name="auto_reconnect_delay" type="integer">
wilmer@gaast.net-20060714092548-d62da2798df02866 		<default>300</default>
wilmer@gaast.net-20060714092548-d62da2798df02866 
wilmer@gaast.net-20060714092548-d62da2798df02866 		<description>
wilmer@gaast.net-20060714092548-d62da2798df02866 			<para>
wilmer@gaast.net-20060714092548-d62da2798df02866 				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.
wilmer@gaast.net-20060714092548-d62da2798df02866 			</para>
wilmer@gaast.net-20060714092548-d62da2798df02866 
wilmer@gaast.net-20060714092548-d62da2798df02866 			<para>
wilmer@gaast.net-20060714092548-d62da2798df02866 				See also the <emphasis>auto_reconnect</emphasis> setting.
wilmer@gaast.net-20060714092548-d62da2798df02866 			</para>
wilmer@gaast.net-20060714092548-d62da2798df02866 		</description>
wilmer@gaast.net-20060714092548-d62da2798df02866 	</bitlbee-setting>
wilmer@gaast.net-20060714092548-d62da2798df02866 
wilmer@gaast.net-20060714092548-d62da2798df02866 	<bitlbee-setting name="away_devoice" type="boolean">
wilmer@gaast.net-20060714092548-d62da2798df02866 		<default>True</default>
wilmer@gaast.net-20060714092548-d62da2798df02866 
wilmer@gaast.net-20060714092548-d62da2798df02866 		<description>
wilmer@gaast.net-20060714092548-d62da2798df02866 			<para>
wilmer@gaast.net-20060714092548-d62da2798df02866 				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.
wilmer@gaast.net-20060714092548-d62da2798df02866 			</para>
wilmer@gaast.net-20060714092548-d62da2798df02866 		</description>
wilmer@gaast.net-20060714092548-d62da2798df02866 	</bitlbee-setting>
wilmer@gaast.net-20060714092548-d62da2798df02866 
wilmer@gaast.net-20060714092548-d62da2798df02866 	<bitlbee-setting name="buddy_sendbuffer" type="boolean">
wilmer@gaast.net-20060714092548-d62da2798df02866 		<default>False</default>
wilmer@gaast.net-20060714092548-d62da2798df02866 
wilmer@gaast.net-20060714092548-d62da2798df02866 		<description>
wilmer@gaast.net-20060714092548-d62da2798df02866 			<para>
wilmer@gaast.net-20060714092548-d62da2798df02866 				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.
wilmer@gaast.net-20060714092548-d62da2798df02866 			</para>
wilmer@gaast.net-20060714092548-d62da2798df02866 
wilmer@gaast.net-20060714092548-d62da2798df02866 			<para>
wilmer@gaast.net-20060714092548-d62da2798df02866 				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.
wilmer@gaast.net-20060714092548-d62da2798df02866 			</para>
wilmer@gaast.net-20060714092548-d62da2798df02866 
wilmer@gaast.net-20060714092548-d62da2798df02866 			<para>
wilmer@gaast.net-20060714092548-d62da2798df02866 				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.
wilmer@gaast.net-20060714092548-d62da2798df02866 			</para>
wilmer@gaast.net-20060714092548-d62da2798df02866 		</description>
wilmer@gaast.net-20060714092548-d62da2798df02866 	</bitlbee-setting>
wilmer@gaast.net-20060714092548-d62da2798df02866 
wilmer@gaast.net-20060714092548-d62da2798df02866 	<bitlbee-setting name="buddy_sendbuffer_delay" type="integer">
wilmer@gaast.net-20060714092548-d62da2798df02866 		<default>200</default>
wilmer@gaast.net-20060714092548-d62da2798df02866 
wilmer@gaast.net-20060714092548-d62da2798df02866 		<description>
wilmer@gaast.net-20060714092548-d62da2798df02866 
wilmer@gaast.net-20060714092548-d62da2798df02866 			<para>
wilmer@gaast.net-20060714092548-d62da2798df02866 				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.
wilmer@gaast.net-20060714092548-d62da2798df02866 			</para>
wilmer@gaast.net-20060714092548-d62da2798df02866 
wilmer@gaast.net-20060714092548-d62da2798df02866 			<para>
wilmer@gaast.net-20060714092548-d62da2798df02866 				See also the <emphasis>buddy_sendbuffer</emphasis> setting.
wilmer@gaast.net-20060714092548-d62da2798df02866 			</para>
wilmer@gaast.net-20060714092548-d62da2798df02866 		</description>
wilmer@gaast.net-20060714092548-d62da2798df02866 	</bitlbee-setting>
wilmer@gaast.net-20060714092548-d62da2798df02866 
293,331,0
341,357,20
wilmer@gaast.net-20060714092548-d62da2798df02866 	<bitlbee-setting name="default_target" type="string">
wilmer@gaast.net-20060714092548-d62da2798df02866 		<default>root</default>
wilmer@gaast.net-20060714092548-d62da2798df02866 		<possible-values>root, last</possible-values>
wilmer@gaast.net-20060714092548-d62da2798df02866 
wilmer@gaast.net-20060714092548-d62da2798df02866 		<description>
wilmer@gaast.net-20060714092548-d62da2798df02866 			<para>
wilmer@gaast.net-20060714092548-d62da2798df02866 				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>.
wilmer@gaast.net-20060714092548-d62da2798df02866 			</para>
wilmer@gaast.net-20060714092548-d62da2798df02866 		</description>
wilmer@gaast.net-20060714092548-d62da2798df02866 	</bitlbee-setting>
wilmer@gaast.net-20060714092548-d62da2798df02866 
wilmer@gaast.net-20060714092548-d62da2798df02866 	<bitlbee-setting name="display_name" type="string">
wilmer@gaast.net-20060714092548-d62da2798df02866 		<description>
wilmer@gaast.net-20060714092548-d62da2798df02866 			<para>
wilmer@gaast.net-20060714092548-d62da2798df02866 				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.
wilmer@gaast.net-20060714092548-d62da2798df02866 			</para>
wilmer@gaast.net-20060714092548-d62da2798df02866 		</description>
wilmer@gaast.net-20060714092548-d62da2798df02866 	</bitlbee-setting>
wilmer@gaast.net-20060714092548-d62da2798df02866 
wilmer@gaast.net-20060714092548-d62da2798df02866 	<bitlbee-setting name="display_namechanges" type="boolean">
359,389,3
wilmer@gaast.net-20060714092548-d62da2798df02866 		<para>
wilmer@gaast.net-20060714092548-d62da2798df02866 			With this option enabled, root will inform you when someone in your buddy list changes his/her "friendly name".
wilmer@gaast.net-20060714092548-d62da2798df02866 		</para>
418,419,1
wilmer@gaast.net-20060714092548-d62da2798df02866 	<bitlbee-setting name="lcnicks" type="boolean">
423,512,19
wilmer@gaast.net-20060714092548-d62da2798df02866 				Hereby you can change whether you want all lower case nick names or leave the case as it intended by your peer.
wilmer@gaast.net-20060714092548-d62da2798df02866 			</para>
wilmer@gaast.net-20060714092548-d62da2798df02866 		</description>
wilmer@gaast.net-20060714092548-d62da2798df02866 
wilmer@gaast.net-20060714092548-d62da2798df02866 	</bitlbee-setting>
wilmer@gaast.net-20060714092548-d62da2798df02866 
wilmer@gaast.net-20060714092548-d62da2798df02866 	<bitlbee-setting name="ops" type="string">
wilmer@gaast.net-20060714092548-d62da2798df02866 		<default>both</default>
wilmer@gaast.net-20060714092548-d62da2798df02866 		<possible-values>both, root, user, none</possible-values>
wilmer@gaast.net-20060714092548-d62da2798df02866 
wilmer@gaast.net-20060714092548-d62da2798df02866 		<description>
wilmer@gaast.net-20060714092548-d62da2798df02866 			<para>
wilmer@gaast.net-20060714092548-d62da2798df02866 				Some people prefer themself and root to have operator status in &amp;bitlbee, other people don't. You can change these states using this setting.
wilmer@gaast.net-20060714092548-d62da2798df02866 			</para>
wilmer@gaast.net-20060714092548-d62da2798df02866 
wilmer@gaast.net-20060714092548-d62da2798df02866 			<para>
wilmer@gaast.net-20060714092548-d62da2798df02866 				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.
wilmer@gaast.net-20060714092548-d62da2798df02866 			</para>
wilmer@gaast.net-20060714092548-d62da2798df02866 		</description>
517,518,31
wilmer@gaast.net-20060714092548-d62da2798df02866 				Use this global setting to change your "NickServ" password.
wilmer@gaast.net-20060714092548-d62da2798df02866 			</para>
wilmer@gaast.net-20060714092548-d62da2798df02866 			
wilmer@gaast.net-20060714092548-d62da2798df02866 			<para>
wilmer@gaast.net-20060714092548-d62da2798df02866 				This setting is also available for all IM accounts to change the password BitlBee uses to connect to the service.
wilmer@gaast.net-20060714092548-d62da2798df02866 			</para>
wilmer@gaast.net-20060714092548-d62da2798df02866 			
wilmer@gaast.net-20060714092548-d62da2798df02866 			<para>
wilmer@gaast.net-20060714092548-d62da2798df02866 				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.
wilmer@gaast.net-20060714092548-d62da2798df02866 			</para>
wilmer@gaast.net-20060714092548-d62da2798df02866 		</description>
wilmer@gaast.net-20060714092548-d62da2798df02866 	</bitlbee-setting>
wilmer@gaast.net-20060714092548-d62da2798df02866 	
wilmer@gaast.net-20060714092548-d62da2798df02866 	<bitlbee-setting name="port" type="integer">
wilmer@gaast.net-20060714092548-d62da2798df02866 		<description>
wilmer@gaast.net-20060714092548-d62da2798df02866 			<para>
wilmer@gaast.net-20060714092548-d62da2798df02866 				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.
wilmer@gaast.net-20060714092548-d62da2798df02866 			</para>
wilmer@gaast.net-20060714092548-d62da2798df02866 		</description>
wilmer@gaast.net-20060714092548-d62da2798df02866 	</bitlbee-setting>
wilmer@gaast.net-20060714092548-d62da2798df02866 
wilmer@gaast.net-20060714092548-d62da2798df02866 	<bitlbee-setting name="private" type="boolean">
wilmer@gaast.net-20060714092548-d62da2798df02866 		<default>True</default>
wilmer@gaast.net-20060714092548-d62da2798df02866 
wilmer@gaast.net-20060714092548-d62da2798df02866 		<description>
wilmer@gaast.net-20060714092548-d62da2798df02866 			<para>
wilmer@gaast.net-20060714092548-d62da2798df02866 				If value is true, messages from users will appear in separate query windows. If false, messages from users will appear in the control channel.
wilmer@gaast.net-20060714092548-d62da2798df02866 			</para>
wilmer@gaast.net-20060714092548-d62da2798df02866 
wilmer@gaast.net-20060714092548-d62da2798df02866 			<para>
wilmer@gaast.net-20060714092548-d62da2798df02866 				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.
537,538,11
wilmer@gaast.net-20060714092548-d62da2798df02866 	<bitlbee-setting name="resource" type="string">
wilmer@gaast.net-20060714092548-d62da2798df02866 		<default>BitlBee</default>
wilmer@gaast.net-20060714092548-d62da2798df02866 
wilmer@gaast.net-20060714092548-d62da2798df02866 		<description>
wilmer@gaast.net-20060714092548-d62da2798df02866 			<para>
wilmer@gaast.net-20060714092548-d62da2798df02866 				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.
wilmer@gaast.net-20060714092548-d62da2798df02866 			</para>
wilmer@gaast.net-20060714092548-d62da2798df02866 		</description>
wilmer@gaast.net-20060714092548-d62da2798df02866 	</bitlbee-setting>
wilmer@gaast.net-20060714092548-d62da2798df02866 
wilmer@gaast.net-20060714092548-d62da2798df02866 	<bitlbee-setting name="save_on_quit" type="boolean">
542,546,58
wilmer@gaast.net-20060714092548-d62da2798df02866 				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.
wilmer@gaast.net-20060714092548-d62da2798df02866 			</para>
wilmer@gaast.net-20060714092548-d62da2798df02866 		</description>
wilmer@gaast.net-20060714092548-d62da2798df02866 	</bitlbee-setting>
wilmer@gaast.net-20060714092548-d62da2798df02866 
wilmer@gaast.net-20060714092548-d62da2798df02866 	<bitlbee-setting name="server" type="string">
wilmer@gaast.net-20060714092548-d62da2798df02866 		<description>
wilmer@gaast.net-20060714092548-d62da2798df02866 			<para>
wilmer@gaast.net-20060714092548-d62da2798df02866 				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.
wilmer@gaast.net-20060714092548-d62da2798df02866 			</para>
wilmer@gaast.net-20060714092548-d62da2798df02866 		</description>
wilmer@gaast.net-20060714092548-d62da2798df02866 	</bitlbee-setting>
wilmer@gaast.net-20060714092548-d62da2798df02866 
wilmer@gaast.net-20060714092548-d62da2798df02866 	<bitlbee-setting name="ssl" type="boolean">
wilmer@gaast.net-20060714092548-d62da2798df02866 		<default>False</default>
wilmer@gaast.net-20060714092548-d62da2798df02866 
wilmer@gaast.net-20060714092548-d62da2798df02866 		<description>
wilmer@gaast.net-20060714092548-d62da2798df02866 			<para>
wilmer@gaast.net-20060714092548-d62da2798df02866 				Currently only available for Jabber connections. Set this to true if the server accepts SSL connections.
wilmer@gaast.net-20060714092548-d62da2798df02866 			</para>
wilmer@gaast.net-20060714092548-d62da2798df02866 		</description>
wilmer@gaast.net-20060714092548-d62da2798df02866 	</bitlbee-setting>
wilmer@gaast.net-20060714092548-d62da2798df02866 
wilmer@gaast.net-20060714092548-d62da2798df02866 	<bitlbee-setting name="strip_html" type="boolean">
wilmer@gaast.net-20060714092548-d62da2798df02866 		<default>True</default>
wilmer@gaast.net-20060714092548-d62da2798df02866 
wilmer@gaast.net-20060714092548-d62da2798df02866 		<description>
wilmer@gaast.net-20060714092548-d62da2798df02866 			<para>
wilmer@gaast.net-20060714092548-d62da2798df02866 				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.
wilmer@gaast.net-20060714092548-d62da2798df02866 			</para>
wilmer@gaast.net-20060714092548-d62da2798df02866 			<para>
wilmer@gaast.net-20060714092548-d62da2798df02866 				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.
wilmer@gaast.net-20060714092548-d62da2798df02866 			</para>
wilmer@gaast.net-20060714092548-d62da2798df02866 		</description>
wilmer@gaast.net-20060714092548-d62da2798df02866 	</bitlbee-setting>
wilmer@gaast.net-20060714092548-d62da2798df02866 
wilmer@gaast.net-20060714092548-d62da2798df02866 	<bitlbee-setting name="to_char" type="string">
wilmer@gaast.net-20060714092548-d62da2798df02866 		<default>": "</default>
wilmer@gaast.net-20060714092548-d62da2798df02866 
wilmer@gaast.net-20060714092548-d62da2798df02866 		<description>
wilmer@gaast.net-20060714092548-d62da2798df02866 			<para>
wilmer@gaast.net-20060714092548-d62da2798df02866 				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>.
wilmer@gaast.net-20060714092548-d62da2798df02866 			</para>
wilmer@gaast.net-20060714092548-d62da2798df02866 
wilmer@gaast.net-20060714092548-d62da2798df02866 			<para>
wilmer@gaast.net-20060714092548-d62da2798df02866 				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.
wilmer@gaast.net-20060714092548-d62da2798df02866 			</para>
wilmer@gaast.net-20060714092548-d62da2798df02866 		</description>
wilmer@gaast.net-20060714092548-d62da2798df02866 	</bitlbee-setting>
wilmer@gaast.net-20060714092548-d62da2798df02866 
wilmer@gaast.net-20060714092548-d62da2798df02866 	<bitlbee-setting name="typing_notice" type="boolean">
wilmer@gaast.net-20060714092548-d62da2798df02866 		<default>False</default>
wilmer@gaast.net-20060714092548-d62da2798df02866 
wilmer@gaast.net-20060714092548-d62da2798df02866 		<description>
wilmer@gaast.net-20060714092548-d62da2798df02866 			<para>
wilmer@gaast.net-20060714092548-d62da2798df02866 				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. ;-)
wilmer@gaast.net-20060714092548-d62da2798df02866 			</para>
wilmer@gaast.net-20060714092548-d62da2798df02866 		</description>
end wilmer@gaast.net-20060714092548-d62da2798df02866
version wilmer@gaast.net-20060714182702-3998de1d3cc5831b 69 d0f87e28ed5400c77812992dfe576f586a579ea9
297,299,2
wilmer@gaast.net-20060714182702-3998de1d3cc5831b 	<bitlbee-setting name="auto_connect" type="boolean" scope="both">
wilmer@gaast.net-20060714182702-3998de1d3cc5831b 		<default>true</default>
311,313,2
wilmer@gaast.net-20060714182702-3998de1d3cc5831b 	<bitlbee-setting name="auto_reconnect" type="boolean" scope="both">
wilmer@gaast.net-20060714182702-3998de1d3cc5831b 		<default>false</default>
322,327,8
wilmer@gaast.net-20060714182702-3998de1d3cc5831b 
wilmer@gaast.net-20060714182702-3998de1d3cc5831b 			<para>
wilmer@gaast.net-20060714182702-3998de1d3cc5831b 				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!)
wilmer@gaast.net-20060714182702-3998de1d3cc5831b 			</para>
wilmer@gaast.net-20060714182702-3998de1d3cc5831b 		</description>
wilmer@gaast.net-20060714182702-3998de1d3cc5831b 	</bitlbee-setting>
wilmer@gaast.net-20060714182702-3998de1d3cc5831b 
wilmer@gaast.net-20060714182702-3998de1d3cc5831b 	<bitlbee-setting name="auto_reconnect_delay" type="integer" scope="global">
340,342,2
wilmer@gaast.net-20060714182702-3998de1d3cc5831b 	<bitlbee-setting name="away_devoice" type="boolean" scope="global">
wilmer@gaast.net-20060714182702-3998de1d3cc5831b 		<default>true</default>
350,352,2
wilmer@gaast.net-20060714182702-3998de1d3cc5831b 	<bitlbee-setting name="buddy_sendbuffer" type="boolean" scope="global">
wilmer@gaast.net-20060714182702-3998de1d3cc5831b 		<default>false</default>
368,369,1
wilmer@gaast.net-20060714182702-3998de1d3cc5831b 	<bitlbee-setting name="buddy_sendbuffer_delay" type="integer" scope="global">
383,384,1
wilmer@gaast.net-20060714182702-3998de1d3cc5831b 	<bitlbee-setting name="charset" type="string" scope="global">
399,401,2
wilmer@gaast.net-20060714182702-3998de1d3cc5831b 	<bitlbee-setting name="debug" type="boolean" scope="global">
wilmer@gaast.net-20060714182702-3998de1d3cc5831b 		<default>false</default>
409,410,1
wilmer@gaast.net-20060714182702-3998de1d3cc5831b 	<bitlbee-setting name="default_target" type="string" scope="global">
420,421,1
wilmer@gaast.net-20060714182702-3998de1d3cc5831b 	<bitlbee-setting name="display_name" type="string" scope="account">
428,430,2
wilmer@gaast.net-20060714182702-3998de1d3cc5831b 	<bitlbee-setting name="display_namechanges" type="boolean" scope="global">
wilmer@gaast.net-20060714182702-3998de1d3cc5831b 		<default>false</default>
436,437,1
wilmer@gaast.net-20060714182702-3998de1d3cc5831b 	<bitlbee-setting name="handle_unknown" type="string" scope="global">
463,465,2
wilmer@gaast.net-20060714182702-3998de1d3cc5831b 	<bitlbee-setting name="lcnicks" type="boolean" scope="global">
wilmer@gaast.net-20060714182702-3998de1d3cc5831b 		<default>true</default>
474,475,1
wilmer@gaast.net-20060714182702-3998de1d3cc5831b 	<bitlbee-setting name="ops" type="string" scope="global">
489,490,1
wilmer@gaast.net-20060714182702-3998de1d3cc5831b 	<bitlbee-setting name="password" type="string" scope="both">
505,506,1
wilmer@gaast.net-20060714182702-3998de1d3cc5831b 	<bitlbee-setting name="port" type="integer" scope="account">
513,515,2
wilmer@gaast.net-20060714182702-3998de1d3cc5831b 	<bitlbee-setting name="private" type="boolean" scope="global">
wilmer@gaast.net-20060714182702-3998de1d3cc5831b 		<default>true</default>
527,528,1
wilmer@gaast.net-20060714182702-3998de1d3cc5831b 	<bitlbee-setting name="query_order" type="string" scope="global">
542,543,1
wilmer@gaast.net-20060714182702-3998de1d3cc5831b 	<bitlbee-setting name="resource" type="string" scope="account">
552,554,2
wilmer@gaast.net-20060714182702-3998de1d3cc5831b 	<bitlbee-setting name="save_on_quit" type="boolean" scope="global">
wilmer@gaast.net-20060714182702-3998de1d3cc5831b 		<default>true</default>
562,563,1
wilmer@gaast.net-20060714182702-3998de1d3cc5831b 	<bitlbee-setting name="server" type="string" scope="account">
570,572,2
wilmer@gaast.net-20060714182702-3998de1d3cc5831b 	<bitlbee-setting name="ssl" type="boolean" scope="account">
wilmer@gaast.net-20060714182702-3998de1d3cc5831b 		<default>false</default>
580,582,2
wilmer@gaast.net-20060714182702-3998de1d3cc5831b 	<bitlbee-setting name="strip_html" type="boolean" scope="global">
wilmer@gaast.net-20060714182702-3998de1d3cc5831b 		<default>true</default>
593,594,1
wilmer@gaast.net-20060714182702-3998de1d3cc5831b 	<bitlbee-setting name="to_char" type="string" scope="global">
607,609,2
wilmer@gaast.net-20060714182702-3998de1d3cc5831b 	<bitlbee-setting name="typing_notice" type="boolean" scope="global">
wilmer@gaast.net-20060714182702-3998de1d3cc5831b 		<default>false</default>
end wilmer@gaast.net-20060714182702-3998de1d3cc5831b
version wilmer@gaast.net-20060719165238-b8cfaccf380c8e17 5 b2f8aaa632b7bcc09a8793fa94152c53f90a404a
747,747,4
wilmer@gaast.net-20060719165238-b8cfaccf380c8e17 
wilmer@gaast.net-20060719165238-b8cfaccf380c8e17 			<para>
wilmer@gaast.net-20060719165238-b8cfaccf380c8e17 				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.
wilmer@gaast.net-20060719165238-b8cfaccf380c8e17 			</para>
end wilmer@gaast.net-20060719165238-b8cfaccf380c8e17
version wilmer@gaast.net-20060813190838-610e2f732d79f57f 15 5726a99919d8f7a648d922f67e7af3d28969c493
620,620,14
wilmer@gaast.net-20060813190838-610e2f732d79f57f 	<bitlbee-setting name="web_aware" type="string" scope="account">
wilmer@gaast.net-20060813190838-610e2f732d79f57f 		<default>false</default>
wilmer@gaast.net-20060813190838-610e2f732d79f57f 
wilmer@gaast.net-20060813190838-610e2f732d79f57f 		<description>
wilmer@gaast.net-20060813190838-610e2f732d79f57f 			<para>
wilmer@gaast.net-20060813190838-610e2f732d79f57f 				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.
wilmer@gaast.net-20060813190838-610e2f732d79f57f 			</para>
wilmer@gaast.net-20060813190838-610e2f732d79f57f 
wilmer@gaast.net-20060813190838-610e2f732d79f57f 			<para>
wilmer@gaast.net-20060813190838-610e2f732d79f57f 				Unless you really intend to use this feature somewhere (on forums or maybe a website), it's probably better to keep this setting disabled.
wilmer@gaast.net-20060813190838-610e2f732d79f57f 			</para>
wilmer@gaast.net-20060813190838-610e2f732d79f57f 		</description>
wilmer@gaast.net-20060813190838-610e2f732d79f57f 	</bitlbee-setting>
wilmer@gaast.net-20060813190838-610e2f732d79f57f 
end wilmer@gaast.net-20060813190838-610e2f732d79f57f
version wilmer@gaast.net-20061015140227-ab2b9966bd821b9c 6 9298368b72ad711a4a22552a7662d74fbf80174d
434,437,5
wilmer@gaast.net-20061015140227-ab2b9966bd821b9c 		<description>
wilmer@gaast.net-20061015140227-ab2b9966bd821b9c 			<para>
wilmer@gaast.net-20061015140227-ab2b9966bd821b9c 				With this option enabled, root will inform you when someone in your buddy list changes his/her "friendly name".
wilmer@gaast.net-20061015140227-ab2b9966bd821b9c 			</para>
wilmer@gaast.net-20061015140227-ab2b9966bd821b9c 		</description>
end wilmer@gaast.net-20061015140227-ab2b9966bd821b9c
version wilmer@gaast.net-20061015145832-3467b4cab598c576 53 93adc6ac4bc39006da3b6f76348c4ec38f3f84c4
31,32,5
wilmer@gaast.net-20061015145832-3467b4cab598c576 						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.
wilmer@gaast.net-20061015145832-3467b4cab598c576 					</para>
wilmer@gaast.net-20061015145832-3467b4cab598c576 
wilmer@gaast.net-20061015145832-3467b4cab598c576 					<para>
wilmer@gaast.net-20061015145832-3467b4cab598c576 						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>).
34,45,0
516,516,14
wilmer@gaast.net-20061015145832-3467b4cab598c576 	<bitlbee-setting name="priority" type="integer" scope="account">
wilmer@gaast.net-20061015145832-3467b4cab598c576 		<default>0</default>
wilmer@gaast.net-20061015145832-3467b4cab598c576 
wilmer@gaast.net-20061015145832-3467b4cab598c576 		<description>
wilmer@gaast.net-20061015145832-3467b4cab598c576 			<para>
wilmer@gaast.net-20061015145832-3467b4cab598c576 				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).
wilmer@gaast.net-20061015145832-3467b4cab598c576 			</para>
wilmer@gaast.net-20061015145832-3467b4cab598c576 
wilmer@gaast.net-20061015145832-3467b4cab598c576 			<para>
wilmer@gaast.net-20061015145832-3467b4cab598c576 				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).
wilmer@gaast.net-20061015145832-3467b4cab598c576 			</para>
wilmer@gaast.net-20061015145832-3467b4cab598c576 		</description>
wilmer@gaast.net-20061015145832-3467b4cab598c576 	</bitlbee-setting>
wilmer@gaast.net-20061015145832-3467b4cab598c576 
555,555,15
wilmer@gaast.net-20061015145832-3467b4cab598c576 	<bitlbee-setting name="resource_select" type="string" scope="account">
wilmer@gaast.net-20061015145832-3467b4cab598c576 		<default>priority</default>
wilmer@gaast.net-20061015145832-3467b4cab598c576 		<possible-values>priority, time</possible-values>
wilmer@gaast.net-20061015145832-3467b4cab598c576 
wilmer@gaast.net-20061015145832-3467b4cab598c576 		<description>
wilmer@gaast.net-20061015145832-3467b4cab598c576 			<para>
wilmer@gaast.net-20061015145832-3467b4cab598c576 				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.
wilmer@gaast.net-20061015145832-3467b4cab598c576 			</para>
wilmer@gaast.net-20061015145832-3467b4cab598c576 
wilmer@gaast.net-20061015145832-3467b4cab598c576 			<para>
wilmer@gaast.net-20061015145832-3467b4cab598c576 				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).
wilmer@gaast.net-20061015145832-3467b4cab598c576 			</para>
wilmer@gaast.net-20061015145832-3467b4cab598c576 		</description>
wilmer@gaast.net-20061015145832-3467b4cab598c576 	</bitlbee-setting>
wilmer@gaast.net-20061015145832-3467b4cab598c576 
592,592,14
wilmer@gaast.net-20061015145832-3467b4cab598c576 			</para>
wilmer@gaast.net-20061015145832-3467b4cab598c576 		</description>
wilmer@gaast.net-20061015145832-3467b4cab598c576 	</bitlbee-setting>
wilmer@gaast.net-20061015145832-3467b4cab598c576 
wilmer@gaast.net-20061015145832-3467b4cab598c576 	<bitlbee-setting name="tls" type="boolean" scope="account">
wilmer@gaast.net-20061015145832-3467b4cab598c576 		<default>try</default>
wilmer@gaast.net-20061015145832-3467b4cab598c576 
wilmer@gaast.net-20061015145832-3467b4cab598c576 		<description>
wilmer@gaast.net-20061015145832-3467b4cab598c576 			<para>
wilmer@gaast.net-20061015145832-3467b4cab598c576 				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.
wilmer@gaast.net-20061015145832-3467b4cab598c576 			</para>
wilmer@gaast.net-20061015145832-3467b4cab598c576 
wilmer@gaast.net-20061015145832-3467b4cab598c576 			<para>
wilmer@gaast.net-20061015145832-3467b4cab598c576 				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.
end wilmer@gaast.net-20061015145832-3467b4cab598c576
version wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 53 93adc6ac4bc39006da3b6f76348c4ec38f3f84c4
31,32,5
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 						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.
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 					</para>
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 					<para>
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 						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>).
34,45,0
516,516,14
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 	<bitlbee-setting name="priority" type="integer" scope="account">
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 		<default>0</default>
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 		<description>
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 			<para>
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 				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).
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 			</para>
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 			<para>
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 				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).
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 			</para>
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 		</description>
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 	</bitlbee-setting>
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 
555,555,15
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 	<bitlbee-setting name="resource_select" type="string" scope="account">
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 		<default>priority</default>
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 		<possible-values>priority, time</possible-values>
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 		<description>
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 			<para>
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 				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.
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 			</para>
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 			<para>
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 				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).
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 			</para>
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 		</description>
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 	</bitlbee-setting>
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 
592,592,14
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 			</para>
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 		</description>
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 	</bitlbee-setting>
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 	<bitlbee-setting name="tls" type="boolean" scope="account">
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 		<default>try</default>
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 		<description>
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 			<para>
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 				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.
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 			</para>
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 			<para>
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 				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.
end wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4
version wilmer@gaast.net-20061015153457-395111a3b2453ad1 6 a0bdbf94f8f9cfc1690b1c5a0432e81e0e197517
427,430,5
wilmer@gaast.net-20061015140227-ab2b9966bd821b9c 		<description>
wilmer@gaast.net-20061015140227-ab2b9966bd821b9c 			<para>
wilmer@gaast.net-20061015140227-ab2b9966bd821b9c 				With this option enabled, root will inform you when someone in your buddy list changes his/her "friendly name".
wilmer@gaast.net-20061015140227-ab2b9966bd821b9c 			</para>
wilmer@gaast.net-20061015140227-ab2b9966bd821b9c 		</description>
end wilmer@gaast.net-20061015153457-395111a3b2453ad1
version wilmer@gaast.net-20070630215244-4zrlolzpsce04xqj 836 c0a3d741f36f498f823f79e2ab54290030b4d588
wilmer@gaast.net-20051106182318-bcd0c40510635707 <chapter id="commands">
wilmer@gaast.net-20051106182318-bcd0c40510635707 	<title>Bitlbee commands</title>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 	<command-list/>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 	<bitlbee-command name="account">
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<short-description>IM-account list maintenance</short-description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<syntax>account &lt;action&gt; [&lt;arguments&gt;]</syntax>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20060714092548-d62da2798df02866 				Available actions: add, del, list, on, off and set. See <emphasis>help account &lt;action&gt;</emphasis> for more information.
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		</description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<bitlbee-command name="add">
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<syntax>account add &lt;protocol&gt; &lt;username&gt; &lt;password&gt; [&lt;server&gt;]</syntax>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 					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 &lt;protocol&gt;</emphasis>.
wilmer@gaast.net-20051106182318-bcd0c40510635707 				</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<bitlbee-command name="jabber">
wilmer@gaast.net-20060714092548-d62da2798df02866 				<syntax>account add jabber &lt;handle@server.tld&gt; &lt;password&gt; [&lt;servertag&gt;]</syntax>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 				<description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 					<para>
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 						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.
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 					</para>
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 					<para>
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 						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>).
wilmer@gaast.net-20060714092548-d62da2798df02866 					</para>
wilmer@gaast.net-20060714092548-d62da2798df02866 				</description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</bitlbee-command>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<bitlbee-command name="msn">
wilmer@gaast.net-20060714092548-d62da2798df02866 				<syntax>account add msn &lt;handle@server.tld&gt; &lt;password&gt;</syntax>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 				<description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 					<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 						For MSN connections there are no special arguments.
wilmer@gaast.net-20051106182318-bcd0c40510635707 					</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				</description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</bitlbee-command>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<bitlbee-command name="oscar">
wilmer@gaast.net-20051106182318-bcd0c40510635707 				<syntax>account add oscar &lt;handle&gt; &lt;password&gt; [&lt;servername&gt;]</syntax>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 				<description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 					<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 						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>.
wilmer@gaast.net-20051106182318-bcd0c40510635707 					</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				</description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 				<ircexample>
wilmer@gaast.net-20051106182318-bcd0c40510635707 					<ircline nick="wilmer">account add oscar 72696705 hobbelmeeuw login.icq.com</ircline>
wilmer@gaast.net-20051106182318-bcd0c40510635707 					<ircline nick="root">Account successfully added</ircline>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				</ircexample>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</bitlbee-command>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<bitlbee-command name="yahoo">
wilmer@gaast.net-20051106182318-bcd0c40510635707 				<syntax>account add yahoo &lt;handle&gt; &lt;password&gt;</syntax>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 				<description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 					<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 						For Yahoo! connections there are no special arguments.
wilmer@gaast.net-20051106182318-bcd0c40510635707 					</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				</description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</bitlbee-command>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		</bitlbee-command>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<bitlbee-command name="del">
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<syntax>account del &lt;account id&gt;</syntax>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 					This commands deletes an account from your account list. You should signoff the account before deleting it.
wilmer@gaast.net-20051106182318-bcd0c40510635707 				</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 				<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 					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.
wilmer@gaast.net-20051106182318-bcd0c40510635707 				</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		</bitlbee-command>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<bitlbee-command name="on">
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<syntax>account on [&lt;account id&gt;]</syntax>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				<para>
wilmer@gaast.net-20060714092548-d62da2798df02866 					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.
wilmer@gaast.net-20051106182318-bcd0c40510635707 				</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 				<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 					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.
wilmer@gaast.net-20051106182318-bcd0c40510635707 				</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		</bitlbee-command>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<bitlbee-command name="off">
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<syntax>account off [&lt;account id&gt;]</syntax>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				<para>
wilmer@gaast.net-20060714092548-d62da2798df02866 					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.
wilmer@gaast.net-20051106182318-bcd0c40510635707 				</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 				<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 					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.
wilmer@gaast.net-20051106182318-bcd0c40510635707 				</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		</bitlbee-command>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<bitlbee-command name="list">
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<syntax>account list</syntax>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 					This command gives you a list of all the accounts known by BitlBee, including the numbers you'll need for most account commands.
wilmer@gaast.net-20060714092548-d62da2798df02866 				</para>
wilmer@gaast.net-20060714092548-d62da2798df02866 			</description>
wilmer@gaast.net-20060714092548-d62da2798df02866 		</bitlbee-command>
wilmer@gaast.net-20060714092548-d62da2798df02866 
wilmer@gaast.net-20060714092548-d62da2798df02866 		<bitlbee-command name="set">
wilmer@gaast.net-20060714092548-d62da2798df02866 			<syntax>account set &lt;account id&gt;</syntax>
wilmer@gaast.net-20060714092548-d62da2798df02866 			<syntax>account set &lt;account id&gt;/&lt;setting&gt;</syntax>
wilmer@gaast.net-20060714092548-d62da2798df02866 			<syntax>account set &lt;account id&gt;/&lt;setting&gt; &lt;value&gt;</syntax>
wilmer@gaast.net-20060714092548-d62da2798df02866 
wilmer@gaast.net-20060714092548-d62da2798df02866 			<description>
wilmer@gaast.net-20060714092548-d62da2798df02866 				<para>
wilmer@gaast.net-20060714092548-d62da2798df02866 					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 &lt;account id&gt;</emphasis>.
wilmer@gaast.net-20060714092548-d62da2798df02866 				</para>
wilmer@gaast.net-20060714092548-d62da2798df02866 				
wilmer@gaast.net-20060714092548-d62da2798df02866 				<para>
wilmer@gaast.net-20060714092548-d62da2798df02866 					For more infomation about a setting, see <emphasis>help set &lt;setting&gt;</emphasis>.
wilmer@gaast.net-20060714092548-d62da2798df02866 				</para>
wilmer@gaast.net-20060714092548-d62da2798df02866 				
wilmer@gaast.net-20060714092548-d62da2798df02866 				<para>
wilmer@gaast.net-20060714092548-d62da2798df02866 					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.
wilmer@gaast.net-20051106182318-bcd0c40510635707 				</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		</bitlbee-command>
wilmer@gaast.net-20051106182318-bcd0c40510635707 	</bitlbee-command>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 	<bitlbee-command name="add">
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<short-description>Add a buddy to your contact list</short-description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<syntax>add &lt;connection&gt; &lt;handle&gt; [&lt;nick&gt;]</syntax>
wilmer@gaast.net-20060505163157-64ae5472a4bc7f0e 		<syntax>add -tmp &lt;connection&gt; &lt;handle&gt; [&lt;nick&gt;]</syntax>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				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.
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				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.
wilmer@gaast.net-20060505163157-64ae5472a4bc7f0e 			</para>
wilmer@gaast.net-20060505163157-64ae5472a4bc7f0e 			
wilmer@gaast.net-20060505163157-64ae5472a4bc7f0e 			<para>
wilmer@gaast.net-20060507112246-bc6c29dcaf50ed57 				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.
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		</description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<ircexample>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<ircline nick="ctrlsoft">add 3 gryp@jabber.org grijp</ircline>
wilmer@gaast.net-20051121115348-47a35a345605739b 			<ircaction nick="grijp" hostmask="gryp@jabber.org">has joined <emphasis>&amp;bitlbee</emphasis></ircaction>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		</ircexample>
wilmer@gaast.net-20051106182318-bcd0c40510635707 	</bitlbee-command>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 	<bitlbee-command name="info">
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<short-description>Request user information</short-description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<syntax>info &lt;connection&gt; &lt;handle&gt;</syntax>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<syntax>info &lt;nick&gt;</syntax>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				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.
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		</description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<ircexample>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<ircline nick="ctrlsoft">info 0 72696705</ircline>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<ircline nick="root">User info - UIN: 72696705   Nick: Lintux   First/Last name: Wilmer van der Gaast   E-mail: lintux@lintux.cx</ircline>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		</ircexample>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 	</bitlbee-command>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 	<bitlbee-command name="remove">
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<short-description>Remove a buddy from your contact list</short-description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<syntax>remove &lt;nick&gt;</syntax>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				Removes the specified nick from your buddy list. 
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		</description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<ircexample>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<ircline nick="ctrlsoft">remove gryp</ircline>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<ircaction nick="gryp" hostmask="gryp@jabber.jabber.org">has quit <emphasis>[Leaving...]</emphasis></ircaction>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		</ircexample>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 	</bitlbee-command>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 	<bitlbee-command name="block">
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<short-description>Block someone</short-description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<syntax>block &lt;nick&gt;</syntax>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<syntax>block &lt;connection&gt; &lt;handle&gt;</syntax>
wilmer@gaast.net-20060321083815-684d54bbabb1a447 		<syntax>block &lt;connection&gt;</syntax>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				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.
wilmer@gaast.net-20060321083815-684d54bbabb1a447 			</para>
wilmer@gaast.net-20060321083815-684d54bbabb1a447 			
wilmer@gaast.net-20060321083815-684d54bbabb1a447 			<para>
wilmer@gaast.net-20060321083815-684d54bbabb1a447 				When called with only a connection specification as an argument, the command displays the current block list for that connection.
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		</description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 	</bitlbee-command>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 	<bitlbee-command name="allow">
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<short-description>Unblock someone</short-description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<syntax>allow &lt;nick&gt;</syntax>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<syntax>allow &lt;connection&gt; &lt;handle&gt;</syntax>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				Reverse of block. Unignores the specified user or user handle on specified connection.
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20060321083815-684d54bbabb1a447 			
wilmer@gaast.net-20060321083815-684d54bbabb1a447 			<para>
wilmer@gaast.net-20060321083815-684d54bbabb1a447 				When called with only a connection specification as an argument, the command displays the current allow list for that connection.
wilmer@gaast.net-20060321083815-684d54bbabb1a447 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		</description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 	</bitlbee-command>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 	<bitlbee-command name="set">
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<short-description>Miscellaneous settings</short-description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<syntax>set [&lt;variable&gt; [&lt;value&gt;]]</syntax>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				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.
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				To get more help information about a setting, try:
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		</description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<ircexample>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<ircline nick="ctrlsoft">help set private</ircline>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		</ircexample>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 	</bitlbee-command>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 	<bitlbee-command name="help">
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<short-description>BitlBee help system</short-description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<syntax>help [subject]</syntax>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				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.
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		</description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 	</bitlbee-command>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 	<bitlbee-command name="save">
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<short-description>Save your account data</short-description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<syntax>save</syntax>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				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... ;-)
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		</description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 	</bitlbee-command>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20060714182702-3998de1d3cc5831b 	<bitlbee-setting name="auto_connect" type="boolean" scope="both">
wilmer@gaast.net-20060714182702-3998de1d3cc5831b 		<default>true</default>
wilmer@gaast.net-20060714092548-d62da2798df02866 
wilmer@gaast.net-20060714092548-d62da2798df02866 		<description>
wilmer@gaast.net-20060714092548-d62da2798df02866 			<para>
wilmer@gaast.net-20060714092548-d62da2798df02866 				With this option enabled, when you identify BitlBee will automatically connect to your accounts, with this disabled it will not do this.
wilmer@gaast.net-20060714092548-d62da2798df02866 			</para>
wilmer@gaast.net-20060714092548-d62da2798df02866 			
wilmer@gaast.net-20060714092548-d62da2798df02866 			<para>
wilmer@gaast.net-20060714092548-d62da2798df02866 				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!)
wilmer@gaast.net-20060714092548-d62da2798df02866 			</para>
wilmer@gaast.net-20060714092548-d62da2798df02866 		</description>
wilmer@gaast.net-20060714092548-d62da2798df02866 	</bitlbee-setting>
wilmer@gaast.net-20060714092548-d62da2798df02866 
wilmer@gaast.net-20060714182702-3998de1d3cc5831b 	<bitlbee-setting name="auto_reconnect" type="boolean" scope="both">
wilmer@gaast.net-20060714182702-3998de1d3cc5831b 		<default>false</default>
wilmer@gaast.net-20060714092548-d62da2798df02866 
wilmer@gaast.net-20060714092548-d62da2798df02866 		<description>
wilmer@gaast.net-20060714092548-d62da2798df02866 			<para>
wilmer@gaast.net-20060714092548-d62da2798df02866 				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.
wilmer@gaast.net-20060714092548-d62da2798df02866 			</para>
wilmer@gaast.net-20060714092548-d62da2798df02866 
wilmer@gaast.net-20060714092548-d62da2798df02866 			<para>
wilmer@gaast.net-20060714092548-d62da2798df02866 				See also the <emphasis>auto_reconnect_delay</emphasis> setting.
wilmer@gaast.net-20060714092548-d62da2798df02866 			</para>
wilmer@gaast.net-20060714182702-3998de1d3cc5831b 
wilmer@gaast.net-20060714182702-3998de1d3cc5831b 			<para>
wilmer@gaast.net-20060714182702-3998de1d3cc5831b 				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!)
wilmer@gaast.net-20060714182702-3998de1d3cc5831b 			</para>
wilmer@gaast.net-20060714182702-3998de1d3cc5831b 		</description>
wilmer@gaast.net-20060714182702-3998de1d3cc5831b 	</bitlbee-setting>
wilmer@gaast.net-20060714182702-3998de1d3cc5831b 
wilmer@gaast.net-20060714182702-3998de1d3cc5831b 	<bitlbee-setting name="auto_reconnect_delay" type="integer" scope="global">
wilmer@gaast.net-20060714092548-d62da2798df02866 		<default>300</default>
wilmer@gaast.net-20060714092548-d62da2798df02866 
wilmer@gaast.net-20060714092548-d62da2798df02866 		<description>
wilmer@gaast.net-20060714092548-d62da2798df02866 			<para>
wilmer@gaast.net-20060714092548-d62da2798df02866 				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.
wilmer@gaast.net-20060714092548-d62da2798df02866 			</para>
wilmer@gaast.net-20060714092548-d62da2798df02866 
wilmer@gaast.net-20060714092548-d62da2798df02866 			<para>
wilmer@gaast.net-20060714092548-d62da2798df02866 				See also the <emphasis>auto_reconnect</emphasis> setting.
wilmer@gaast.net-20060714092548-d62da2798df02866 			</para>
wilmer@gaast.net-20060714092548-d62da2798df02866 		</description>
wilmer@gaast.net-20060714092548-d62da2798df02866 	</bitlbee-setting>
wilmer@gaast.net-20060714092548-d62da2798df02866 
wilmer@gaast.net-20060714182702-3998de1d3cc5831b 	<bitlbee-setting name="away_devoice" type="boolean" scope="global">
wilmer@gaast.net-20060714182702-3998de1d3cc5831b 		<default>true</default>
wilmer@gaast.net-20060714092548-d62da2798df02866 
wilmer@gaast.net-20060714092548-d62da2798df02866 		<description>
wilmer@gaast.net-20060714092548-d62da2798df02866 			<para>
wilmer@gaast.net-20060714092548-d62da2798df02866 				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.
wilmer@gaast.net-20060714092548-d62da2798df02866 			</para>
wilmer@gaast.net-20060714092548-d62da2798df02866 		</description>
wilmer@gaast.net-20060714092548-d62da2798df02866 	</bitlbee-setting>
wilmer@gaast.net-20060714092548-d62da2798df02866 
wilmer@gaast.net-20060714182702-3998de1d3cc5831b 	<bitlbee-setting name="buddy_sendbuffer" type="boolean" scope="global">
wilmer@gaast.net-20060714182702-3998de1d3cc5831b 		<default>false</default>
wilmer@gaast.net-20060714092548-d62da2798df02866 
wilmer@gaast.net-20060714092548-d62da2798df02866 		<description>
wilmer@gaast.net-20060714092548-d62da2798df02866 			<para>
wilmer@gaast.net-20060714092548-d62da2798df02866 				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.
wilmer@gaast.net-20060714092548-d62da2798df02866 			</para>
wilmer@gaast.net-20060714092548-d62da2798df02866 
wilmer@gaast.net-20060714092548-d62da2798df02866 			<para>
wilmer@gaast.net-20060714092548-d62da2798df02866 				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.
wilmer@gaast.net-20060714092548-d62da2798df02866 			</para>
wilmer@gaast.net-20060714092548-d62da2798df02866 
wilmer@gaast.net-20060714092548-d62da2798df02866 			<para>
wilmer@gaast.net-20060714092548-d62da2798df02866 				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.
wilmer@gaast.net-20060714092548-d62da2798df02866 			</para>
wilmer@gaast.net-20060714092548-d62da2798df02866 		</description>
wilmer@gaast.net-20060714092548-d62da2798df02866 	</bitlbee-setting>
wilmer@gaast.net-20060714092548-d62da2798df02866 
wilmer@gaast.net-20060714182702-3998de1d3cc5831b 	<bitlbee-setting name="buddy_sendbuffer_delay" type="integer" scope="global">
wilmer@gaast.net-20060714092548-d62da2798df02866 		<default>200</default>
wilmer@gaast.net-20060714092548-d62da2798df02866 
wilmer@gaast.net-20060714092548-d62da2798df02866 		<description>
wilmer@gaast.net-20060714092548-d62da2798df02866 
wilmer@gaast.net-20060714092548-d62da2798df02866 			<para>
wilmer@gaast.net-20060714092548-d62da2798df02866 				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.
wilmer@gaast.net-20060714092548-d62da2798df02866 			</para>
wilmer@gaast.net-20060714092548-d62da2798df02866 
wilmer@gaast.net-20060714092548-d62da2798df02866 			<para>
wilmer@gaast.net-20060714092548-d62da2798df02866 				See also the <emphasis>buddy_sendbuffer</emphasis> setting.
wilmer@gaast.net-20060714092548-d62da2798df02866 			</para>
wilmer@gaast.net-20060714092548-d62da2798df02866 		</description>
wilmer@gaast.net-20060714092548-d62da2798df02866 	</bitlbee-setting>
wilmer@gaast.net-20060714092548-d62da2798df02866 
wilmer@gaast.net-20060714182702-3998de1d3cc5831b 	<bitlbee-setting name="charset" type="string" scope="global">
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<default>iso8859-1</default>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<possible-values>you can get a list of all possible values by doing 'iconv -l' in a shell</possible-values>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				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.
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				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
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		</description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 	</bitlbee-setting>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20060714182702-3998de1d3cc5831b 	<bitlbee-setting name="debug" type="boolean" scope="global">
wilmer@gaast.net-20060714182702-3998de1d3cc5831b 		<default>false</default>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				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.
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		</description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 	</bitlbee-setting>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20060714182702-3998de1d3cc5831b 	<bitlbee-setting name="default_target" type="string" scope="global">
wilmer@gaast.net-20060714092548-d62da2798df02866 		<default>root</default>
wilmer@gaast.net-20060714092548-d62da2798df02866 		<possible-values>root, last</possible-values>
wilmer@gaast.net-20060714092548-d62da2798df02866 
wilmer@gaast.net-20060714092548-d62da2798df02866 		<description>
wilmer@gaast.net-20060714092548-d62da2798df02866 			<para>
wilmer@gaast.net-20060714092548-d62da2798df02866 				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>.
wilmer@gaast.net-20060714092548-d62da2798df02866 			</para>
wilmer@gaast.net-20060714092548-d62da2798df02866 		</description>
wilmer@gaast.net-20060714092548-d62da2798df02866 	</bitlbee-setting>
wilmer@gaast.net-20060714092548-d62da2798df02866 
wilmer@gaast.net-20060714182702-3998de1d3cc5831b 	<bitlbee-setting name="display_name" type="string" scope="account">
wilmer@gaast.net-20060714092548-d62da2798df02866 		<description>
wilmer@gaast.net-20060714092548-d62da2798df02866 			<para>
wilmer@gaast.net-20060714092548-d62da2798df02866 				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.
wilmer@gaast.net-20060714092548-d62da2798df02866 			</para>
wilmer@gaast.net-20060714092548-d62da2798df02866 		</description>
wilmer@gaast.net-20060714092548-d62da2798df02866 	</bitlbee-setting>
wilmer@gaast.net-20060714092548-d62da2798df02866 
wilmer@gaast.net-20060714182702-3998de1d3cc5831b 	<bitlbee-setting name="display_namechanges" type="boolean" scope="global">
wilmer@gaast.net-20060714182702-3998de1d3cc5831b 		<default>false</default>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20061015140227-ab2b9966bd821b9c 		<description>
wilmer@gaast.net-20061015140227-ab2b9966bd821b9c 			<para>
wilmer@gaast.net-20061015140227-ab2b9966bd821b9c 				With this option enabled, root will inform you when someone in your buddy list changes his/her "friendly name".
wilmer@gaast.net-20061015140227-ab2b9966bd821b9c 			</para>
wilmer@gaast.net-20061015140227-ab2b9966bd821b9c 		</description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 	</bitlbee-setting>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20060714182702-3998de1d3cc5831b 	<bitlbee-setting name="handle_unknown" type="string" scope="global">
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<default>root</default>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<possible-values>root, add, add_private, add_channel, ignore</possible-values>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				Messages from unknown users are echoed like this by default:
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<ircexample>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				<ircline nick="root">Unknown message from handle 3137137:</ircline>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				<ircline nick="root">j0000! 1 4m l33t h4x0r! kill me!</ircline>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</ircexample>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				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.
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<note>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 					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.
wilmer@gaast.net-20051106182318-bcd0c40510635707 				</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</note>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		</description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 	</bitlbee-setting>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20060714182702-3998de1d3cc5831b 	<bitlbee-setting name="lcnicks" type="boolean" scope="global">
wilmer@gaast.net-20060714182702-3998de1d3cc5831b 		<default>true</default>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20060714092548-d62da2798df02866 				Hereby you can change whether you want all lower case nick names or leave the case as it intended by your peer.
wilmer@gaast.net-20060714092548-d62da2798df02866 			</para>
wilmer@gaast.net-20060714092548-d62da2798df02866 		</description>
wilmer@gaast.net-20060714092548-d62da2798df02866 
wilmer@gaast.net-20060714092548-d62da2798df02866 	</bitlbee-setting>
wilmer@gaast.net-20060714092548-d62da2798df02866 
wilmer@gaast.net-20060714182702-3998de1d3cc5831b 	<bitlbee-setting name="ops" type="string" scope="global">
wilmer@gaast.net-20060714092548-d62da2798df02866 		<default>both</default>
wilmer@gaast.net-20060714092548-d62da2798df02866 		<possible-values>both, root, user, none</possible-values>
wilmer@gaast.net-20060714092548-d62da2798df02866 
wilmer@gaast.net-20060714092548-d62da2798df02866 		<description>
wilmer@gaast.net-20060714092548-d62da2798df02866 			<para>
wilmer@gaast.net-20060714092548-d62da2798df02866 				Some people prefer themself and root to have operator status in &amp;bitlbee, other people don't. You can change these states using this setting.
wilmer@gaast.net-20060714092548-d62da2798df02866 			</para>
wilmer@gaast.net-20060714092548-d62da2798df02866 
wilmer@gaast.net-20060714092548-d62da2798df02866 			<para>
wilmer@gaast.net-20060714092548-d62da2798df02866 				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.
wilmer@gaast.net-20060714092548-d62da2798df02866 			</para>
wilmer@gaast.net-20060714092548-d62da2798df02866 		</description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 	</bitlbee-setting>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20060714182702-3998de1d3cc5831b 	<bitlbee-setting name="password" type="string" scope="both">
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20060714092548-d62da2798df02866 				Use this global setting to change your "NickServ" password.
wilmer@gaast.net-20060714092548-d62da2798df02866 			</para>
wilmer@gaast.net-20060714092548-d62da2798df02866 			
wilmer@gaast.net-20060714092548-d62da2798df02866 			<para>
wilmer@gaast.net-20060714092548-d62da2798df02866 				This setting is also available for all IM accounts to change the password BitlBee uses to connect to the service.
wilmer@gaast.net-20060714092548-d62da2798df02866 			</para>
wilmer@gaast.net-20060714092548-d62da2798df02866 			
wilmer@gaast.net-20060714092548-d62da2798df02866 			<para>
wilmer@gaast.net-20060714092548-d62da2798df02866 				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.
wilmer@gaast.net-20060714092548-d62da2798df02866 			</para>
wilmer@gaast.net-20060714092548-d62da2798df02866 		</description>
wilmer@gaast.net-20060714092548-d62da2798df02866 	</bitlbee-setting>
wilmer@gaast.net-20060714092548-d62da2798df02866 	
wilmer@gaast.net-20060714182702-3998de1d3cc5831b 	<bitlbee-setting name="port" type="integer" scope="account">
wilmer@gaast.net-20060714092548-d62da2798df02866 		<description>
wilmer@gaast.net-20060714092548-d62da2798df02866 			<para>
wilmer@gaast.net-20060714092548-d62da2798df02866 				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.
wilmer@gaast.net-20060714092548-d62da2798df02866 			</para>
wilmer@gaast.net-20060714092548-d62da2798df02866 		</description>
wilmer@gaast.net-20060714092548-d62da2798df02866 	</bitlbee-setting>
wilmer@gaast.net-20060714092548-d62da2798df02866 
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 	<bitlbee-setting name="priority" type="integer" scope="account">
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 		<default>0</default>
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 		<description>
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 			<para>
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 				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).
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 			</para>
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 			<para>
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 				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).
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 			</para>
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 		</description>
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 	</bitlbee-setting>
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 
wilmer@gaast.net-20060714182702-3998de1d3cc5831b 	<bitlbee-setting name="private" type="boolean" scope="global">
wilmer@gaast.net-20060714182702-3998de1d3cc5831b 		<default>true</default>
wilmer@gaast.net-20060714092548-d62da2798df02866 
wilmer@gaast.net-20060714092548-d62da2798df02866 		<description>
wilmer@gaast.net-20060714092548-d62da2798df02866 			<para>
wilmer@gaast.net-20060714092548-d62da2798df02866 				If value is true, messages from users will appear in separate query windows. If false, messages from users will appear in the control channel.
wilmer@gaast.net-20060714092548-d62da2798df02866 			</para>
wilmer@gaast.net-20060714092548-d62da2798df02866 
wilmer@gaast.net-20060714092548-d62da2798df02866 			<para>
wilmer@gaast.net-20060714092548-d62da2798df02866 				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.
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		</description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 	</bitlbee-setting>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20060714182702-3998de1d3cc5831b 	<bitlbee-setting name="query_order" type="string" scope="global">
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<default>lifo</default>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<possible-values>lifo, fifo</possible-values>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				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.
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				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).
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		</description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 	</bitlbee-setting>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20060714182702-3998de1d3cc5831b 	<bitlbee-setting name="resource" type="string" scope="account">
wilmer@gaast.net-20060714092548-d62da2798df02866 		<default>BitlBee</default>
wilmer@gaast.net-20060714092548-d62da2798df02866 
wilmer@gaast.net-20060714092548-d62da2798df02866 		<description>
wilmer@gaast.net-20060714092548-d62da2798df02866 			<para>
wilmer@gaast.net-20060714092548-d62da2798df02866 				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.
wilmer@gaast.net-20060714092548-d62da2798df02866 			</para>
wilmer@gaast.net-20060714092548-d62da2798df02866 		</description>
wilmer@gaast.net-20060714092548-d62da2798df02866 	</bitlbee-setting>
wilmer@gaast.net-20060714092548-d62da2798df02866 
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 	<bitlbee-setting name="resource_select" type="string" scope="account">
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 		<default>priority</default>
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 		<possible-values>priority, time</possible-values>
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 		<description>
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 			<para>
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 				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.
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 			</para>
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 			<para>
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 				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).
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 			</para>
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 		</description>
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 	</bitlbee-setting>
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 
wilmer@gaast.net-20060714182702-3998de1d3cc5831b 	<bitlbee-setting name="save_on_quit" type="boolean" scope="global">
wilmer@gaast.net-20060714182702-3998de1d3cc5831b 		<default>true</default>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20060714092548-d62da2798df02866 				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.
wilmer@gaast.net-20060714092548-d62da2798df02866 			</para>
wilmer@gaast.net-20060714092548-d62da2798df02866 		</description>
wilmer@gaast.net-20060714092548-d62da2798df02866 	</bitlbee-setting>
wilmer@gaast.net-20060714092548-d62da2798df02866 
wilmer@gaast.net-20060714182702-3998de1d3cc5831b 	<bitlbee-setting name="server" type="string" scope="account">
wilmer@gaast.net-20060714092548-d62da2798df02866 		<description>
wilmer@gaast.net-20060714092548-d62da2798df02866 			<para>
wilmer@gaast.net-20060714092548-d62da2798df02866 				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.
wilmer@gaast.net-20060714092548-d62da2798df02866 			</para>
wilmer@gaast.net-20060714092548-d62da2798df02866 		</description>
wilmer@gaast.net-20060714092548-d62da2798df02866 	</bitlbee-setting>
wilmer@gaast.net-20060714092548-d62da2798df02866 
wilmer@gaast.net-20060714182702-3998de1d3cc5831b 	<bitlbee-setting name="ssl" type="boolean" scope="account">
wilmer@gaast.net-20060714182702-3998de1d3cc5831b 		<default>false</default>
wilmer@gaast.net-20060714092548-d62da2798df02866 
wilmer@gaast.net-20060714092548-d62da2798df02866 		<description>
wilmer@gaast.net-20060714092548-d62da2798df02866 			<para>
wilmer@gaast.net-20060714092548-d62da2798df02866 				Currently only available for Jabber connections. Set this to true if the server accepts SSL connections.
wilmer@gaast.net-20060714092548-d62da2798df02866 			</para>
wilmer@gaast.net-20060714092548-d62da2798df02866 		</description>
wilmer@gaast.net-20060714092548-d62da2798df02866 	</bitlbee-setting>
wilmer@gaast.net-20060714092548-d62da2798df02866 
wilmer@gaast.net-20060714182702-3998de1d3cc5831b 	<bitlbee-setting name="strip_html" type="boolean" scope="global">
wilmer@gaast.net-20060714182702-3998de1d3cc5831b 		<default>true</default>
wilmer@gaast.net-20060714092548-d62da2798df02866 
wilmer@gaast.net-20060714092548-d62da2798df02866 		<description>
wilmer@gaast.net-20060714092548-d62da2798df02866 			<para>
wilmer@gaast.net-20060714092548-d62da2798df02866 				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.
wilmer@gaast.net-20060714092548-d62da2798df02866 			</para>
wilmer@gaast.net-20060714092548-d62da2798df02866 			<para>
wilmer@gaast.net-20060714092548-d62da2798df02866 				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.
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 			</para>
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 		</description>
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 	</bitlbee-setting>
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 	<bitlbee-setting name="tls" type="boolean" scope="account">
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 		<default>try</default>
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 		<description>
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 			<para>
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 				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.
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 			</para>
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 			<para>
wilmer@gaast.net-20061015150113-e9ccddbd6b6f79c4 				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.
wilmer@gaast.net-20060714092548-d62da2798df02866 			</para>
wilmer@gaast.net-20060714092548-d62da2798df02866 		</description>
wilmer@gaast.net-20060714092548-d62da2798df02866 	</bitlbee-setting>
wilmer@gaast.net-20060714092548-d62da2798df02866 
wilmer@gaast.net-20060714182702-3998de1d3cc5831b 	<bitlbee-setting name="to_char" type="string" scope="global">
wilmer@gaast.net-20060714092548-d62da2798df02866 		<default>": "</default>
wilmer@gaast.net-20060714092548-d62da2798df02866 
wilmer@gaast.net-20060714092548-d62da2798df02866 		<description>
wilmer@gaast.net-20060714092548-d62da2798df02866 			<para>
wilmer@gaast.net-20060714092548-d62da2798df02866 				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>.
wilmer@gaast.net-20060714092548-d62da2798df02866 			</para>
wilmer@gaast.net-20060714092548-d62da2798df02866 
wilmer@gaast.net-20060714092548-d62da2798df02866 			<para>
wilmer@gaast.net-20060714092548-d62da2798df02866 				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.
wilmer@gaast.net-20060714092548-d62da2798df02866 			</para>
wilmer@gaast.net-20060714092548-d62da2798df02866 		</description>
wilmer@gaast.net-20060714092548-d62da2798df02866 	</bitlbee-setting>
wilmer@gaast.net-20060714092548-d62da2798df02866 
wilmer@gaast.net-20060714182702-3998de1d3cc5831b 	<bitlbee-setting name="typing_notice" type="boolean" scope="global">
wilmer@gaast.net-20060714182702-3998de1d3cc5831b 		<default>false</default>
wilmer@gaast.net-20060714092548-d62da2798df02866 
wilmer@gaast.net-20060714092548-d62da2798df02866 		<description>
wilmer@gaast.net-20060714092548-d62da2798df02866 			<para>
wilmer@gaast.net-20060714092548-d62da2798df02866 				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. ;-)
wilmer@gaast.net-20060714092548-d62da2798df02866 			</para>
wilmer@gaast.net-20060714092548-d62da2798df02866 		</description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 	</bitlbee-setting>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20060813190838-610e2f732d79f57f 	<bitlbee-setting name="web_aware" type="string" scope="account">
wilmer@gaast.net-20060813190838-610e2f732d79f57f 		<default>false</default>
wilmer@gaast.net-20060813190838-610e2f732d79f57f 
wilmer@gaast.net-20060813190838-610e2f732d79f57f 		<description>
wilmer@gaast.net-20060813190838-610e2f732d79f57f 			<para>
wilmer@gaast.net-20060813190838-610e2f732d79f57f 				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.
wilmer@gaast.net-20060813190838-610e2f732d79f57f 			</para>
wilmer@gaast.net-20060813190838-610e2f732d79f57f 
wilmer@gaast.net-20060813190838-610e2f732d79f57f 			<para>
wilmer@gaast.net-20060813190838-610e2f732d79f57f 				Unless you really intend to use this feature somewhere (on forums or maybe a website), it's probably better to keep this setting disabled.
wilmer@gaast.net-20060813190838-610e2f732d79f57f 			</para>
wilmer@gaast.net-20060813190838-610e2f732d79f57f 		</description>
wilmer@gaast.net-20060813190838-610e2f732d79f57f 	</bitlbee-setting>
wilmer@gaast.net-20060813190838-610e2f732d79f57f 
wilmer@gaast.net-20051106182318-bcd0c40510635707 	<bitlbee-command name="rename">
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<short-description>Rename (renick) a buddy</short-description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<syntax>rename &lt;oldnick&gt; &lt;newnick&gt;</syntax>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				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).
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		</description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<ircexample>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<ircline nick="itsme">rename itsme_ you</ircline>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<ircaction nick="itsme_">is now known as <emphasis>you</emphasis></ircaction>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		</ircexample>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 	</bitlbee-command>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 	<bitlbee-command name="yes">
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<short-description>Accept a request</short-description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<syntax>yes [&lt;number&gt;]</syntax>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				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.
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				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.
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		</description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 	</bitlbee-command>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 	<bitlbee-command name="no">
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<short-description>Deny a request</short-description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<syntax>no [&lt;number&gt;]</syntax>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				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.
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				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.
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		</description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 	</bitlbee-command>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 	<bitlbee-command name="qlist">
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<short-description>List all the unanswered questions root asked</short-description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<syntax>qlist</syntax>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				This gives you a list of all the unanswered questions from root.
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		</description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 	</bitlbee-command>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 	<bitlbee-command name="register">
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<short-description>Register yourself</short-description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<syntax>register &lt;password&gt;</syntax>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				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.
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				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.. ;-)
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20060505161250-78e1921a80cd8ecb 				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.
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		</description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 	</bitlbee-command>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 	<bitlbee-command name="identify">
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<syntax>identify &lt;password&gt;</syntax>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<short-description>Identify yourself with your password</short-description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				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.
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				Once you're registered, you can change your password using <emphasis>set password &lt;password&gt;</emphasis>.
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		</description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 	</bitlbee-command>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 	<bitlbee-command name="drop">
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<syntax>drop &lt;password&gt;</syntax>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<short-description>Drop your account</short-description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				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.
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		</description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 	</bitlbee-command>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 	<bitlbee-command name="blist">
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<syntax>blist [all|online|offline|away]</syntax>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<short-description>List all the buddies in your contact list</short-description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				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.
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		</description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 	</bitlbee-command>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 	<bitlbee-command name="nick">
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<short-description>Change friendly name, nick</short-description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<syntax>nick &lt;connection&gt; [&lt;new nick&gt;]</syntax>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<syntax>nick</syntax>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 				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.
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20060719165238-b8cfaccf380c8e17 
wilmer@gaast.net-20060719165238-b8cfaccf380c8e17 			<para>
wilmer@gaast.net-20060719165238-b8cfaccf380c8e17 				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.
wilmer@gaast.net-20060719165238-b8cfaccf380c8e17 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		</description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<ircexample>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<ircline nick="wouter">nick 1 "Wouter Paesen"</ircline>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<ircline nick="root">Setting your name on connection 1 to `Wouter Paesen'</ircline>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		</ircexample>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 	</bitlbee-command>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20070630215244-4zrlolzpsce04xqj 	<bitlbee-command name="join_chat">
wilmer@gaast.net-20070630215244-4zrlolzpsce04xqj 		<short-description>Join a named groupchat/conference room</short-description>
wilmer@gaast.net-20070630215244-4zrlolzpsce04xqj 		<syntax>import_buddies &lt;connection&gt; &lt;room name&gt; [&lt;channel name&gt;] [&lt;room nickname&gt;] [&lt;password&gt;]</syntax>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20051106182318-bcd0c40510635707 		<description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 			<para>
wilmer@gaast.net-20070630215244-4zrlolzpsce04xqj 				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.
wilmer@gaast.net-20070630215244-4zrlolzpsce04xqj 			</para>
wilmer@gaast.net-20070630215244-4zrlolzpsce04xqj 
wilmer@gaast.net-20070630215244-4zrlolzpsce04xqj 			<para>
wilmer@gaast.net-20070630215244-4zrlolzpsce04xqj 				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.
wilmer@gaast.net-20070630215244-4zrlolzpsce04xqj 			</para>
wilmer@gaast.net-20070630215244-4zrlolzpsce04xqj 
wilmer@gaast.net-20070630215244-4zrlolzpsce04xqj 			<para>
wilmer@gaast.net-20070630215244-4zrlolzpsce04xqj 				The following command will join you to the chatroom called <emphasis>bitlbee@conference.bitlbee.org</emphasis>. The channel will be called <emphasis>&amp;bitlbee-help</emphasis> because <emphasis>&amp;bitlbee</emphasis> will already be in use. Your nickname will be <emphasis>help-me</emphasis>.
wilmer@gaast.net-20051106182318-bcd0c40510635707 			</para>
wilmer@gaast.net-20051106182318-bcd0c40510635707 		</description>
wilmer@gaast.net-20051106182318-bcd0c40510635707 
wilmer@gaast.net-20070630215244-4zrlolzpsce04xqj 		<ircexample>
wilmer@gaast.net-20070630215244-4zrlolzpsce04xqj 			<ircline nick="wilmer">join_chat jabber bitlbee@conference.bitlbee.org &amp;bitlbee-help help-me</ircline>
wilmer@gaast.net-20070630215244-4zrlolzpsce04xqj 		</ircexample>
wilmer@gaast.net-20070630215244-4zrlolzpsce04xqj 
wilmer@gaast.net-20051106182318-bcd0c40510635707 	</bitlbee-command>
wilmer@gaast.net-20051106182318-bcd0c40510635707 </chapter>
end wilmer@gaast.net-20070630215244-4zrlolzpsce04xqj
version wilmer@gaast.net-20071010221559-rh4fi91i3quuwnjw 11 494cb91eaa2eb944842bc11a721ba5d6cf3701f1
597,597,10
wilmer@gaast.net-20071010221559-rh4fi91i3quuwnjw 	<bitlbee-setting name="simulate_netsplit" type="boolean" scope="global">
wilmer@gaast.net-20071010221559-rh4fi91i3quuwnjw 		<default>true</default>
wilmer@gaast.net-20071010221559-rh4fi91i3quuwnjw 
wilmer@gaast.net-20071010221559-rh4fi91i3quuwnjw 		<description>
wilmer@gaast.net-20071010221559-rh4fi91i3quuwnjw 			<para>
wilmer@gaast.net-20071010221559-rh4fi91i3quuwnjw 				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.
wilmer@gaast.net-20071010221559-rh4fi91i3quuwnjw 			</para>
wilmer@gaast.net-20071010221559-rh4fi91i3quuwnjw 		</description>
wilmer@gaast.net-20071010221559-rh4fi91i3quuwnjw 	</bitlbee-setting>
wilmer@gaast.net-20071010221559-rh4fi91i3quuwnjw 
end wilmer@gaast.net-20071010221559-rh4fi91i3quuwnjw
version wilmer@gaast.net-20071014225742-72ovmbq2zmoaxmof 2 ff031def01c1511785e07d8e74870641c3cdf382
824,825,1
wilmer@gaast.net-20071014225742-72ovmbq2zmoaxmof 		<syntax>join_chat &lt;connection&gt; &lt;room name&gt; [&lt;channel name&gt;] [&lt;room nickname&gt;] [&lt;password&gt;]</syntax>
end wilmer@gaast.net-20071014225742-72ovmbq2zmoaxmof
version wilmer@gaast.net-20071114232943-n0iwi7vhyjdlmig0 14 d058511c9078ae4443d88dc8e805d89493157f7d
682,682,13
wilmer@gaast.net-20071114232943-n0iwi7vhyjdlmig0 	<bitlbee-setting name="xmlconsole" type="boolean" scope="account">
wilmer@gaast.net-20071114232943-n0iwi7vhyjdlmig0 		<default>false</default>
wilmer@gaast.net-20071114232943-n0iwi7vhyjdlmig0 
wilmer@gaast.net-20071114232943-n0iwi7vhyjdlmig0 		<description>
wilmer@gaast.net-20071114232943-n0iwi7vhyjdlmig0 			<para>
wilmer@gaast.net-20071114232943-n0iwi7vhyjdlmig0 				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.
wilmer@gaast.net-20071114232943-n0iwi7vhyjdlmig0 			</para>
wilmer@gaast.net-20071114232943-n0iwi7vhyjdlmig0 			<para>
wilmer@gaast.net-20071114232943-n0iwi7vhyjdlmig0 				If you want to enable this XML console permanently (and at login time already), you can set this setting.
wilmer@gaast.net-20071114232943-n0iwi7vhyjdlmig0 			</para>
wilmer@gaast.net-20071114232943-n0iwi7vhyjdlmig0 		</description>
wilmer@gaast.net-20071114232943-n0iwi7vhyjdlmig0 	</bitlbee-setting>
wilmer@gaast.net-20071114232943-n0iwi7vhyjdlmig0 
end wilmer@gaast.net-20071114232943-n0iwi7vhyjdlmig0
version wilmer@gaast.net-20071114234207-5sea1o8nfvcv0kjh 2 a74f970382778fcf303a691e81f983fd8596aab6
837,838,1
wilmer@gaast.net-20071014225742-72ovmbq2zmoaxmof 		<syntax>join_chat &lt;connection&gt; &lt;room name&gt; [&lt;channel name&gt;] [&lt;room nickname&gt;] [&lt;password&gt;]</syntax>
end wilmer@gaast.net-20071114234207-5sea1o8nfvcv0kjh
version wilmer@gaast.net-20071117122051-dy3244fbeoiby5ek 11 a231effc5718707af660cae4127b9d2149d00c3b
135,135,1
wilmer@gaast.net-20071117122051-dy3244fbeoiby5ek 			<syntax>account set -del &lt;account id&gt;/&lt;setting&gt;</syntax>
142,143,1
wilmer@gaast.net-20071117122051-dy3244fbeoiby5ek 					For more infomation about a setting, see <emphasis>help set &lt;setting&gt;</emphasis>. For details about the syntax of this command, see <emphasis>help set</emphasis>.
247,248,4
wilmer@gaast.net-20071117122051-dy3244fbeoiby5ek 		<syntax>set</syntax>
wilmer@gaast.net-20071117122051-dy3244fbeoiby5ek 		<syntax>set &lt;variable&gt;</syntax>
wilmer@gaast.net-20071117122051-dy3244fbeoiby5ek 		<syntax>set &lt;variable&gt; &lt;value&gt;</syntax>
wilmer@gaast.net-20071117122051-dy3244fbeoiby5ek 		<syntax>set -del &lt;variable&gt;</syntax>
252,253,1
wilmer@gaast.net-20071117122051-dy3244fbeoiby5ek 				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.
end wilmer@gaast.net-20071117122051-dy3244fbeoiby5ek
version wilmer@gaast.net-20071119231618-z1iiz441uo5hpgmq 11 f24c54ce4e7428914d7b947f7862493c70db224c
135,135,1
wilmer@gaast.net-20071117122051-dy3244fbeoiby5ek 			<syntax>account set -del &lt;account id&gt;/&lt;setting&gt;</syntax>
142,143,1
wilmer@gaast.net-20071117122051-dy3244fbeoiby5ek 					For more infomation about a setting, see <emphasis>help set &lt;setting&gt;</emphasis>. For details about the syntax of this command, see <emphasis>help set</emphasis>.
247,248,4
wilmer@gaast.net-20071117122051-dy3244fbeoiby5ek 		<syntax>set</syntax>
wilmer@gaast.net-20071117122051-dy3244fbeoiby5ek 		<syntax>set &lt;variable&gt;</syntax>
wilmer@gaast.net-20071117122051-dy3244fbeoiby5ek 		<syntax>set &lt;variable&gt; &lt;value&gt;</syntax>
wilmer@gaast.net-20071117122051-dy3244fbeoiby5ek 		<syntax>set -del &lt;variable&gt;</syntax>
252,253,1
wilmer@gaast.net-20071117122051-dy3244fbeoiby5ek 				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.
end wilmer@gaast.net-20071119231618-z1iiz441uo5hpgmq
version wilmer@gaast.net-20071212233051-fn8bh4aytsx0hiz9 12 3cdfe57e7728962a735ae64f392bfd7069de503a
18,19,1
wilmer@gaast.net-20071212233051-fn8bh4aytsx0hiz9 			<syntax>account add &lt;protocol&gt; &lt;username&gt; &lt;password&gt;</syntax>
27,28,1
wilmer@gaast.net-20071212233051-fn8bh4aytsx0hiz9 				<syntax>account add jabber &lt;handle@server.tld&gt; &lt;password&gt;</syntax>
51,52,1
wilmer@gaast.net-20071212233051-fn8bh4aytsx0hiz9 				<syntax>account add oscar &lt;handle&gt; &lt;password&gt;</syntax>
55,56,1
wilmer@gaast.net-20071212233051-fn8bh4aytsx0hiz9 						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.
60,61,1
wilmer@gaast.net-20071212233051-fn8bh4aytsx0hiz9 					<ircline nick="wilmer">account add oscar 72696705 hobbelmeeuw</ircline>
596,597,1
wilmer@gaast.net-20071212233051-fn8bh4aytsx0hiz9 				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.
end wilmer@gaast.net-20071212233051-fn8bh4aytsx0hiz9
version wilmer@gaast.net-20080105211532-ob9a3ghyrjdd6m44 12 cecacc389518ae72d44faca02b9cc36f5c08db12
476,476,11
wilmer@gaast.net-20080105211532-ob9a3ghyrjdd6m44 	<bitlbee-setting name="mail_notifications" type="boolean" scope="account">
wilmer@gaast.net-20080105211532-ob9a3ghyrjdd6m44 		<default>false</default>
wilmer@gaast.net-20080105211532-ob9a3ghyrjdd6m44 
wilmer@gaast.net-20080105211532-ob9a3ghyrjdd6m44 		<description>
wilmer@gaast.net-20080105211532-ob9a3ghyrjdd6m44 			<para>
wilmer@gaast.net-20080105211532-ob9a3ghyrjdd6m44 				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.
wilmer@gaast.net-20080105211532-ob9a3ghyrjdd6m44 			</para>
wilmer@gaast.net-20080105211532-ob9a3ghyrjdd6m44 		</description>
wilmer@gaast.net-20080105211532-ob9a3ghyrjdd6m44 
wilmer@gaast.net-20080105211532-ob9a3ghyrjdd6m44 	</bitlbee-setting>
wilmer@gaast.net-20080105211532-ob9a3ghyrjdd6m44 
end wilmer@gaast.net-20080105211532-ob9a3ghyrjdd6m44
version wilmer@gaast.net-20080228223937-hsopsc13n610553c 3 4258836678fe33fbec6729899b91a364ee76ed42
844,846,2
wilmer@gaast.net-20080228223937-hsopsc13n610553c 			<ircline nick="wouter">account set 1/display_name "The majestik møøse"</ircline>
wilmer@gaast.net-20080228223937-hsopsc13n610553c 			<ircline nick="root">display_name = `The majestik møøse'</ircline>
end wilmer@gaast.net-20080228223937-hsopsc13n610553c
version wilmer@gaast.net-20080302221206-536f5q1nzk5m22a2 14 b9e51a0848a00926ba93a3f64eb1de254f4a6dad
164,169,1
wilmer@gaast.net-20080302221206-536f5q1nzk5m22a2 				If you want, you can also tell BitlBee what nick to give the new contact. The -tmp option adds the buddy to the internal BitlBee structures only, not to the real contact list (like done by <emphasis>set handle_unknown add</emphasis>). This allows you to talk to people who are not in your contact list. This normally won't show you any presence notifications.
384,385,1
wilmer@gaast.net-20080302221206-536f5q1nzk5m22a2 		<default>utf-8</default>
389,390,1
wilmer@gaast.net-20080302221206-536f5q1nzk5m22a2 				This setting tells BitlBee what your IRC client sends and expects. It should be equal to the charset setting of your IRC client if you want to be able to send and receive non-ASCII text properly.
393,394,1
wilmer@gaast.net-20080302221206-536f5q1nzk5m22a2 				Most systems use UTF-8 these days. On older systems, an iso8859 charset may work better. For example, iso8859-1 is the best choice for most Western countries. You can try to find what works best for you on http://www.unicodecharacter.com/charsets/iso8859.html
678,679,1
wilmer@gaast.net-20080302221206-536f5q1nzk5m22a2 				Sends you a /notice when a user starts typing a message (if supported by the IM protocol and the user's client). To use this, you most likely want to use a script in your IRC client to show this information in a more sensible way.
831,832,1
wilmer@gaast.net-20080302221206-536f5q1nzk5m22a2 		<syntax>nick &lt;connection&gt;</syntax>
835,840,1
wilmer@gaast.net-20080302221206-536f5q1nzk5m22a2 				Deprecated: Use the per-account <emphasis>display_name</emphasis> setting to read and change this information.
end wilmer@gaast.net-20080302221206-536f5q1nzk5m22a2
version wilmer@gaast.net-20080405130331-6vlt92xpyv3htddj 11 a0b11c0ddaff2c66c8f9e4d926517dd58cfa3c23
590,590,10
wilmer@gaast.net-20080405130331-6vlt92xpyv3htddj 	<bitlbee-setting name="root_nick" type="string" scope="global">
wilmer@gaast.net-20080405130331-6vlt92xpyv3htddj 		<default>root</default>
wilmer@gaast.net-20080405130331-6vlt92xpyv3htddj 
wilmer@gaast.net-20080405130331-6vlt92xpyv3htddj 		<description>
wilmer@gaast.net-20080405130331-6vlt92xpyv3htddj 			<para>
wilmer@gaast.net-20080405130331-6vlt92xpyv3htddj 				Normally the "bot" that takes all your BitlBee commands is called "root". If you don't like this name, you can rename it to anything else using the <emphasis>rename</emphasis> command, or by changing this setting.
wilmer@gaast.net-20080405130331-6vlt92xpyv3htddj 			</para>
wilmer@gaast.net-20080405130331-6vlt92xpyv3htddj 		</description>
wilmer@gaast.net-20080405130331-6vlt92xpyv3htddj 	</bitlbee-setting>
wilmer@gaast.net-20080405130331-6vlt92xpyv3htddj 
end wilmer@gaast.net-20080405130331-6vlt92xpyv3htddj
version wilmer@gaast.net-20080809230038-b59qrpai565hnmit 9 5dc0f5e74d31e4415867edd0463a684a53ae238a
322,324,2
wilmer@gaast.net-20080809230038-b59qrpai565hnmit 	<bitlbee-setting name="auto_reconnect_delay" type="string" scope="global">
wilmer@gaast.net-20080809230038-b59qrpai565hnmit 		<default>5*3&lt;900</default>
327,328,5
wilmer@gaast.net-20080809230038-b59qrpai565hnmit 				Tell BitlBee after how many seconds it should attempt to bring a broken IM-connection back up.
wilmer@gaast.net-20080809230038-b59qrpai565hnmit 			</para>
wilmer@gaast.net-20080809230038-b59qrpai565hnmit 
wilmer@gaast.net-20080809230038-b59qrpai565hnmit 			<para>
wilmer@gaast.net-20080809230038-b59qrpai565hnmit 				This can be one integer, for a constant delay. One can also set it to something like &quot;10*10&quot;, which means wait for ten seconds on the first reconnect, multiply it by ten on every failure. Once successfully connected, this delay is re-set to the initial value. With &lt; you can give a maximum delay.
end wilmer@gaast.net-20080809230038-b59qrpai565hnmit
version wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 111 da5fb808b9a3e6e252d13bcb39e9ffa3ac21bd88
126,127,1
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 					This command gives you a list of all the accounts known by BitlBee.
139,140,1
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 					This command can be used to change various settings for IM accounts. For all protocols, this command can be used to change the handle or the password BitlBee uses to log in and if it should be logged in automatically. Some protocols have additional settings. You can see the settings available for a connection by typing <emphasis>account set &lt;account id&gt;</emphasis>.
143,144,1
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 					For more infomation about a setting, see <emphasis>help set &lt;setting&gt;</emphasis>.
153,153,83
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 	<bitlbee-command name="chat">
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 		<short-description>Chatroom list maintenance</short-description>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 		<syntax>chat &lt;action&gt; [&lt;arguments&gt;]</syntax>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 		<description>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 			<para>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 				Available actions: add, del, list, with and set. See <emphasis>help chat &lt;action&gt;</emphasis> for more information.
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 			</para>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 		</description>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 		<bitlbee-command name="add">
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 			<syntax>chat add &lt;account&gt; &lt;room&gt; [&lt;channel&gt;]</syntax>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 			<description>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 				<para>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 					Add a chatroom to the list of chatrooms you're interested in. BitlBee needs this list to map room names to a proper IRC channel name.
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 				</para>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 				<para>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 					After adding a room to your list, you can simply use the IRC /join command to enter the room. Also, you can tell BitlBee to automatically join the room when you log in. (See <emphasis>chat set</emphasis>)
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 				</para>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 			</description>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 		</bitlbee-command>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 		<bitlbee-command name="del">
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 			<syntax>chat del &lt;chat id&gt;</syntax>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 			<description>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 				<para>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 					This commands deletes an chatroom from your list.
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 				</para>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 				<para>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 					The room ID can be a number (see <emphasis>chat list</emphasis>), or (part of) the name of the room/channel.
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 				</para>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 			</description>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 		</bitlbee-command>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 		<bitlbee-command name="list">
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 			<syntax>chat list</syntax>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 			<description>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 				<para>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 					This command gives you a list of all the chatrooms known by BitlBee.
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 				</para>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 			</description>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 		</bitlbee-command>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 		<bitlbee-command name="with">
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 			<syntax>chat with &lt;nickname&gt;</syntax>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 			<description>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 				<para>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 					While most <emphasis>chat</emphasis> subcommands are about named chatrooms, this command can be used to open an unnamed groupchat with one or more persons. This command is what <emphasis>/join #nickname</emphasis> used to do in older BitlBee versions.
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 				</para>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 			</description>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 		</bitlbee-command>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 		<bitlbee-command name="set">
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 			<syntax>chat set &lt;chat id&gt;</syntax>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 			<syntax>chat set &lt;chat id&gt;/&lt;setting&gt;</syntax>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 			<syntax>chat set &lt;chat id&gt;/&lt;setting&gt; &lt;value&gt;</syntax>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 			<syntax>chat set -del &lt;chat id&gt;/&lt;setting&gt;</syntax>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 			<description>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 				<para>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 					This command can be used to change various settings for chatrooms.
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 				</para>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 				
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 				<para>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 					For more infomation about a setting, see <emphasis>help set &lt;setting&gt;</emphasis>.
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 				</para>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 				
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 				<para>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 					The room ID can be a number (see <emphasis>chat list</emphasis>), or (part of) the name of the room/channel.
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 				</para>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 			</description>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 		</bitlbee-command>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 	</bitlbee-command>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 
304,304,10
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 	<bitlbee-setting name="auto_join" type="boolean" scope="chat">
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 		<default>false</default>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 		<description>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 			<para>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 				With this option enabled, BitlBee will automatically join this chatroom when you log in.
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 			</para>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 		</description>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 	</bitlbee-setting>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 
487,487,9
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 	<bitlbee-setting name="nick" type="string" scope="chat">
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 		<description>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 			<para>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 				You can use this option to set your nickname in a chatroom. You won't see this nickname yourself, but other people in the room will. By default, BitlBee will use your username as the chatroom nickname.
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 			</para>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 		</description>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 	</bitlbee-setting>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 
end wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9
version wilmer@gaast.net-20080831233427-upzwwdfv8jop9wj4 1 e3e1d5f1d8bf9addece855952dc8e97b411e87cf
957,981,0
end wilmer@gaast.net-20080831233427-upzwwdfv8jop9wj4
version wilmer@gaast.net-20080831233756-y6zq7vrr2odl13if 1 e3e1d5f1d8bf9addece855952dc8e97b411e87cf
957,981,0
end wilmer@gaast.net-20080831233756-y6zq7vrr2odl13if
version wilmer@gaast.net-20090113185928-rh3gmzgunxogcicn 4 6f473cf18903b046fbe4d88a7ab264007abb0ba2
683,684,1
wilmer@gaast.net-20090113185928-rh3gmzgunxogcicn 		<possible-values>priority, activity</possible-values>
691,692,1
wilmer@gaast.net-20090113185928-rh3gmzgunxogcicn 				Normally it's set to <emphasis>priority</emphasis> which means messages will always be delivered to the buddy's resource with the highest priority. If the setting is set to <emphasis>activity</emphasis>, messages will be delivered to the resource that was last used to send you a message (or the resource that most recently connected).
end wilmer@gaast.net-20090113185928-rh3gmzgunxogcicn
version wilmer@gaast.net-20091017150430-s1x3fv9a3j6l2ehg 5 3342f75a8fa8a0612430b4abc814860b2e9b1b9d
176,176,4
wilmer@gaast.net-20091017150430-s1x3fv9a3j6l2ehg 
wilmer@gaast.net-20091017150430-s1x3fv9a3j6l2ehg 				<para>
wilmer@gaast.net-20091017150430-s1x3fv9a3j6l2ehg 					Password-protected rooms work exactly like on IRC, by passing the password as an extra argument to /join.
wilmer@gaast.net-20091017150430-s1x3fv9a3j6l2ehg 				</para>
end wilmer@gaast.net-20091017150430-s1x3fv9a3j6l2ehg
version a.sporto+bee@gmail.com-20071203142845-a01twmtobeitsnpm 44 65cbfead2504750d1da29b2e5ce52bd0f024a9ee
862,862,43
a.sporto+bee@gmail.com-20071203142845-a01twmtobeitsnpm 	
a.sporto+bee@gmail.com-20071203142845-a01twmtobeitsnpm 	<bitlbee-command name="transfers">
a.sporto+bee@gmail.com-20071203142845-a01twmtobeitsnpm 		<short-description>Monitor, cancel, or reject file transfers</short-description>
a.sporto+bee@gmail.com-20071203142845-a01twmtobeitsnpm 		<syntax>transfers [&lt;cancel&gt; id | &lt;reject&gt;]</syntax>
a.sporto+bee@gmail.com-20071203142845-a01twmtobeitsnpm 		
a.sporto+bee@gmail.com-20071203142845-a01twmtobeitsnpm 		<description>
a.sporto+bee@gmail.com-20071203142845-a01twmtobeitsnpm 			<para>
a.sporto+bee@gmail.com-20071203142845-a01twmtobeitsnpm 				Without parameters the currently pending file transfers and their status will be listed. Available actions are <emphasis>cancel</emphasis> and <emphasis>reject</emphasis>. See <emphasis>help transfers &lt;action&gt;</emphasis> for more information.
a.sporto+bee@gmail.com-20071203142845-a01twmtobeitsnpm 			</para>
a.sporto+bee@gmail.com-20071203142845-a01twmtobeitsnpm 
a.sporto+bee@gmail.com-20071203142845-a01twmtobeitsnpm 			<ircexample>
a.sporto+bee@gmail.com-20071203142845-a01twmtobeitsnpm 				<ircline nick="ulim">transfers</ircline>
a.sporto+bee@gmail.com-20071203142845-a01twmtobeitsnpm 			</ircexample>
a.sporto+bee@gmail.com-20071203142845-a01twmtobeitsnpm 		</description>
a.sporto+bee@gmail.com-20071203142845-a01twmtobeitsnpm 		
a.sporto+bee@gmail.com-20071203142845-a01twmtobeitsnpm 		<bitlbee-command name="cancel">
a.sporto+bee@gmail.com-20071203142845-a01twmtobeitsnpm 			<short-description>Cancels the file transfer with the given id</short-description>
a.sporto+bee@gmail.com-20071203142845-a01twmtobeitsnpm 			<syntax>transfers &lt;cancel&gt; id</syntax>
a.sporto+bee@gmail.com-20071203142845-a01twmtobeitsnpm 
a.sporto+bee@gmail.com-20071203142845-a01twmtobeitsnpm 			<description>
a.sporto+bee@gmail.com-20071203142845-a01twmtobeitsnpm 				<para>Cancels the file transfer with the given id</para>
a.sporto+bee@gmail.com-20071203142845-a01twmtobeitsnpm 			</description>
a.sporto+bee@gmail.com-20071203142845-a01twmtobeitsnpm 
a.sporto+bee@gmail.com-20071203142845-a01twmtobeitsnpm 			<ircexample>
a.sporto+bee@gmail.com-20071203142845-a01twmtobeitsnpm 				<ircline nick="ulim">transfers cancel 1</ircline>
a.sporto+bee@gmail.com-20071203142845-a01twmtobeitsnpm 				<ircline nick="root">Canceling file transfer for test</ircline>
a.sporto+bee@gmail.com-20071203142845-a01twmtobeitsnpm 			</ircexample>
a.sporto+bee@gmail.com-20071203142845-a01twmtobeitsnpm 		</bitlbee-command>
a.sporto+bee@gmail.com-20071203142845-a01twmtobeitsnpm 
a.sporto+bee@gmail.com-20071203142845-a01twmtobeitsnpm 		<bitlbee-command name="reject">
a.sporto+bee@gmail.com-20071203142845-a01twmtobeitsnpm 			<short-description>Rejects all incoming transfers</short-description>
a.sporto+bee@gmail.com-20071203142845-a01twmtobeitsnpm 			<syntax>transfers &lt;reject&gt;</syntax>
a.sporto+bee@gmail.com-20071203142845-a01twmtobeitsnpm 
a.sporto+bee@gmail.com-20071203142845-a01twmtobeitsnpm 			<description>
a.sporto+bee@gmail.com-20071203142845-a01twmtobeitsnpm 				<para>Rejects all incoming (not already transferring) file transfers. Since you probably have only one incoming transfer at a time, no id is neccessary. Or is it?</para>
a.sporto+bee@gmail.com-20071203142845-a01twmtobeitsnpm 			</description>
a.sporto+bee@gmail.com-20071203142845-a01twmtobeitsnpm 
a.sporto+bee@gmail.com-20071203142845-a01twmtobeitsnpm 			<ircexample>
a.sporto+bee@gmail.com-20071203142845-a01twmtobeitsnpm 				<ircline nick="ulim">transfers reject</ircline>
a.sporto+bee@gmail.com-20071203142845-a01twmtobeitsnpm 			</ircexample>
a.sporto+bee@gmail.com-20071203142845-a01twmtobeitsnpm 		</bitlbee-command>
a.sporto+bee@gmail.com-20071203142845-a01twmtobeitsnpm 	</bitlbee-command>
a.sporto+bee@gmail.com-20071203142845-a01twmtobeitsnpm 	
end a.sporto+bee@gmail.com-20071203142845-a01twmtobeitsnpm
version kenobi@rhea-20071218235935-utpyo7hoo9imtr2c 12 663c81e9ee4be345cc746426c32fa8cfa89582b6
18,19,1
kenobi@rhea-20071218235935-utpyo7hoo9imtr2c 			<syntax>account add &lt;protocol&gt; &lt;username&gt; &lt;password&gt;</syntax>
27,28,1
kenobi@rhea-20071218235935-utpyo7hoo9imtr2c 				<syntax>account add jabber &lt;handle@server.tld&gt; &lt;password&gt;</syntax>
51,52,1
kenobi@rhea-20071218235935-utpyo7hoo9imtr2c 				<syntax>account add oscar &lt;handle&gt; &lt;password&gt;</syntax>
55,56,1
kenobi@rhea-20071218235935-utpyo7hoo9imtr2c 						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.
60,61,1
kenobi@rhea-20071218235935-utpyo7hoo9imtr2c 					<ircline nick="wilmer">account add oscar 72696705 hobbelmeeuw</ircline>
596,597,1
kenobi@rhea-20071218235935-utpyo7hoo9imtr2c 				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.
end kenobi@rhea-20071218235935-utpyo7hoo9imtr2c
version a.sporto+bee@gmail.com-20080215173857-19ptd7cwwi4e1jic 44 ea415d5b7fca209b8641308baa9f2273e128262a
873,873,43
a.sporto+bee@gmail.com-20071203142845-a01twmtobeitsnpm 	
a.sporto+bee@gmail.com-20071203142845-a01twmtobeitsnpm 	<bitlbee-command name="transfers">
a.sporto+bee@gmail.com-20071203142845-a01twmtobeitsnpm 		<short-description>Monitor, cancel, or reject file transfers</short-description>
a.sporto+bee@gmail.com-20071203142845-a01twmtobeitsnpm 		<syntax>transfers [&lt;cancel&gt; id | &lt;reject&gt;]</syntax>
a.sporto+bee@gmail.com-20071203142845-a01twmtobeitsnpm 		
a.sporto+bee@gmail.com-20071203142845-a01twmtobeitsnpm 		<description>
a.sporto+bee@gmail.com-20071203142845-a01twmtobeitsnpm 			<para>
a.sporto+bee@gmail.com-20071203142845-a01twmtobeitsnpm 				Without parameters the currently pending file transfers and their status will be listed. Available actions are <emphasis>cancel</emphasis> and <emphasis>reject</emphasis>. See <emphasis>help transfers &lt;action&gt;</emphasis> for more information.
a.sporto+bee@gmail.com-20071203142845-a01twmtobeitsnpm 			</para>
a.sporto+bee@gmail.com-20071203142845-a01twmtobeitsnpm 
a.sporto+bee@gmail.com-20071203142845-a01twmtobeitsnpm 			<ircexample>
a.sporto+bee@gmail.com-20071203142845-a01twmtobeitsnpm 				<ircline nick="ulim">transfers</ircline>
a.sporto+bee@gmail.com-20071203142845-a01twmtobeitsnpm 			</ircexample>
a.sporto+bee@gmail.com-20071203142845-a01twmtobeitsnpm 		</description>
a.sporto+bee@gmail.com-20071203142845-a01twmtobeitsnpm 		
a.sporto+bee@gmail.com-20071203142845-a01twmtobeitsnpm 		<bitlbee-command name="cancel">
a.sporto+bee@gmail.com-20071203142845-a01twmtobeitsnpm 			<short-description>Cancels the file transfer with the given id</short-description>
a.sporto+bee@gmail.com-20071203142845-a01twmtobeitsnpm 			<syntax>transfers &lt;cancel&gt; id</syntax>
a.sporto+bee@gmail.com-20071203142845-a01twmtobeitsnpm 
a.sporto+bee@gmail.com-20071203142845-a01twmtobeitsnpm 			<description>
a.sporto+bee@gmail.com-20071203142845-a01twmtobeitsnpm 				<para>Cancels the file transfer with the given id</para>
a.sporto+bee@gmail.com-20071203142845-a01twmtobeitsnpm 			</description>
a.sporto+bee@gmail.com-20071203142845-a01twmtobeitsnpm 
a.sporto+bee@gmail.com-20071203142845-a01twmtobeitsnpm 			<ircexample>
a.sporto+bee@gmail.com-20071203142845-a01twmtobeitsnpm 				<ircline nick="ulim">transfers cancel 1</ircline>
a.sporto+bee@gmail.com-20071203142845-a01twmtobeitsnpm 				<ircline nick="root">Canceling file transfer for test</ircline>
a.sporto+bee@gmail.com-20071203142845-a01twmtobeitsnpm 			</ircexample>
a.sporto+bee@gmail.com-20071203142845-a01twmtobeitsnpm 		</bitlbee-command>
a.sporto+bee@gmail.com-20071203142845-a01twmtobeitsnpm 
a.sporto+bee@gmail.com-20071203142845-a01twmtobeitsnpm 		<bitlbee-command name="reject">
a.sporto+bee@gmail.com-20071203142845-a01twmtobeitsnpm 			<short-description>Rejects all incoming transfers</short-description>
a.sporto+bee@gmail.com-20071203142845-a01twmtobeitsnpm 			<syntax>transfers &lt;reject&gt;</syntax>
a.sporto+bee@gmail.com-20071203142845-a01twmtobeitsnpm 
a.sporto+bee@gmail.com-20071203142845-a01twmtobeitsnpm 			<description>
a.sporto+bee@gmail.com-20071203142845-a01twmtobeitsnpm 				<para>Rejects all incoming (not already transferring) file transfers. Since you probably have only one incoming transfer at a time, no id is neccessary. Or is it?</para>
a.sporto+bee@gmail.com-20071203142845-a01twmtobeitsnpm 			</description>
a.sporto+bee@gmail.com-20071203142845-a01twmtobeitsnpm 
a.sporto+bee@gmail.com-20071203142845-a01twmtobeitsnpm 			<ircexample>
a.sporto+bee@gmail.com-20071203142845-a01twmtobeitsnpm 				<ircline nick="ulim">transfers reject</ircline>
a.sporto+bee@gmail.com-20071203142845-a01twmtobeitsnpm 			</ircexample>
a.sporto+bee@gmail.com-20071203142845-a01twmtobeitsnpm 		</bitlbee-command>
a.sporto+bee@gmail.com-20071203142845-a01twmtobeitsnpm 	</bitlbee-command>
a.sporto+bee@gmail.com-20071203142845-a01twmtobeitsnpm 	
end a.sporto+bee@gmail.com-20080215173857-19ptd7cwwi4e1jic
version a.sporto+bee@gmail.com-20080414131053-x7o8w2fgi20cu0yv 28 83ea26747781b719f260b8b15de2c8a84e703821
164,169,1
wilmer@gaast.net-20080302221206-536f5q1nzk5m22a2 				If you want, you can also tell BitlBee what nick to give the new contact. The -tmp option adds the buddy to the internal BitlBee structures only, not to the real contact list (like done by <emphasis>set handle_unknown add</emphasis>). This allows you to talk to people who are not in your contact list. This normally won't show you any presence notifications.
384,385,1
wilmer@gaast.net-20080302221206-536f5q1nzk5m22a2 		<default>utf-8</default>
389,390,1
wilmer@gaast.net-20080302221206-536f5q1nzk5m22a2 				This setting tells BitlBee what your IRC client sends and expects. It should be equal to the charset setting of your IRC client if you want to be able to send and receive non-ASCII text properly.
393,394,1
wilmer@gaast.net-20080302221206-536f5q1nzk5m22a2 				Most systems use UTF-8 these days. On older systems, an iso8859 charset may work better. For example, iso8859-1 is the best choice for most Western countries. You can try to find what works best for you on http://www.unicodecharacter.com/charsets/iso8859.html
594,594,10
wilmer@gaast.net-20080405130331-6vlt92xpyv3htddj 	<bitlbee-setting name="root_nick" type="string" scope="global">
wilmer@gaast.net-20080405130331-6vlt92xpyv3htddj 		<default>root</default>
wilmer@gaast.net-20080405130331-6vlt92xpyv3htddj 
wilmer@gaast.net-20080405130331-6vlt92xpyv3htddj 		<description>
wilmer@gaast.net-20080405130331-6vlt92xpyv3htddj 			<para>
wilmer@gaast.net-20080405130331-6vlt92xpyv3htddj 				Normally the "bot" that takes all your BitlBee commands is called "root". If you don't like this name, you can rename it to anything else using the <emphasis>rename</emphasis> command, or by changing this setting.
wilmer@gaast.net-20080405130331-6vlt92xpyv3htddj 			</para>
wilmer@gaast.net-20080405130331-6vlt92xpyv3htddj 		</description>
wilmer@gaast.net-20080405130331-6vlt92xpyv3htddj 	</bitlbee-setting>
wilmer@gaast.net-20080405130331-6vlt92xpyv3htddj 
678,679,1
wilmer@gaast.net-20080302221206-536f5q1nzk5m22a2 				Sends you a /notice when a user starts typing a message (if supported by the IM protocol and the user's client). To use this, you most likely want to use a script in your IRC client to show this information in a more sensible way.
831,832,1
wilmer@gaast.net-20080302221206-536f5q1nzk5m22a2 		<syntax>nick &lt;connection&gt;</syntax>
835,840,1
wilmer@gaast.net-20080302221206-536f5q1nzk5m22a2 				Deprecated: Use the per-account <emphasis>display_name</emphasis> setting to read and change this information.
844,846,2
wilmer@gaast.net-20080228223937-hsopsc13n610553c 			<ircline nick="wouter">account set 1/display_name "The majestik møøse"</ircline>
wilmer@gaast.net-20080228223937-hsopsc13n610553c 			<ircline nick="root">display_name = `The majestik møøse'</ircline>
end a.sporto+bee@gmail.com-20080414131053-x7o8w2fgi20cu0yv
version a.sporto+bee@gmail.com-20080810104252-dtqyzhqzt467jnrg 9 7fddb343474490967d5c15ae1e5963bc6c3b9c95
322,324,2
wilmer@gaast.net-20080809230038-b59qrpai565hnmit 	<bitlbee-setting name="auto_reconnect_delay" type="string" scope="global">
wilmer@gaast.net-20080809230038-b59qrpai565hnmit 		<default>5*3&lt;900</default>
327,328,5
wilmer@gaast.net-20080809230038-b59qrpai565hnmit 				Tell BitlBee after how many seconds it should attempt to bring a broken IM-connection back up.
wilmer@gaast.net-20080809230038-b59qrpai565hnmit 			</para>
wilmer@gaast.net-20080809230038-b59qrpai565hnmit 
wilmer@gaast.net-20080809230038-b59qrpai565hnmit 			<para>
wilmer@gaast.net-20080809230038-b59qrpai565hnmit 				This can be one integer, for a constant delay. One can also set it to something like &quot;10*10&quot;, which means wait for ten seconds on the first reconnect, multiply it by ten on every failure. Once successfully connected, this delay is re-set to the initial value. With &lt; you can give a maximum delay.
end a.sporto+bee@gmail.com-20080810104252-dtqyzhqzt467jnrg
version wilmer@gaast.net-20091207215419-hmg3jj59bwtakf2p 120 036d86f7c2b8ce0726168657b63a50f348930d1f
126,127,1
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 					This command gives you a list of all the accounts known by BitlBee.
139,140,1
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 					This command can be used to change various settings for IM accounts. For all protocols, this command can be used to change the handle or the password BitlBee uses to log in and if it should be logged in automatically. Some protocols have additional settings. You can see the settings available for a connection by typing <emphasis>account set &lt;account id&gt;</emphasis>.
143,144,1
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 					For more infomation about a setting, see <emphasis>help set &lt;setting&gt;</emphasis>.
153,153,87
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 	<bitlbee-command name="chat">
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 		<short-description>Chatroom list maintenance</short-description>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 		<syntax>chat &lt;action&gt; [&lt;arguments&gt;]</syntax>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 		<description>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 			<para>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 				Available actions: add, del, list, with and set. See <emphasis>help chat &lt;action&gt;</emphasis> for more information.
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 			</para>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 		</description>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 		<bitlbee-command name="add">
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 			<syntax>chat add &lt;account&gt; &lt;room&gt; [&lt;channel&gt;]</syntax>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 			<description>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 				<para>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 					Add a chatroom to the list of chatrooms you're interested in. BitlBee needs this list to map room names to a proper IRC channel name.
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 				</para>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 				<para>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 					After adding a room to your list, you can simply use the IRC /join command to enter the room. Also, you can tell BitlBee to automatically join the room when you log in. (See <emphasis>chat set</emphasis>)
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 				</para>
wilmer@gaast.net-20091017150430-s1x3fv9a3j6l2ehg 
wilmer@gaast.net-20091017150430-s1x3fv9a3j6l2ehg 				<para>
wilmer@gaast.net-20091017150430-s1x3fv9a3j6l2ehg 					Password-protected rooms work exactly like on IRC, by passing the password as an extra argument to /join.
wilmer@gaast.net-20091017150430-s1x3fv9a3j6l2ehg 				</para>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 			</description>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 		</bitlbee-command>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 		<bitlbee-command name="del">
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 			<syntax>chat del &lt;chat id&gt;</syntax>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 			<description>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 				<para>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 					This commands deletes an chatroom from your list.
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 				</para>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 				<para>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 					The room ID can be a number (see <emphasis>chat list</emphasis>), or (part of) the name of the room/channel.
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 				</para>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 			</description>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 		</bitlbee-command>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 		<bitlbee-command name="list">
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 			<syntax>chat list</syntax>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 			<description>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 				<para>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 					This command gives you a list of all the chatrooms known by BitlBee.
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 				</para>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 			</description>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 		</bitlbee-command>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 		<bitlbee-command name="with">
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 			<syntax>chat with &lt;nickname&gt;</syntax>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 			<description>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 				<para>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 					While most <emphasis>chat</emphasis> subcommands are about named chatrooms, this command can be used to open an unnamed groupchat with one or more persons. This command is what <emphasis>/join #nickname</emphasis> used to do in older BitlBee versions.
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 				</para>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 			</description>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 		</bitlbee-command>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 		<bitlbee-command name="set">
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 			<syntax>chat set &lt;chat id&gt;</syntax>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 			<syntax>chat set &lt;chat id&gt;/&lt;setting&gt;</syntax>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 			<syntax>chat set &lt;chat id&gt;/&lt;setting&gt; &lt;value&gt;</syntax>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 			<syntax>chat set -del &lt;chat id&gt;/&lt;setting&gt;</syntax>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 			<description>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 				<para>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 					This command can be used to change various settings for chatrooms.
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 				</para>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 				
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 				<para>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 					For more infomation about a setting, see <emphasis>help set &lt;setting&gt;</emphasis>.
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 				</para>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 				
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 				<para>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 					The room ID can be a number (see <emphasis>chat list</emphasis>), or (part of) the name of the room/channel.
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 				</para>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 			</description>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 		</bitlbee-command>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 	</bitlbee-command>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 
304,304,10
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 	<bitlbee-setting name="auto_join" type="boolean" scope="chat">
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 		<default>false</default>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 		<description>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 			<para>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 				With this option enabled, BitlBee will automatically join this chatroom when you log in.
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 			</para>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 		</description>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 	</bitlbee-setting>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 
487,487,9
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 	<bitlbee-setting name="nick" type="string" scope="chat">
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 		<description>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 			<para>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 				You can use this option to set your nickname in a chatroom. You won't see this nickname yourself, but other people in the room will. By default, BitlBee will use your username as the chatroom nickname.
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 			</para>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 		</description>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 	</bitlbee-setting>
wilmer@gaast.net-20080831231932-w8pi0rga94hsbjc9 
581,582,1
wilmer@gaast.net-20090113185928-rh3gmzgunxogcicn 		<possible-values>priority, activity</possible-values>
589,590,1
wilmer@gaast.net-20090113185928-rh3gmzgunxogcicn 				Normally it's set to <emphasis>priority</emphasis> which means messages will always be delivered to the buddy's resource with the highest priority. If the setting is set to <emphasis>activity</emphasis>, messages will be delivered to the resource that was last used to send you a message (or the resource that most recently connected).
855,879,0
end wilmer@gaast.net-20091207215419-hmg3jj59bwtakf2p