Mercurial > ~mikael > mcabber > hg
annotate mcabber/doc/mcabber.1.txt @ 630:713ba1932382
Post-0.7.2 changes
| author | Mikael Berthe <mikael@lilotux.net> |
|---|---|
| date | Fri, 23 Dec 2005 17:19:02 +0100 |
| parents | d04b950122b9 |
| children | aff6df4b408b |
| rev | line source |
|---|---|
| 198 | 1 MCABBER(1) |
| 2 =========== | |
| 222 | 3 Mikael BERTHE <mcabber@lilotux.net> |
| 630 | 4 v0.7.3-dev, January 2006 |
| 198 | 5 |
| 6 NAME | |
| 7 ---- | |
| 200 | 8 mcabber - a simple Jabber console client |
| 198 | 9 |
| 10 SYNOPSIS | |
| 11 -------- | |
| 12 'mcabber' [ -f configfile ] [ --help | -h ] | |
| 13 | |
| 14 DESCRIPTION | |
| 15 ----------- | |
| 204 | 16 `mcabber(1)` is a small Jabber console client. + |
| 200 | 17 For now it needs a configuration file to start, so please copy the sample |
| 208 | 18 mcabberrc file and adapt your connection settings. |
| 200 | 19 |
|
360
20283b69db99
Doc: Say a Jabber account should already exist for using mcabber
Mikael Berthe <mikael@lilotux.net>
parents:
349
diff
changeset
|
20 You also need to have an existing Jabber account to use this software, as |
|
20283b69db99
Doc: Say a Jabber account should already exist for using mcabber
Mikael Berthe <mikael@lilotux.net>
parents:
349
diff
changeset
|
21 it cannot (un)register accounts yet. |
|
20283b69db99
Doc: Say a Jabber account should already exist for using mcabber
Mikael Berthe <mikael@lilotux.net>
parents:
349
diff
changeset
|
22 |
| 202 | 23 The `mcabber(1)` screen is divided into 4 regions. |
| 200 | 24 The 'roster', alias 'buddylist', is on the left. The 'chat window', or chat |
| 25 buffer, is on the right. The 'input line' lies at the bottom of the screen, | |
| 26 under a small 'log window'. | |
| 27 | |
| 204 | 28 To display buddies chat buffers, you will have to enter 'chat mode'. |
| 29 You can enter chat mode by pressing enter, and leave chat mode with the ESC | |
| 229 | 30 key. Simply sending a message will also enable chat mode. |
| 204 | 31 |
| 32 Here are some of the features of `mcabber`: | |
| 200 | 33 |
| 204 | 34 - 'SSL support'. |
| 467 | 35 - 'MUC support' (Multi-User Chat). |
| 204 | 36 - 'History logging:' If enabled (see the CONFIGURATION FILE section), |
| 432 | 37 `mcabber` can save discussions to history log files. |
| 38 - 'Commands completion:' If possible, `mcabber` will try to complete your | |
| 229 | 39 command line if you hit the Tab key. |
| 618 | 40 - 'Input line history:' Any message or command entered is in the input line |
| 41 history and can be reused easily. | |
| 204 | 42 - 'External actions:' Some events (like receiving a message) can trigger an |
| 43 external action, for example a shell script (you need to enable it in your | |
| 432 | 44 configuration file). A sample events script ("eventcmd") is provided with |
| 45 `mcabber` source code, in the contrib directory. | |
| 200 | 46 |
| 47 OPTIONS | |
| 48 ------- | |
| 49 --help, -h:: | |
| 202 | 50 Quick help usage message |
| 200 | 51 |
| 52 -f configfile:: | |
| 202 | 53 Use configuration file 'configfile' |
| 200 | 54 |
| 55 KEYS | |
| 56 ---- | |
| 57 | |
| 229 | 58 Text typing occurs in the 'input line'; basic operations are supported |
| 59 (left arrow, right arrow, home/end keys, insert, delete, backspace...). | |
| 200 | 60 |
| 61 PageUp and PageDown keys are used to move in the roster. | |
| 62 | |
| 618 | 63 Up and Down arrow keys can be used to move in the input line history; they |
| 64 jump to the previous/next line from the history beginning with the same string | |
| 65 (from first column to the cursor column). | |
| 66 | |
| 200 | 67 To send a message, move to the choosen buddy in the buddylist, type your |
| 68 message and hit enter. If the line begins with a slash, this will be | |
| 69 interpreted as a command (see the COMMAND section below). Hit escape to | |
| 70 leave the chat mode. | |
| 71 | |
| 72 Here is a quick description of the key bindings: | |
| 73 | |
| 74 Ctrl-a:: Go to the beginning of the input line | |
| 75 Ctrl-e:: Go to the end of the input line | |
| 618 | 76 Ctrl-l:: Force a refresh |
| 77 Up/Down:: Move in the input line history | |
| 200 | 78 PgUp/PgDown:: Move inside the roster (buddylist) |
| 79 Tab:: Complete current word, in the input line | |
| 80 Ctrl-g:: Cancel completion / ctrl-g | |
| 81 Ctrl-p/Ctrl-n:: Scroll up/down half a screen in the buffer window (chat mode) | |
| 82 Ctrl-u:: Delete from beginning of the line to the cursor | |
| 83 Ctrl-k:: Delete from the cursor to the end of line | |
| 84 Ctrl-w:: Backward kill word | |
| 85 Ctrl-t:: Transpose chars | |
| 263 | 86 Ctrl-o:: Accept line and put the next history line in the input line (accept-line-and-down-history) |
| 236 | 87 Ctrl-q:: Jump to the next unread message |
| 198 | 88 |
| 199 | 89 COMMANDS |
| 90 -------- | |
| 91 | |
| 245 | 92 /add jid [nickname]:: |
| 491 | 93 Add the "jid" Jabber user to our roster (default group), and send a |
| 245 | 94 notification request to this buddy. If no nickname is specified, the |
| 95 jid is used. | |
| 199 | 96 |
|
286
a3d65d7f0bc3
Add /alias documentation
Mikael Berthe <mikael@lilotux.net>
parents:
277
diff
changeset
|
97 /alias name = command line:: |
| 289 | 98 Add "name" as an alias for "command line". + |
| 99 Aliases are expanded only once, thus they can not be chained. + | |
| 100 "/alias name" displays the value associated with the "name" alias; | |
| 101 "/alias name =" unsets the "name" alias. + | |
|
286
a3d65d7f0bc3
Add /alias documentation
Mikael Berthe <mikael@lilotux.net>
parents:
277
diff
changeset
|
102 Example: "/alias away = status away". |
| 289 | 103 |
| 618 | 104 /authorization allow|cancel|request [jid]:: |
| 105 Manage the presence subscriptions. + | |
| 106 If no jid is provided, the current buddy is used. | |
| 107 | |
| 108 'allow';; allow the buddy to receive your presence updates | |
| 109 'cancel';; cancel the buddy' subscription to your presence updates | |
| 110 'request';; request a subscription to the buddy's presence updates | |
| 111 | |
| 289 | 112 /bind keycode = command line:: |
| 113 Bind a command line to the key with the "keycode" code number. + | |
| 432 | 114 Keycodes of unused keys are displayed by `mcabber` in the log window |
| 289 | 115 when pressing the key, for example "Unknown key=265". + |
| 116 "/bind keycode" displays the command line bound to the given keycode; | |
| 117 "/bind keycode" unbinds the given keycode. + | |
| 118 Note: aliases can be used in key bindings. + | |
| 450 | 119 Example: "/bind 265 = status online" (265 is F1 for me, but it may |
| 289 | 120 depend on your ncurses installation). |
|
286
a3d65d7f0bc3
Add /alias documentation
Mikael Berthe <mikael@lilotux.net>
parents:
277
diff
changeset
|
121 |
| 618 | 122 /buffer clear|top|bottom|date|%|search_backward|search_forward:: |
| 202 | 123 The 'buffer' command manipulates the current buddy's buffer |
| 124 (chat window). | |
| 199 | 125 |
|
465
52171a3dc199
Update manual page (/buffer command)
Mikael Berthe <mikael@lilotux.net>
parents:
450
diff
changeset
|
126 'clear';; clear the current buddy chat window |
| 511 | 127 'bottom';; jump to the bottom of the current buddy chat buffer |
|
465
52171a3dc199
Update manual page (/buffer command)
Mikael Berthe <mikael@lilotux.net>
parents:
450
diff
changeset
|
128 'top';; jump to the top of the current buddy chat buffer |
| 511 | 129 'up' [n];; scroll the buffer up n lines (default: half a screen) |
| 130 'down' [n];; scroll the buffer down n lines (default: half a screen) | |
| 618 | 131 'date' date;; jump to the first line after the specified date in the chat buffer (date format: "YYYY-mm-dd[THH:MM:SS]", "-" and ":" are optional) |
| 132 '%' n;; jump to position %n of the buddy chat buffer | |
| 491 | 133 'search_backward' text;; search for "text" in the current buddy chat buffer |
| 134 'search_forward' text;; search for "text" in the current buddy chat buffer | |
| 199 | 135 |
| 136 /clear:: | |
| 206 | 137 The 'clear' command is actually an alias for "/buffer clear". |
| 199 | 138 |
|
298
35cda94e570d
Add /connect and /disconnect commands
Mikael Berthe <mikael@lilotux.net>
parents:
290
diff
changeset
|
139 /connect:: |
|
35cda94e570d
Add /connect and /disconnect commands
Mikael Berthe <mikael@lilotux.net>
parents:
290
diff
changeset
|
140 Establish connection to the Jabber server. |
|
35cda94e570d
Add /connect and /disconnect commands
Mikael Berthe <mikael@lilotux.net>
parents:
290
diff
changeset
|
141 |
| 205 | 142 /del:: |
| 143 Delete the current buddy from our roster, unsubscribe from its presence | |
| 144 notification and unsubscribe it from ours. | |
| 145 | |
|
298
35cda94e570d
Add /connect and /disconnect commands
Mikael Berthe <mikael@lilotux.net>
parents:
290
diff
changeset
|
146 /disconnect:: |
|
35cda94e570d
Add /connect and /disconnect commands
Mikael Berthe <mikael@lilotux.net>
parents:
290
diff
changeset
|
147 Terminate connection to the Jabber server. Note: the roster is only |
|
35cda94e570d
Add /connect and /disconnect commands
Mikael Berthe <mikael@lilotux.net>
parents:
290
diff
changeset
|
148 available when the connection to the server is active, so the |
|
35cda94e570d
Add /connect and /disconnect commands
Mikael Berthe <mikael@lilotux.net>
parents:
290
diff
changeset
|
149 buddylist is empty when disconnected. |
|
35cda94e570d
Add /connect and /disconnect commands
Mikael Berthe <mikael@lilotux.net>
parents:
290
diff
changeset
|
150 |
| 240 | 151 /group fold|unfold|toggle:: |
| 152 The 'group' command changes the current group display. | |
| 199 | 153 |
| 240 | 154 'fold';; fold (shrink) the current group tree in the roster |
| 155 'unfold';; unfold (expand) the current group tree in the roster | |
| 156 'toggle';; toggle the state (fold/unfold) of the current tree | |
| 199 | 157 |
| 158 /info:: | |
|
440
264f40222872
Update documentation (/info command)
Mikael Berthe <mikael@lilotux.net>
parents:
436
diff
changeset
|
159 Display info on the selected entry (user, agent, group...). + |
|
264f40222872
Update documentation (/info command)
Mikael Berthe <mikael@lilotux.net>
parents:
436
diff
changeset
|
160 For users, resources are displayed with the status, priority and |
|
264f40222872
Update documentation (/info command)
Mikael Berthe <mikael@lilotux.net>
parents:
436
diff
changeset
|
161 status message (if available) of each resource. |
| 199 | 162 |
| 210 | 163 /move [groupname]:: |
| 164 Move the current buddy to the requested group. If no group is | |
| 623 | 165 specified, then the buddy is moved to the default group. + |
|
506
74dcd0df532e
"/move" does not jump to the buddy in the new group
Mikael Berthe <mikael@lilotux.net>
parents:
497
diff
changeset
|
166 Tip: if the chatmode is enabled, you can use "/roster alternate" |
|
74dcd0df532e
"/move" does not jump to the buddy in the new group
Mikael Berthe <mikael@lilotux.net>
parents:
497
diff
changeset
|
167 to jump to the moved buddy. |
| 210 | 168 |
|
260
33e1a05864a6
Add "verbatim multi-line" mode, with commands disabled
mikael@frmp8452
parents:
254
diff
changeset
|
169 /msay begin|verbatim|send|abort:: |
| 238 | 170 Send a multi-line message. To write a single message with several |
| 289 | 171 lines, the 'multi-line mode' should be used. + |
| 172 In multi-line mode, each line (except command lines) typed in the input | |
| 173 line will be added to the multi-line message. Once the message is | |
| 450 | 174 finished, it can be sent to the current selected buddy with the "/msay |
| 175 send" command. + | |
| 289 | 176 The 'verbatim' multi-line mode disables commands, so that it is |
| 177 possible to enter lines starting with a slash. Only the "/msay" | |
| 178 command (with send or abort parameters) can be used to exit verbatim | |
| 179 mode. | |
| 238 | 180 |
| 181 'begin';; enter multi-line mode | |
|
260
33e1a05864a6
Add "verbatim multi-line" mode, with commands disabled
mikael@frmp8452
parents:
254
diff
changeset
|
182 'verbatim';; enter verbatim multi-line mode |
| 238 | 183 'send';; send the current multi-line message to the currently selected buddy |
| 184 'abort';; leave multi-line mode without sending the message | |
| 185 | |
| 199 | 186 /quit:: |
| 208 | 187 Disconnect and leave `mcabber(1)`. |
| 188 | |
| 436 | 189 /rawxml send:: |
| 190 'send' string: send string (raw XML format) to the Jabber server. No check is done on the string provided. BEWARE! Use this only if you know what you are doing, or you could terminate the connection. | |
| 191 | |
| 208 | 192 /rename nickname:: |
| 193 Rename current buddy to the given nickname. | |
| 229 | 194 This command does not work for groups, at the moment (but you can move |
| 450 | 195 the buddies to another group with the "/move" command). |
| 196 | |
| 601 | 197 /room join|leave|names|nick|privmsg|remove|topic|unlock|destroy:: |
| 593 | 198 /room invite|kick|ban|role|affil:: |
| 450 | 199 The 'room' command handles Multi-User Chat room actions. |
| 200 | |
| 487 | 201 'join' room nick;; join "room", using "nick" as nickname |
| 202 'leave' [message];; leave the current room | |
| 203 'names';; display members of the current room | |
| 204 'nick' nick;; change your nickname in the current room | |
| 491 | 205 'privmsg' nick msg;; send private message "msg" to "nick" |
| 487 | 206 'remove';; remove the current room from the roster (you must have left this room before) |
| 207 'topic';; set topic for current room | |
| 208 'unlock';; unlock current room (if you are the owner) | |
| 601 | 209 'destroy' [reason];; destroy the current room (use with care!) |
| 573 | 210 'whois' nick;; display MUC information about "nick" |
| 593 | 211 'ban' jid [reason];; ban jid from the current room |
| 212 'invite' jid [reason];; invite jid to the current room | |
| 213 'kick' nick [reason];; kick "nick" from the current room | |
| 214 'role' jid role [reason];; change jid's role (role can be "none", "visitor", "participant", "moderator") | |
| 215 'affil' jid affil [reason];; change jid's affiliation (affil can be "none", "member", "admin", "owner") | |
| 199 | 216 |
| 330 | 217 /roster bottom|top|hide_offline|show_offline|toggle_offline:: |
| 218 /roster alternate|unread_first|unread_next:: | |
| 265 | 219 /roster search bud:: |
| 220 The 'roster' command manipulates the roster/buddylist. Here are the available parameters: | |
| 199 | 221 |
| 265 | 222 'bottom';; jump to the bottom of the roster |
| 223 'top';; jump to the top of the roster | |
|
377
00809e3e327e
Add "/roster up" and "/roster down"
Mikael Berthe <mikael@lilotux.net>
parents:
372
diff
changeset
|
224 'up';; move up in the roster |
|
00809e3e327e
Add "/roster up" and "/roster down"
Mikael Berthe <mikael@lilotux.net>
parents:
372
diff
changeset
|
225 'down';; move down in the roster |
| 202 | 226 'hide_offline';; hide offline buddies |
| 227 'show_offline';; show offline buddies | |
|
290
f63839a4cb35
Add /roster toggle_offline
Mikael Berthe <mikael@lilotux.net>
parents:
289
diff
changeset
|
228 'toggle_offline';; toggle display of offline buddies |
| 265 | 229 'search' bud;; search for a buddy with a name or buddy containing "bud" (only in the displayed buddylist) |
| 330 | 230 'alternate';; jump to alternate buddy. The "alternate" buddy is the last buddy left while being in chat mode (this command is thus especially useful after commands like "/roster unread_first") |
| 236 | 231 'unread_first';; jump to the first unread message |
| 232 'unread_next';; jump to the next unread message | |
| 199 | 233 |
| 234 /say text:: | |
| 491 | 235 Send the "text" message to the currently selected buddy. Can be useful |
| 199 | 236 if you want to send a message beginning with a slash, for example. |
| 237 | |
| 480 | 238 /say_to jid text:: |
| 491 | 239 Send the "text" message to the specified jid. |
| 480 | 240 Please note that this command doesn't set the default resource for |
| 241 a contact, so if you want to send several messages to a specific | |
| 242 ressource you will have to use "/say_to" for each message. | |
| 243 | |
| 522 | 244 /status [online|avail|invisible|free|dnd|notavail|away [-|StatusMessage]]:: |
| 245 Show or set the current status. + | |
| 246 If no status is specified, display the current status. + | |
|
320
dce1dd4d0ca8
Update documentation for "/status status message"
Mikael Berthe <mikael@lilotux.net>
parents:
310
diff
changeset
|
247 If a status message is specified, it will overrride the message* |
| 522 | 248 variables (these variables can be set in the configuration file). |
| 249 If no relevant message* variable is set and no status message provided, | |
| 250 the current status message is kept. If StatusMessage is "-", the | |
| 251 current status message is cleared. | |
| 199 | 252 |
| 450 | 253 /status_to jid online|avail|invisible|free|dnd|notavail|away [StatusMessage]:: |
| 254 Send the requested status to the specified Jabber user. + | |
| 255 Note: this status will be overridden by subsequent "/status" commands. | |
| 256 If you are using the auto-away feature, the status will overridden | |
| 257 too. + | |
| 258 Note: The jid can include a resource (i.e. user@server/resource). | |
| 259 | |
| 623 | 260 /version:: |
| 261 Display mcabber version | |
| 262 | |
| 199 | 263 CONFIGURATION FILE |
| 264 ------------------ | |
| 265 See the provided sample configuration file, which should be self-documented. | |
| 198 | 266 |
| 200 | 267 FILES |
| 268 ----- | |
| 202 | 269 The following files can be used by `mcabber(1)`: |
| 200 | 270 |
| 271 $HOME/.mcabber/mcabberrc Default configuration file | |
| 272 $HOME/.mcabberrc Configuration file used if no other has been found | |
| 273 $HOME/.mcabber/histo/ Default directory for storing chat history files, if enabled | |
| 274 | |
| 198 | 275 BUGS |
| 276 ---- | |
| 349 | 277 Certainly. Please tell me if you find one! :-) |
| 198 | 278 |
| 279 AUTHOR | |
| 280 ------ | |
| 222 | 281 Written by mailto:mcabber@lilotux.net[Mikael BERTHE]. + |
| 204 | 282 Originally based on http://cabber.sourceforge.net[Cabber], please |
| 198 | 283 consult the AUTHORS file for details. |
| 284 | |
| 285 RESOURCES | |
| 286 --------- | |
| 202 | 287 http://www.lilotux.net/~mikael/mcabber/[Main web site] |
| 198 | 288 |
| 289 COPYING | |
| 290 ------- | |
| 202 | 291 Copyright (C) 2005 Mikael Berthe. + |
| 292 Some portions are Copyright (C) 2002-2004 mailto:cabber@ajmacias.com[]. | |
| 198 | 293 |
| 294 Free use of this software is granted under the terms of the GNU General Public | |
| 295 License (GPL). | |
| 296 |