Changeset 537d9b9 for doc/user-guide/commands.xml
- Timestamp:
- 2016-11-20T08:40:36Z (7 years ago)
- Children:
- 3f44e43
- Parents:
- ba52ac5 (diff), 9f03c47 (diff)
Note: this is a merge changeset, the changes displayed below correspond to the merge itself.
Use the(diff)links above to see all the changes relative to each parent. - File:
-
- 1 edited
-
doc/user-guide/commands.xml (modified) (9 diffs)
Legend:
- Unmodified
- Added
- Removed
-
doc/user-guide/commands.xml
rba52ac5 r537d9b9 258 258 259 259 <para> 260 Available actions: add, with . See <emphasis>help chat <action></emphasis> for more information.260 Available actions: add, with, list. See <emphasis>help chat <action></emphasis> for more information. 261 261 </para> 262 262 … … 264 264 265 265 <bitlbee-command name="add"> 266 <syntax>chat add <account id> <room > [<channel>]</syntax>266 <syntax>chat add <account id> <room|!index> [<channel>]</syntax> 267 267 268 268 <description> … … 272 272 273 273 <para> 274 After adding a room to your list, you can simply use the IRC /join command to enter the room. Also, you can tell BitlBee to automatically join the room when you log in. ( See <emphasis>chat set</emphasis>)274 After adding a room to your list, you can simply use the IRC /join command to enter the room. Also, you can tell BitlBee to automatically join the room when you log in. (<emphasis>channel <channel> set auto_join true</emphasis>) 275 275 </para> 276 276 … … 280 280 </description> 281 281 282 </bitlbee-command> 283 284 <bitlbee-command name="list"> 285 <syntax>chat list <account id> [<server>]</syntax> 286 287 <description> 288 <para> 289 List existing chatrooms provided by an account. BitlBee needs this to propogate an internal list of chats. The existing chat can then be added with <emphasis>chat add</emphasis>, using the number in the index column after a "!" as a shortcut. 290 </para> 291 </description> 292 293 <ircexample> 294 <ircline nick="dx">chat list facebook</ircline> 295 <ircline pre="1" nick="root">Index Title Topic</ircline> 296 <ircline pre="1" nick="root"> 1 869891016470949 cool kids club</ircline> 297 <ircline pre="1" nick="root"> 2 457892181062459 uncool kids club</ircline> 298 <ircline nick="root">2 facebook chatrooms</ircline> 299 <ircline nick="dx">chat add facebook !1 #cool-kids-club</ircline> 300 </ircexample> 282 301 </bitlbee-command> 283 302 … … 288 307 <para> 289 308 While most <emphasis>chat</emphasis> subcommands are about named chatrooms, this command can be used to open an unnamed groupchat with one or more persons. This command is what <emphasis>/join #nickname</emphasis> used to do in older BitlBee versions. 309 </para> 310 311 <para> 312 Another way to do this is to join to a new, empty channel with <emphasis>/join #newchannel</emphasis> and invite the first person with <emphasis>/invite nickname</emphasis> 290 313 </para> 291 314 </description> … … 645 668 <para> 646 669 When you're already connected to a BitlBee server and you connect (and identify) again, BitlBee will offer to migrate your existing session to the new connection. If for whatever reason you don't want this, you can disable this setting. 670 </para> 671 </description> 672 </bitlbee-setting> 673 674 <bitlbee-setting name="always_use_nicks" type="boolean" scope="channel"> 675 <default>false</default> 676 677 <description> 678 <para> 679 Jabber groupchat specific. This setting ensures that the nicks defined by the other members of a groupchat are used, instead of the username part of their JID. This only applies to groupchats where their real JID is known (either "non-anonymous" ones, or "semi-anonymous" from the point of view of the channel moderators) 680 </para> 681 682 <para> 683 Enabling this may have the side effect of changing the nick of existing contacts, either in your buddy list or in other groupchats. If a contact is in multiple groupchats with different nicks, enabling this setting for all those would result in multiple nick changes when joining, and the order of those changes may vary. 684 </para> 685 686 <para> 687 Note that manual nick changes done through the <emphasis>rename</emphasis> command always take priority 647 688 </para> 648 689 </description> … … 1491 1532 and any modes they should have. The following statuses are currently 1492 1533 recognised: <emphasis>online</emphasis> (i.e. available, not 1493 away), <emphasis>special</emphasis> , <emphasis>away</emphasis>,1494 and <emphasis>offline</emphasis>.1534 away), <emphasis>special</emphasis> (specific to the protocol), 1535 <emphasis>away</emphasis>, and <emphasis>offline</emphasis>. 1495 1536 </para> 1496 1537 … … 1498 1539 If a status is followed by a valid channel mode character 1499 1540 (@, % or +), it will be given to users with that status. 1500 For example, <emphasis>online@,special%,away+,offline</emphasis> 1541 For example, <emphasis>online@,special%,away+,offline</emphasis> 1501 1542 will show all users in the channel. Online people will 1502 1543 have +o, people who are online but away will have +v, … … 1815 1856 </para> 1816 1857 </description> 1858 </bitlbee-command> 1859 1860 <bitlbee-command name="plugins"> 1861 <short-description>List all the external plugins and protocols</short-description> 1862 <syntax>plugins</syntax> 1863 1864 <description> 1865 <para> 1866 This gives you a list of all the external plugins and protocols. 1867 </para> 1868 </description> 1869 1817 1870 </bitlbee-command> 1818 1871
Note: See TracChangeset
for help on using the changeset viewer.
