Changes in doc/user-guide/commands.xml [3e57660:57d8421]
- File:
-
- 1 edited
-
doc/user-guide/commands.xml (modified) (8 diffs)
Legend:
- Unmodified
- Added
- Removed
-
doc/user-guide/commands.xml
r3e57660 r57d8421 436 436 </bitlbee-setting> 437 437 438 <bitlbee-setting name="away" type="string" scope="both">439 <description>440 <para>441 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.442 </para>443 444 <para>445 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.446 </para>447 448 <para>449 Any per-account away setting will override globally set away states. To un-set the setting, use <emphasis>set -del away</emphasis>.450 </para>451 </description>452 </bitlbee-setting>453 454 438 <bitlbee-setting name="away_devoice" type="boolean" scope="global"> 455 439 <default>true</default> … … 509 493 </description> 510 494 511 </bitlbee-setting>512 513 <bitlbee-setting name="control_channel" type="string" scope="global">514 <default>&bitlbee</default>515 516 <description>517 <para>518 Normally the control channel where you can see all your contacts is called "&bitlbee". 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.519 </para>520 </description>521 495 </bitlbee-setting> 522 496 … … 587 561 </bitlbee-setting> 588 562 589 <bitlbee-setting name="ignore_auth_requests" type="boolean" scope="account">590 <default>true</default>591 592 <description>593 <para>594 Only supported by OSCAR so far, you can use this setting to ignore ICQ authorization requests, which are hardly used for legitimate (i.e. non-spam) reasons anymore.595 </para>596 </description>597 598 </bitlbee-setting>599 600 563 <bitlbee-setting name="lcnicks" type="boolean" scope="global"> 601 564 <default>true</default> … … 609 572 </bitlbee-setting> 610 573 611 <bitlbee-setting name="local_display_name" type="boolean" scope="account">612 <default>false</default>613 614 <description>615 <para>616 Mostly meant to work around a bug in MSN servers (forgetting the display name set by the user), this setting tells BitlBee to store your display name locally and set this name on the MSN servers when connecting.617 </para>618 </description>619 620 </bitlbee-setting>621 622 574 <bitlbee-setting name="mail_notifications" type="boolean" scope="account"> 623 575 <default>false</default> … … 636 588 <para> 637 589 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. 638 </para>639 </description>640 </bitlbee-setting>641 642 <bitlbee-setting name="nick_source" type="string" scope="account">643 <default>handle</default>644 <possible-values>handle, full_name, first_name</possible-values>645 646 <description>647 <para>648 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.649 </para>650 651 <para>652 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.653 590 </para> 654 591 </description> … … 748 685 749 686 <bitlbee-setting name="resource_select" type="string" scope="account"> 750 <default> activity</default>687 <default>priority</default> 751 688 <possible-values>priority, activity</possible-values> 752 689 … … 810 747 </bitlbee-setting> 811 748 812 <bitlbee-setting name="status" type="string" scope="both">813 <description>814 <para>815 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.816 </para>817 818 <para>819 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).820 </para>821 822 <para>823 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>.824 </para>825 </description>826 </bitlbee-setting>827 828 749 <bitlbee-setting name="strip_html" type="boolean" scope="global"> 829 750 <default>true</default> … … 835 756 <para> 836 757 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. 837 </para>838 </description>839 </bitlbee-setting>840 841 <bitlbee-setting name="timezone" type="string" scope="global">842 <default>local</default>843 <possible-values>local, utc, gmt, timezone-spec</possible-values>844 845 <description>846 <para>847 If message timestamps are available for offline messages or chatroom backlogs, BitlBee will display them as part of the message. By default it will use the local timezone. If you're not in the same timezone as the BitlBee server, you can adjust the timestamps using this setting.848 </para>849 850 <para>851 Values local/utc/gmt should be self-explanatory. timezone-spec is a time offset in hours:minutes, for example: -8 for Pacific Standard Time, +2 for Central European Summer Time, +5:30 for Indian Standard Time.852 758 </para> 853 759 </description>
Note: See TracChangeset
for help on using the changeset viewer.
