Changes in doc/user-guide/commands.xml [73dd021:82cb190]
- File:
-
- 1 edited
-
doc/user-guide/commands.xml (modified) (12 diffs)
Legend:
- Unmodified
- Added
- Removed
-
doc/user-guide/commands.xml
r73dd021 r82cb190 182 182 183 183 <para> 184 For more info mation about a setting, see <emphasis>help set <setting></emphasis>.184 For more information about a setting, see <emphasis>help set <setting></emphasis>. 185 185 </para> 186 186 … … 240 240 241 241 <para> 242 For more info mation about a setting, see <emphasis>help set <setting></emphasis>.242 For more information about a setting, see <emphasis>help set <setting></emphasis>. 243 243 </para> 244 244 … … 785 785 <para> 786 786 Keep two things in mind: When not using Twitter, you <emphasis>must</emphasis> also disable the <emphasis>oauth</emphasis> setting as it currently only works with Twitter. If you're still having issues, make sure there is <emphasis>no</emphasis> slash at the end of the URL you enter here. 787 </para> 788 </description> 789 </bitlbee-setting> 790 791 <bitlbee-setting name="carbons" type="boolean" scope="account"> 792 <default>true</default> 793 794 <description> 795 <para> 796 Jabber specific. "Message carbons" (XEP-0280) is a server feature to get copies of outgoing messages sent from other clients connected to the same account. It's not widely supported by most public XMPP servers (easier if you host your own), but this will probably change in the next few years. 797 </para> 798 <para> 799 This defaults to true, which will enable it if the server supports it, or fail silently if it's not. This setting only exists to allow disabling the feature if anyone considers it undesirable. 800 </para> 801 <para> 802 See also the <emphasis>self_messages</emphasis> setting. 787 803 </para> 788 804 </description> … … 1093 1109 1094 1110 <para> 1095 With modes "chat" and "many", you can send direct messages by /msg'ing your contacts directly. Note, however, that incoming DMs are not fetched yet.1111 With modes "chat" and "many", you can send direct messages by /msg'ing your contacts directly. Incoming DMs are only fetched if the "stream" setting is on (default). 1096 1112 </para> 1097 1113 … … 1158 1174 <description> 1159 1175 <para> 1160 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.1176 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. Some servers use internal identifiers, which are often just numbers. 1161 1177 </para> 1162 1178 … … 1172 1188 <description> 1173 1189 <para> 1174 This enables OAuth authentication for an IM account; right now the Twitter (working for Twitter only) and Jabber (for Google Talk , Facebook and MSN Messenger) module support it.1190 This enables OAuth authentication for an IM account; right now the Twitter (working for Twitter only) and Jabber (for Google Talk only) module support it. 1175 1191 </para> 1176 1192 … … 1324 1340 </bitlbee-setting> 1325 1341 1342 <bitlbee-setting name="proxy" type="string" scope="account"> 1343 <default><local><auto></default> 1344 1345 <description> 1346 <para> 1347 A list of <emphasis>file transfer proxies</emphasis> for jabber. This isn't the connection proxy. Sorry, look in bitlbee.conf for those. 1348 </para> 1349 1350 <para> 1351 It's a semicolon-separated list of items that can be either <emphasis>JID,HOST,PORT</emphasis> or two special values, <emphasis><local></emphasis> (to try a direct connection first) and <emphasis><auto></emphasis> (to try to discover a proxy). For example, "<local>;proxy.somewhere.org,123.123.123.123,7777". 1352 </para> 1353 <para> 1354 The address should point to a SOCKS5 bytestreams server, usually provided by jabber servers. This is only used for sending files. Note that the host address might not match what DNS tells you, and the port isn't always the same. 1355 </para> 1356 <para> 1357 The correct way to get a socks proxy host/port is a mystery, and the file transfer might fail anyway. Maybe just try using dropbox instead. 1358 </para> 1359 </description> 1360 </bitlbee-setting> 1361 1326 1362 <bitlbee-setting name="query_order" type="string" scope="global"> 1327 1363 <default>lifo</default> … … 1384 1420 </bitlbee-setting> 1385 1421 1422 <bitlbee-setting name="self_messages" type="string" scope="global"> 1423 <default>true</default> 1424 <possible-values>true, false, prefix, prefix_notice</possible-values> 1425 1426 <description> 1427 <para> 1428 Change this setting to customize how (or whether) to show self-messages, which are messages sent by yourself from other locations (for example, mobile clients), for IM protocols that support it. 1429 </para> 1430 1431 <para> 1432 When this is set to "true", it will send those messages in the "standard" way, which is a PRIVMSG with source and target fields swapped. 1433 </para> 1434 1435 <para> 1436 Since this isn't very well supported by some clients (the messages might appear in the wrong window), you can set it to "prefix" to show them as a normal message prefixed with "-> ", or use "prefix_notice" which is the same thing but with a NOTICE instead. 1437 </para> 1438 1439 <para> 1440 You can also set it to "false" to disable these messages completely. 1441 </para> 1442 1443 <para> 1444 This setting only applies to private messages. Self messages in groupchats are always shown, since they haven't caused issues in any clients so far. 1445 </para> 1446 1447 <para> 1448 More information: <emphasis>https://wiki.bitlbee.org/SelfMessages</emphasis> 1449 </para> 1450 </description> 1451 </bitlbee-setting> 1452 1386 1453 <bitlbee-setting name="server" type="string" scope="account"> 1387 1454 <description> … … 1417 1484 1418 1485 <bitlbee-setting name="show_users" type="string" scope="channel"> 1419 <default>online+, away</default>1486 <default>online+,special%,away</default> 1420 1487 1421 1488 <description> … … 1424 1491 and any modes they should have. The following statuses are currently 1425 1492 recognised: <emphasis>online</emphasis> (i.e. available, not 1426 away), <emphasis>away</emphasis>, and <emphasis>offline</emphasis>. 1493 away), <emphasis>special</emphasis>, <emphasis>away</emphasis>, 1494 and <emphasis>offline</emphasis>. 1427 1495 </para> 1428 1496 … … 1430 1498 If a status is followed by a valid channel mode character 1431 1499 (@, % or +), it will be given to users with that status. 1432 For example, <emphasis>online@, away+,offline</emphasis> will1433 show all users in the channel. Online people will1500 For example, <emphasis>online@,special%,away+,offline</emphasis> 1501 will show all users in the channel. Online people will 1434 1502 have +o, people who are online but away will have +v, 1435 1503 and others will have no special modes. … … 1891 1959 1892 1960 <description> 1893 <para>Rejects all incoming (not already transferring) file transfers. Since you probably have only one incoming transfer at a time, no id is nec cessary. Or is it?</para>1961 <para>Rejects all incoming (not already transferring) file transfers. Since you probably have only one incoming transfer at a time, no id is necessary. Or is it?</para> 1894 1962 </description> 1895 1963
Note: See TracChangeset
for help on using the changeset viewer.
