Changes in doc/user-guide/commands.xml [cd428e4:eded1f7]
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
doc/user-guide/commands.xml
rcd428e4 reded1f7 17 17 18 18 <bitlbee-command name="add"> 19 <syntax>account add <protocol> <username> <password> [<server>]</syntax>19 <syntax>account add <protocol> <username> <password></syntax> 20 20 21 21 <description> … … 26 26 27 27 <bitlbee-command name="jabber"> 28 <syntax>account add jabber <handle@server.tld> <password> [<servertag>]</syntax>28 <syntax>account add jabber <handle@server.tld> <password></syntax> 29 29 30 30 <description> … … 50 50 51 51 <bitlbee-command name="oscar"> 52 <syntax>account add oscar <handle> <password> [<servername>]</syntax>52 <syntax>account add oscar <handle> <password></syntax> 53 53 54 54 <description> 55 55 <para> 56 Specifying a server is required for OSCAR, since OSCAR can be used for both ICQ- and AIM-connections. Although these days it's supposed to be possible to connect to ICQ via AIM-servers and vice versa, we like to stick with this separation for now. For ICQ connections, the servername is <emphasis>login.icq.com</emphasis>, for AIM connections it's <emphasis>login.oscar.aol.com</emphasis>.56 OSCAR is the protocol used to connect to AIM and/or ICQ. The servers will automatically detect if you're using a numeric or non-numeric username so there's no need to tell which network you want to connect to. 57 57 </para> 58 58 </description> 59 59 60 60 <ircexample> 61 <ircline nick="wilmer">account add oscar 72696705 hobbelmeeuw login.icq.com</ircline>61 <ircline nick="wilmer">account add oscar 72696705 hobbelmeeuw</ircline> 62 62 <ircline nick="root">Account successfully added</ircline> 63 63 </ircexample> … … 595 595 <description> 596 596 <para> 597 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.597 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. 598 598 </para> 599 599 </description> … … 681 681 <para> 682 682 Unless you really intend to use this feature somewhere (on forums or maybe a website), it's probably better to keep this setting disabled. 683 </para> 684 </description> 685 </bitlbee-setting> 686 687 <bitlbee-setting name="xmlconsole" type="boolean" scope="account"> 688 <default>false</default> 689 690 <description> 691 <para> 692 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. 693 </para> 694 <para> 695 If you want to enable this XML console permanently (and at login time already), you can set this setting. 683 696 </para> 684 697 </description> … … 848 861 849 862 </bitlbee-command> 863 864 <bitlbee-command name="transfers"> 865 <short-description>Monitor, cancel, or reject file transfers</short-description> 866 <syntax>transfers [<cancel> id | <reject>]</syntax> 867 868 <description> 869 <para> 870 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 <action></emphasis> for more information. 871 </para> 872 873 <ircexample> 874 <ircline nick="ulim">transfers</ircline> 875 </ircexample> 876 </description> 877 878 <bitlbee-command name="cancel"> 879 <short-description>Cancels the file transfer with the given id</short-description> 880 <syntax>transfers <cancel> id</syntax> 881 882 <description> 883 <para>Cancels the file transfer with the given id</para> 884 </description> 885 886 <ircexample> 887 <ircline nick="ulim">transfers cancel 1</ircline> 888 <ircline nick="root">Canceling file transfer for test</ircline> 889 </ircexample> 890 </bitlbee-command> 891 892 <bitlbee-command name="reject"> 893 <short-description>Rejects all incoming transfers</short-description> 894 <syntax>transfers <reject></syntax> 895 896 <description> 897 <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> 898 </description> 899 900 <ircexample> 901 <ircline nick="ulim">transfers reject</ircline> 902 </ircexample> 903 </bitlbee-command> 904 </bitlbee-command> 905 850 906 </chapter>
Note: See TracChangeset
for help on using the changeset viewer.