Ignore:
File:
1 edited

Legend:

Unmodified
Added
Removed

  • doc/user-guide/commands.xml

    r2ff2076 rcd428e4  
    685685        </bitlbee-setting>
    686686
    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.
    696                         </para>
    697                 </description>
    698         </bitlbee-setting>
    699 
    700687        <bitlbee-command name="rename">
    701688                <short-description>Rename (renick) a buddy</short-description>
    … …  
    861848
    862849        </bitlbee-command>
    863        
    864         <bitlbee-command name="transfers">
    865                 <short-description>Monitor, cancel, or reject file transfers</short-description>
    866                 <syntax>transfers [&lt;cancel&gt; id | &lt;reject&gt;]</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 &lt;action&gt;</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 &lt;cancel&gt; 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 &lt;reject&gt;</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        
    906850</chapter>
Note: See TracChangeset for help on using the changeset viewer.