Changeset 6738a67 for doc/user-guide/commands.xml
- Timestamp:
- 2008-07-16T23:22:52Z (16 years ago)
- Branches:
- master
- Children:
- 9b55485
- Parents:
- 9730d72 (diff), 6a78c0e (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
Legend:
- Unmodified
- Added
- Removed
-
doc/user-guide/commands.xml
r9730d72 r6738a67 163 163 164 164 <para> 165 If you want, you can also tell BitlBee what nick to give the new contact. Of course you can also use the <emphasis>rename</emphasis> command for that, but sometimes this might be more convenient. 166 </para> 167 168 <para> 169 Adding -tmp adds the buddy to the internal BitlBee structures only, not to the real contact list (like done by <emphasis>set handle_unknown add</emphasis>). This allows you to talk to people who are not in your contact list. 165 If you want, you can also tell BitlBee what nick to give the new contact. The -tmp option adds the buddy to the internal BitlBee structures only, not to the real contact list (like done by <emphasis>set handle_unknown add</emphasis>). This allows you to talk to people who are not in your contact list. This normally won't show you any presence notifications. 170 166 </para> 171 167 </description> … … 532 528 533 529 <bitlbee-setting name="charset" type="string" scope="global"> 534 <default> iso8859-1</default>530 <default>utf-8</default> 535 531 <possible-values>you can get a list of all possible values by doing 'iconv -l' in a shell</possible-values> 536 532 537 533 <description> 538 534 <para> 539 Th e charset setting enables you to use different character sets in BitlBee. These get converted to UTF-8 before sending and from UTF-8 when receiving.540 </para> 541 542 <para> 543 If you don't know what's the best value for this, at least iso8859-1 is the best choice for most Western countries. You can try to find what works best for you on http://czyborra.com/charsets/iso8859.html535 This setting tells BitlBee what your IRC client sends and expects. It should be equal to the charset setting of your IRC client if you want to be able to send and receive non-ASCII text properly. 536 </para> 537 538 <para> 539 Most systems use UTF-8 these days. On older systems, an iso8859 charset may work better. For example, iso8859-1 is the best choice for most Western countries. You can try to find what works best for you on http://www.unicodecharacter.com/charsets/iso8859.html 544 540 </para> 545 541 </description> … … 804 800 </bitlbee-setting> 805 801 802 <bitlbee-setting name="root_nick" type="string" scope="global"> 803 <default>root</default> 804 805 <description> 806 <para> 807 Normally the "bot" that takes all your BitlBee commands is called "root". If you don't like this name, you can rename it to anything else using the <emphasis>rename</emphasis> command, or by changing this setting. 808 </para> 809 </description> 810 </bitlbee-setting> 811 806 812 <bitlbee-setting name="save_on_quit" type="boolean" scope="global"> 807 813 <default>true</default> … … 888 894 <description> 889 895 <para> 890 Sends you a /notice when a user starts typing a message (if the protocol supports it, MSN for example). This is a bug, not a feature. (But please don't report it.. ;-) You don't want to use it. Really. In fact the typing-notification is just one of the least useful 'innovations' ever. It's just there because some guy will probably ask me about it anyway. ;-)896 Sends you a /notice when a user starts typing a message (if supported by the IM protocol and the user's client). To use this, you most likely want to use a script in your IRC client to show this information in a more sensible way. 891 897 </para> 892 898 </description> … … 1057 1063 <short-description>Change friendly name, nick</short-description> 1058 1064 <syntax>nick <connection> [<new nick>]</syntax> 1059 <syntax>nick</syntax> 1060 1061 <description> 1062 <para> 1063 This command allows to set the friendly name of an im account. If no new name is specified the command will report the current name. When the name contains spaces, don't forget to quote the whole nick in double quotes. Currently this command is only supported by the MSN protocol. 1064 </para> 1065 1066 <para> 1067 It is recommended to use the per-account <emphasis>display_name</emphasis> setting to read and change this information. The <emphasis>nick</emphasis> command is deprecated. 1065 <syntax>nick <connection></syntax> 1066 1067 <description> 1068 <para> 1069 Deprecated: Use the per-account <emphasis>display_name</emphasis> setting to read and change this information. 1068 1070 </para> 1069 1071 </description> 1070 1072 1071 1073 <ircexample> 1072 <ircline nick="wouter"> nick 1 "Wouter Paesen"</ircline>1073 <ircline nick="root"> Setting your name on connection 1 to `Wouter Paesen'</ircline>1074 <ircline nick="wouter">account set 1/display_name "The majestik møøse"</ircline> 1075 <ircline nick="root">display_name = `The majestik møøse'</ircline> 1074 1076 </ircexample> 1075 1077
Note: See TracChangeset
for help on using the changeset viewer.