Mercurial > ~mikael > mcabber > hg
comparison mcabber/doc/mcabber.1.txt @ 1842:cec7cbeb1c2e
Update manpage
author | Mikael Berthe <mikael@lilotux.net> |
---|---|
date | Sun, 28 Mar 2010 11:55:34 +0200 |
parents | 921429804e20 |
children | 41699679b121 |
comparison
equal
deleted
inserted
replaced
1841:8ad982f83fd6 | 1842:cec7cbeb1c2e |
---|---|
115 Additional key bindings may be specified using the '/bind' command described | 115 Additional key bindings may be specified using the '/bind' command described |
116 in the COMMANDS section. | 116 in the COMMANDS section. |
117 | 117 |
118 MCABBER'S ROSTER | 118 MCABBER'S ROSTER |
119 ---------------- | 119 ---------------- |
120 The first listed resource on the roster is '[status]', which keeps a log of | 120 The first listed item on the roster is '[status]', which keeps a log of |
121 everything that appears in the short log window below the main chat area. | 121 everything that appears in the short log window below the main chat area. |
122 While the log window was designed for showing the latest few elements, the | 122 While the log window was designed for showing the latest few elements, the |
123 dedicated '[status]' buffer allows more comfortable viewing of the log, as | 123 dedicated '[status]' buffer allows more comfortable viewing of the log, as |
124 well as scrolling it in a standard manner. | 124 well as scrolling it in a standard manner. |
125 | 125 |
126 Group names are displayed above the resources that are within them, and are | 126 Group names are displayed above the items that are within them, and are |
127 indicated by '---' to the left of the name. | 127 indicated by '---' to the left of the name. |
128 | 128 |
129 For every real Jabber resource, the roster displays four pieces of information: | 129 For every real Jabber contact, the roster displays four pieces of information: |
130 the resource's name or alias, its online status, its authorization status, and | 130 the buddy's name or alias, its online status, its authorization status, and |
131 whether there are unread messages from the resource waiting for you. | 131 whether there are unread messages from the buddy waiting for you. |
132 | 132 |
133 The online status is one of the following: | 133 The online status is one of the following: |
134 | 134 |
135 'o';; online | 135 'o';; online |
136 'f';; free for chat | 136 'f';; free for chat |
137 'a';; away | 137 'a';; away |
138 'n';; not available (labeled 'extended away' in some clients) | 138 'n';; not available (labeled 'extended away' in some clients) |
139 'd';; do not disturb | 139 'd';; do not disturb |
140 'i';; invisible (displayed only for your resource) | 140 'i';; invisible (displayed only for your resource) |
141 '_';; offline (or invisible to you) | 141 '_';; offline (or invisible to you) |
142 '?';; unknown, usually meaning you are not authorized to see this resource's status | 142 '?';; unknown, usually meaning you are not authorized to see this buddy's status |
143 'x';; a conference room in which you are not participating | 143 'x';; a conference room in which you are not participating |
144 'C';; a conference room in which you are participating | 144 'C';; a conference room in which you are participating |
145 | 145 |
146 The authorization status indicates whether a resource is authorized to receive | 146 The authorization status indicates whether a buddy is authorized to receive |
147 your online status updates, and is displayed by the brackets surrounding the | 147 your online status updates, and is displayed by the brackets surrounding the |
148 resource's online status. Square brackets, like '[o]', indicate that this | 148 buddy's online status. Square brackets, like '[o]', indicate that this |
149 resource is authorized to receive your status. Curly braces, like '\{o\}', | 149 buddy is authorized to receive your status. Curly braces, like '\{o\}', |
150 indicate that they are not authorized to receive your status. | 150 indicate that they are not authorized to receive your status. |
151 | 151 |
152 When there are unread messages from the resource which you have not looked at, | 152 When there are unread messages from a buddy which you have not looked at, |
153 a hash mark ('#') appears in the leftmost section of the roster for that | 153 a hash mark ('#') appears in the leftmost section of the roster for that |
154 resource. The hash mark disappears once you view that resource's message log. | 154 buddy. The hash mark disappears once you view that buddy's message |
155 buffer. | |
156 When the user attention is requested (or when you receive a message containing | |
157 your nickname in a MUC room), the hash mark is replaced with the 'attention | |
158 sign', an exclamation mark ('!'). | |
155 | 159 |
156 Examples: | 160 Examples: |
157 | 161 |
158 ' --- Buds';; This is a group named 'Buds' | 162 ' --- Buds';; This is a group named 'Buds' |
159 '#[o] John';; John is online, can see your status, and sent you a message that you did not read yet | 163 '#[o] John';; John is online, can see your status, and sent you a message that you did not read yet |
209 | 213 |
210 /buffer clear|close|close_all|purge|list:: | 214 /buffer clear|close|close_all|purge|list:: |
211 /buffer top|bottom|date|%|search_backward|search_forward:: | 215 /buffer top|bottom|date|%|search_backward|search_forward:: |
212 /buffer scroll_lock|scroll_unlock|scroll_toggle:: | 216 /buffer scroll_lock|scroll_unlock|scroll_toggle:: |
213 /buffer save filename:: | 217 /buffer save filename:: |
214 Buddy's buffer manipulation command. Eg. you can search through buffer for "text", clear chat window etc. | 218 Buddy's buffer manipulation command. E.g. you can search through buffer for "text", clear chat window etc. |
215 | 219 |
216 'clear';; Clear the current buddy chat window | 220 'clear';; Clear the current buddy chat window |
217 'close' [jid];; Empty all contents of the buffer and close the current buddy chat window | 221 'close' [jid];; Empty all contents of the buffer and close the current buddy chat window |
218 'close_all';; Empty all contents of the chat buffers and close the chat windows | 222 'close_all';; Empty all contents of the chat buffers and close the chat windows |
219 'purge' [jid];; Clear the current buddy chat window and empty all contents of the chat buffer | 223 'purge' [jid];; Clear the current buddy chat window and empty all contents of the chat buffer |
241 /color roster (status wildcard (color|-)|clear):: | 245 /color roster (status wildcard (color|-)|clear):: |
242 /color mucnick nick (color|-):: | 246 /color mucnick nick (color|-):: |
243 /color muc (jid|.|*) [on|preset|off|-]:: | 247 /color muc (jid|.|*) [on|preset|off|-]:: |
244 The 'color' command allows setting dynamic color properties of the screen. | 248 The 'color' command allows setting dynamic color properties of the screen. |
245 | 249 |
246 'roster' clear;; Remove all color rules for the roster. All roster items will get its default color. | 250 'roster' clear;; Remove all color rules for the roster. All roster items will get its default color. |
247 'roster' status wildcard color;; Set a color rule (or overwrite, if it already exists). The status is string containing all statuses the roster item can have for the rule to match, or * if any status is OK. Wildcard is the file-matching wildcard that will be applied to JID. Color is the wanted color. If color is -, the rule is removed. If more than one rule matches, the color from the last created (not overwritten) is used. | 251 'roster' status wildcard color;; Set a color rule (or overwrite, if it already exists). The status is string containing all statuses the roster item can have for the rule to match, or * if any status is OK. Wildcard is the file-matching wildcard that will be applied to JID. Color is the wanted color. If color is -, the rule is removed. If more than one rule matches, the color from the last created (not overwritten) is used. |
248 'mucnick' nick (color|-);; Marks the nick to be colored by given color. If a MUC has colored nicks, this one will be used. If color is -, the color is marked as chosen automatically, which means it will not be used in 'preset' coloring mode, but will stay the same in 'on' coloring mode. | 252 'mucnick' nick (color|-);; Marks the nick to be colored by given color. If a MUC has colored nicks, this one will be used. If color is -, the color is marked as chosen automatically, which means it will not be used in 'preset' coloring mode, but will stay the same in 'on' coloring mode. |
249 'muc' (jid|.|*) [on|preset|off|-];; Sets a MUC nick coloring mode. If a jid (. means currently selected jid) is provided, the mode will apply to this specific MUC. If * is used, it will be applied to all MUCs, except the ones set by their jid. Mode 'on' colors all nicks, 'preset' only the ones manually set by /color mucnick command and 'off' colors none. If not specified, defaults to 'on'. Mode '-' removes the mode from given JID, which means the global one will apply. You can not remove the global mode. Default global coloring mode is 'off'. | 253 'muc' (jid|.|*) [on|preset|off|-];; Sets a MUC nick coloring mode. If a jid (. means currently selected jid) is provided, the mode will apply to this specific MUC. If * is used, it will be applied to all MUCs, except the ones set by their jid. Mode 'on' colors all nicks, 'preset' only the ones manually set by /color mucnick command and 'off' colors none. If not specified, defaults to 'on'. Mode '-' removes the mode from given JID, which means the global one will apply. You can not remove the global mode. Default global coloring mode is 'off'. |
250 | 254 |
251 /connect:: | 255 /connect:: |
252 Establish connection to the Jabber server. | 256 Establish connection to the Jabber server. |
253 | 257 |
254 /del:: | 258 /del:: |
263 | 267 |
264 /event #n|* accept|ignore|reject [event-specific arguments]:: | 268 /event #n|* accept|ignore|reject [event-specific arguments]:: |
265 /event list:: | 269 /event list:: |
266 Tell mcabber what to do about pending events. + | 270 Tell mcabber what to do about pending events. + |
267 If the first parameter is '*', the command will apply to all queued events. + | 271 If the first parameter is '*', the command will apply to all queued events. + |
268 Event-specific arguments will be interpreted on event-to event basis. The only built-in case, when argument is used is MUC invitation reject - argument, if present, will be interpreted as reject reason. | 272 Event-specific arguments will be interpreted on event-to event basis. The only built-in case, when argument is used is MUC invitation reject - argument, if present, will be interpreted as reject reason. |
269 | 273 |
270 #N|* accept [event-specific arguments];; Event number #N/All events will be accepted | 274 #N|* accept [event-specific arguments];; Event number #N/All events will be accepted |
271 #N|* ignore [event-specific arguments];; Event number #N/All events will be ignored | 275 #N|* ignore [event-specific arguments];; Event number #N/All events will be ignored |
272 #N|* reject [event-specific arguments];; Event number #N/All events will be rejected | 276 #N|* reject [event-specific arguments];; Event number #N/All events will be rejected |
273 'list';; List all pending events | 277 'list';; List all pending events |
327 /module load|unload [-f] module:: | 331 /module load|unload [-f] module:: |
328 /module info module:: | 332 /module info module:: |
329 /module [list]:: | 333 /module [list]:: |
330 Load, unload or show info on module. | 334 Load, unload or show info on module. |
331 | 335 |
332 'load' [-f] module;; Loads specified module. If -f flag is specified, most of module loading errors will be ignored. | 336 'load' [-f] module;; Loads specified module. If -f flag is specified, most of module loading errors will be ignored. |
333 'unload' [-f] module;; Unloads specified module. Note: The force flag will not remove any dependent on this modules! | 337 'unload' [-f] module;; Unloads specified module. Note: The force flag will not remove any dependency on this module! |
334 'info' module;; Shows available information about this module. | 338 'info' module;; Shows available information about this module. |
335 ['list'];; Lists modules in a format: [modulename] [reference count] ([Manually/Automatically loaded]) [any extra info, like version or dependencies] | 339 ['list'];; Lists modules in a format: [modulename] [reference count] ([Manually/Automatically loaded]) [any extra info, like version or dependencies] |
336 | 340 |
337 /move [groupname]:: | 341 /move [groupname]:: |
338 Move the current buddy to the requested group. If no group is specified, then the buddy is moved to the default group. If the group "groupname" doesn't exist, it is created. + | 342 Move the current buddy to the requested group. If no group is specified, then the buddy is moved to the default group. If the group "groupname" doesn't exist, it is created. + |
363 | 367 |
364 'key';; Print the fingerprint of your private key to the Status Buffer | 368 'key';; Print the fingerprint of your private key to the Status Buffer |
365 'start' [jid];; Open an OTR channel to the specified jid (or the currently selected contact) | 369 'start' [jid];; Open an OTR channel to the specified jid (or the currently selected contact) |
366 'stop' [jid];; Close the OTR channel to the specified jid (or the currently selected contact) | 370 'stop' [jid];; Close the OTR channel to the specified jid (or the currently selected contact) |
367 'info' [jid];; Show current OTR status for the specified jid (or the currently selected contact) | 371 'info' [jid];; Show current OTR status for the specified jid (or the currently selected contact) |
368 'fingerprint' [jid [fpr]];; Show the active fingerprint of an OTR channel. If the fingerprint is provided instead of "fpr", the fingerprint will become trusted. If you replace "fpr" by some bogus string the fingerprint will loose the trusted status. | 372 'fingerprint' [jid [fpr]];; Show the active fingerprint of an OTR channel. If the fingerprint is provided instead of "fpr", the fingerprint will become trusted. If you replace "fpr" by some bogus string the fingerprint will loose the trusted status. |
369 'smpq' [jid] secret;; Initiate the Socialist Millionaires Protocol with the secret and the buddy | 373 'smpq' [jid] secret;; Initiate the Socialist Millionaires Protocol with the secret and the buddy |
370 'smpr' [jid] secret;; Respond to the Initiation of the jid with the secret | 374 'smpr' [jid] secret;; Respond to the Initiation of the jid with the secret |
371 'smpa' [jid];; Abort the running Socialist Millionaires Protocol | 375 'smpa' [jid];; Abort the running Socialist Millionaires Protocol |
372 | 376 |
373 /otrpolicy:: | 377 /otrpolicy:: |
374 /otrpolicy (default|jid) (plain|manual|opportunistic|always):: | 378 /otrpolicy (default|jid) (plain|manual|opportunistic|always):: |
375 You can use the shortcut-jid "." for the currently selected contact. | 379 You can use the shortcut-jid "." for the currently selected contact. |
376 | 380 |
377 (without arguments);; Prints all OTR policies to the status buffer | 381 (without arguments);; Prints all OTR policies to the status buffer |
378 ('default'|'jid') (plain|manual|opportunistic|always);; Sets either the default policy or the policy for the given jid The plain policy should never be used, because you won't be able to receive or send any OTR encrypted messages. If you set the policy to manual, you or your chat partner have to start the OTR encryption by hand (e.g. with /otr start). The policy "opportunistic" does that itself by sending a special whitespace-sequence at the end of unencrypted messages. So the other OTR-enabled chat client knows, that you want to use OTR. Note that the first message will always be unencryted, if you use this policy. With the policy "always" no message will be sent in plain text. If you try to sent the first message unencrypted, mcabber will try to establish an OTR channel. Please resend your message, when you get the information that the channel was established. If someone sends you plaintext messages while the policy is set to "always", you'll be able to read the message but it won't be saved to the history. | 382 ('default'|'jid') (plain|manual|opportunistic|always);; Sets either the default policy or the policy for the given jid The plain policy should never be used, because you won't be able to receive or send any OTR encrypted messages. If you set the policy to manual, you or your chat partner have to start the OTR encryption by hand (e.g. with /otr start). The policy "opportunistic" does that itself by sending a special whitespace-sequence at the end of unencrypted messages. So the other OTR-enabled chat client knows, that you want to use OTR. Note that the first message will always be unencryted, if you use this policy. With the policy "always" no message will be sent in plain text. If you try to sent the first message unencrypted, mcabber will try to establish an OTR channel. Please resend your message, when you get the information that the channel was established. If someone sends you plaintext messages while the policy is set to "always", you'll be able to read the message but it won't be saved to the history. |
379 | 383 |
380 /pgp disable|enable|force|info [jid]:: | 384 /pgp disable|enable|force|info [jid]:: |
381 /pgp setkey [jid [key]]:: | 385 /pgp setkey [jid [key]]:: |
382 This command manipulates PGP settings for the specified jid (by default the currently selected contact). + | 386 This command manipulates PGP settings for the specified jid (by default the currently selected contact). + |
383 Please note that PGP encryption won't be used if no remote PGP support is detected, even if PGP is enabled with this command. You can force PGP encryption with the "force" subcommand. | 387 Please note that PGP encryption won't be used if no remote PGP support is detected, even if PGP is enabled with this command. You can force PGP encryption with the "force" subcommand. |
467 'toggle';; Toggle roster visibility | 471 'toggle';; Toggle roster visibility |
468 'note' [-|text];; Set/update/delete an annotation. If there is no text, the current item's annotation is displayed -- if you are in the status buffer, all notes are displayed. If text is "-", the note is erased. | 472 'note' [-|text];; Set/update/delete an annotation. If there is no text, the current item's annotation is displayed -- if you are in the status buffer, all notes are displayed. If text is "-", the note is erased. |
469 | 473 |
470 /say [-n|-h|--] text:: | 474 /say [-n|-h|--] text:: |
471 Send the "text" message to the currently selected buddy. It can be useful if you want to send a message beginning with a slash, for example. + | 475 Send the "text" message to the currently selected buddy. It can be useful if you want to send a message beginning with a slash, for example. + |
472 The "-n" flag turns the message to "normal" type, "-h" to "headline". "--" can be used to send chat message beginning with -n or -h. | 476 The "-n" flag turns the message to "normal" type, "-h" to "headline". "--" can be used to send chat message beginning with -n or -h. |
473 | 477 |
474 /say_to [-n|-h] [-q] [-f file] jid text:: | 478 /say_to [-n|-h] [-q] [-f file] jid text:: |
475 Send the "text" message to the specified jid. + | 479 Send the "text" message to the specified jid. + |
476 Please note that this command doesn't set the default resource for a contact, so if you want to send several messages to a specific resource you will have to use "/say_to" for each message. + | 480 Please note that this command doesn't set the default resource for a contact, so if you want to send several messages to a specific resource you will have to use "/say_to" for each message. + |
477 The "-n" flag turns the message to "normal" type, "-h" to "headline". "--" can be used to send chat messages beginning with -n or -h. + | 481 The "-n" flag turns the message to "normal" type, "-h" to "headline". "--" can be used to send chat messages beginning with -n or -h. + |
479 A text file can be provided with the "-f" switch (in which case there's no need to pass a text argument after the jid, of course). | 483 A text file can be provided with the "-f" switch (in which case there's no need to pass a text argument after the jid, of course). |
480 | 484 |
481 /screen_refresh:: | 485 /screen_refresh:: |
482 Refresh the mcabber screen. | 486 Refresh the mcabber screen. |
483 | 487 |
484 /set option [= value]:: | 488 /set [option [= value]]:: |
485 Display or set an option value. | 489 Display or set an option value. + |
490 Without arguments prints a list of all set options with their values | |
486 | 491 |
487 /source pattern:: | 492 /source pattern:: |
488 Read configuration files, that match glob pattern (sorted in alphabetical order). | 493 Read configuration files, that match glob pattern (sorted in alphabetical order). |
489 | 494 |
490 /status [online|avail|invisible|free|dnd|notavail|away [-|statusmessage]]:: | 495 /status [online|avail|invisible|free|dnd|notavail|away [-|statusmessage]]:: |
530 Written by mailto:mikael@lilotux.net[Mikael BERTHE] and others | 535 Written by mailto:mikael@lilotux.net[Mikael BERTHE] and others |
531 (see AUTHORS file). + | 536 (see AUTHORS file). + |
532 | 537 |
533 RESOURCES | 538 RESOURCES |
534 --------- | 539 --------- |
535 http://mcabber.com/[Main web site] | 540 http://mcabber.com/[Main web site] + |
541 http://wiki.mcabber.com/[Official wiki] + | |
542 xmpp:mcabber@conf.lilotux.net[MCabber MUC room] | |
536 | 543 |
537 COPYING | 544 COPYING |
538 ------- | 545 ------- |
539 Copyright \(C) 2005-2010 Mikael Berthe and others. + | 546 Copyright \(C) 2005-2010 Mikael Berthe and others. + |
540 | 547 |