Changes in doc/user-guide/commands.xml [ee5c355:f7b44f2]
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
doc/user-guide/commands.xml
ree5c355 rf7b44f2 426 426 <default>false</default> 427 427 428 <para> 429 With this option enabled, root will inform you when someone in your buddy list changes his/her "friendly name". 430 </para> 428 <description> 429 <para> 430 With this option enabled, root will inform you when someone in your buddy list changes his/her "friendly name". 431 </para> 432 </description> 431 433 </bitlbee-setting> 432 434 … … 809 811 </bitlbee-command> 810 812 811 <bitlbee-command name=" import_buddies">812 <short-description> Copy local buddy list to server (normally only needed when upgrading)</short-description>813 <syntax>import_buddies <connection> [clear]</syntax>814 815 <description> 816 <para> 817 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.818 </para> 819 820 <para> 821 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.822 </para> 823 824 <para> 825 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.826 </para> 827 828 <para> 829 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.830 < /para>831 </ description>813 <bitlbee-command name="join_chat"> 814 <short-description>Join a named groupchat/conference room</short-description> 815 <syntax>import_buddies <connection> <room name> [<channel name>] [<room nickname>] [<password>]</syntax> 816 817 <description> 818 <para> 819 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. 820 </para> 821 822 <para> 823 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. 824 </para> 825 826 <para> 827 The following command will join you to the chatroom called <emphasis>bitlbee@conference.bitlbee.org</emphasis>. The channel will be called <emphasis>&bitlbee-help</emphasis> because <emphasis>&bitlbee</emphasis> will already be in use. Your nickname will be <emphasis>help-me</emphasis>. 828 </para> 829 </description> 830 831 <ircexample> 832 <ircline nick="wilmer">join_chat jabber bitlbee@conference.bitlbee.org &bitlbee-help help-me</ircline> 833 </ircexample> 832 834 833 835 </bitlbee-command>
Note: See TracChangeset
for help on using the changeset viewer.