aboutsummaryrefslogtreecommitdiffstats
path: root/doc/user-guide/commands.xml
diff options
context:
space:
mode:
Diffstat (limited to 'doc/user-guide/commands.xml')
-rw-r--r--doc/user-guide/commands.xml64
1 files changed, 63 insertions, 1 deletions
diff --git a/doc/user-guide/commands.xml b/doc/user-guide/commands.xml
index aa88eb3a..1a07c835 100644
--- a/doc/user-guide/commands.xml
+++ b/doc/user-guide/commands.xml
@@ -584,6 +584,22 @@
</description>
</bitlbee-setting>
+ <bitlbee-setting name="away" type="string" scope="both">
+ <description>
+ <para>
+ To mark yourself as away, it is recommended to just use <emphasis>/away</emphasis>, like on normal IRC networks. If you want to mark yourself as away on only one IM network, you can use this per-account setting.
+ </para>
+
+ <para>
+ You can set it to any value and BitlBee will try to map it to the most appropriate away state for every open IM connection, or set it as a free-form away message where possible.
+ </para>
+
+ <para>
+ Any per-account away setting will override globally set away states. To un-set the setting, use <emphasis>set -del away</emphasis>.
+ </para>
+ </description>
+ </bitlbee-setting>
+
<bitlbee-setting name="away_devoice" type="boolean" scope="global">
<default>true</default>
@@ -817,6 +833,36 @@
</description>
</bitlbee-setting>
+ <bitlbee-setting name="nick_source" type="string" scope="account">
+ <default>handle</default>
+ <possible-values>handle, full_name, first_name</possible-values>
+
+ <description>
+ <para>
+ By default, BitlBee generates a nickname for every contact by taking its handle and chopping off everything after the @. In some cases, this gives very inconvenient nicknames. The Facebook XMPP server is a good example, as all Facebook XMPP handles are numeric.
+ </para>
+
+ <para>
+ With this setting set to <emphasis>full_name</emphasis>, the person's full name is used to generate a nickname. Or if you don't like long nicknames, set this setting to <emphasis>first_name</emphasis> instead and only the first word will be used. Note that the full name can be full of non-ASCII characters which will be stripped off.
+ </para>
+ </description>
+ </bitlbee-setting>
+
+ <bitlbee-setting name="ops" type="string" scope="global">
+ <default>both</default>
+ <possible-values>both, root, user, none</possible-values>
+
+ <description>
+ <para>
+ 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.
+ </para>
+
+ <para>
+ 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.
+ </para>
+ </description>
+ </bitlbee-setting>
+
<bitlbee-setting name="password" type="string" scope="both">
<description>
<para>
@@ -895,7 +941,7 @@
</bitlbee-setting>
<bitlbee-setting name="resource_select" type="string" scope="account">
- <default>priority</default>
+ <default>activity</default>
<possible-values>priority, activity</possible-values>
<description>
@@ -957,6 +1003,22 @@
</description>
</bitlbee-setting>
+ <bitlbee-setting name="status" type="string" scope="both">
+ <description>
+ <para>
+ Certain protocols (like Jabber/XMPP) support status messages, similar to away messages. They can be used to indicate things like your location or activity, without showing up as away/busy.
+ </para>
+
+ <para>
+ This setting can be used to set such a message. It will be available as a per-account setting for protocols that support it, and also as a global setting (which will then automatically be used for all protocols that support it).
+ </para>
+
+ <para>
+ Away states set using <emphasis>/away</emphasis> or the <emphasis>away</emphasis> setting will override this setting. To un-set the setting, use <emphasis>set -del status</emphasis>.
+ </para>
+ </description>
+ </bitlbee-setting>
+
<bitlbee-setting name="strip_html" type="boolean" scope="global">
<default>true</default>