Mercurial > hg
annotate mcabber/doc/mcabber.1.txt @ 872:a0ddc43b421e
Don't stop when there is no configuration file
author | Mikael Berthe <mikael@lilotux.net> |
---|---|
date | Thu, 25 May 2006 22:39:37 +0200 |
parents | 4b77a2ab18e5 |
children | e583d617838a |
rev | line source |
---|---|
198 | 1 MCABBER(1) |
2 =========== | |
222 | 3 Mikael BERTHE <mcabber@lilotux.net> |
829 | 4 v0.7.7-dev, May 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 |
854 | 23 Here are some of the features of `mcabber`: |
24 | |
25 - 'SSL support'. | |
26 - 'MUC support' (Multi-User Chat). | |
27 - 'History logging:' If enabled (see the CONFIGURATION FILE section), | |
28 `mcabber` can save discussions to history log files. | |
29 - 'Commands completion:' If possible, `mcabber` will try to complete your | |
30 command line if you hit the Tab key. | |
31 - 'Input line history:' Any message or command entered is in the input line | |
32 history and can be reused easily. | |
33 - 'External actions:' Some events (like receiving a message) can trigger an | |
34 external action such as a shell script if you enable it in your | |
35 configuration file. A sample events script ("eventcmd") is provided with | |
36 `mcabber` source code, in the contrib directory. | |
37 | |
38 OPTIONS | |
39 ------- | |
40 --help, -h:: | |
41 Quick help usage message | |
42 | |
43 -f configfile:: | |
44 Use configuration file 'configfile' | |
45 | |
46 WINDOWS/PANES | |
47 ------------- | |
202 | 48 The `mcabber(1)` screen is divided into 4 regions. |
200 | 49 The 'roster', alias 'buddylist', is on the left. The 'chat window', or chat |
50 buffer, is on the right. The 'input line' lies at the bottom of the screen, | |
51 under a small 'log window'. | |
52 | |
775
b4befb3052e5
Update NEWS, ChangeLog and documentation
Mikael Berthe <mikael@lilotux.net>
parents:
710
diff
changeset
|
53 Two status lines surround the log window. The bottom status line is the |
b4befb3052e5
Update NEWS, ChangeLog and documentation
Mikael Berthe <mikael@lilotux.net>
parents:
710
diff
changeset
|
54 "main status line" and reflects mcabber general status. The other line |
b4befb3052e5
Update NEWS, ChangeLog and documentation
Mikael Berthe <mikael@lilotux.net>
parents:
710
diff
changeset
|
55 is the "chat status line" and shows the status of the currently selected |
b4befb3052e5
Update NEWS, ChangeLog and documentation
Mikael Berthe <mikael@lilotux.net>
parents:
710
diff
changeset
|
56 buddy. |
b4befb3052e5
Update NEWS, ChangeLog and documentation
Mikael Berthe <mikael@lilotux.net>
parents:
710
diff
changeset
|
57 |
204 | 58 To display buddies chat buffers, you will have to enter 'chat mode'. |
59 You can enter chat mode by pressing enter, and leave chat mode with the ESC | |
229 | 60 key. Simply sending a message will also enable chat mode. |
204 | 61 |
854 | 62 There are several advantages to the two-mode implementation: first, it allows |
63 accurate "unread" message functionality, as described in the next section; | |
64 without this, merely scrolling to a specific buddy will "read" the new | |
65 messages of all buddies in-between. Second, it allows quickly hiding the | |
66 conversation with a single keystroke. Third, it allows jumping between | |
67 the few buddies with whom you are conversing with the '/roster alternate' | |
68 command described in another section, without having to manually scroll | |
69 back and forth. | |
200 | 70 |
71 KEYS | |
72 ---- | |
229 | 73 Text typing occurs in the 'input line'; basic operations are supported |
74 (left arrow, right arrow, home/end keys, insert, delete, backspace...). | |
200 | 75 |
76 PageUp and PageDown keys are used to move in the roster. | |
77 | |
618 | 78 Up and Down arrow keys can be used to move in the input line history; they |
79 jump to the previous/next line from the history beginning with the same string | |
80 (from first column to the cursor column). | |
81 | |
200 | 82 To send a message, move to the choosen buddy in the buddylist, type your |
83 message and hit enter. If the line begins with a slash, this will be | |
84 interpreted as a command (see the COMMAND section below). Hit escape to | |
85 leave the chat mode. | |
86 | |
87 Here is a quick description of the key bindings: | |
88 | |
89 Ctrl-a:: Go to the beginning of the input line | |
90 Ctrl-e:: Go to the end of the input line | |
618 | 91 Ctrl-l:: Force a refresh |
92 Up/Down:: Move in the input line history | |
200 | 93 PgUp/PgDown:: Move inside the roster (buddylist) |
94 Tab:: Complete current word, in the input line | |
95 Ctrl-g:: Cancel completion / ctrl-g | |
96 Ctrl-p/Ctrl-n:: Scroll up/down half a screen in the buffer window (chat mode) | |
775
b4befb3052e5
Update NEWS, ChangeLog and documentation
Mikael Berthe <mikael@lilotux.net>
parents:
710
diff
changeset
|
97 Ctrl-Left:: Move the cursor back to the start of the current or previous word |
b4befb3052e5
Update NEWS, ChangeLog and documentation
Mikael Berthe <mikael@lilotux.net>
parents:
710
diff
changeset
|
98 Ctrl-Right:: Move the cursor forward to the end of the current or next word |
200 | 99 Ctrl-u:: Delete from beginning of the line to the cursor |
100 Ctrl-k:: Delete from the cursor to the end of line | |
101 Ctrl-w:: Backward kill word | |
102 Ctrl-t:: Transpose chars | |
263 | 103 Ctrl-o:: Accept line and put the next history line in the input line (accept-line-and-down-history) |
236 | 104 Ctrl-q:: Jump to the next unread message |
198 | 105 |
854 | 106 Additional key bindings may be specified using the /bind command described |
107 in the COMMANDS section. | |
108 | |
109 MCABBER'S ROSTER | |
110 ---------------- | |
111 The first listed resource on the roster is '[status]', which keeps a log of | |
112 everything that appears in the short log window below the main chat area. | |
113 While the log window was designed for showing the latest few elements, the | |
114 dedicated '[status]' buffer allows more comfortable viewing of the log, as | |
115 well as scrolling it in a standard manner. | |
116 | |
117 Group names are displayed above the resources that are within them, and are | |
118 indicated by '---' to the left of the name. | |
119 | |
120 For every real Jabber resource, the roster displays four pieces of information: | |
121 the resource's name or alias, its online status, its authorization status, and | |
122 whether there are unread messages from the resource waiting for you. | |
123 | |
124 The online status is one of the following: | |
199 | 125 |
854 | 126 'o';; online |
127 'f';; free for chat | |
128 'a';; away | |
129 'n';; not available (labeled 'extended away' in some clients) | |
130 'd';; do not disturb | |
131 'i';; invisible (displayed only for your resource) | |
132 '_';; offline (or invisible to you) | |
133 '?';; unknown, usually meaning you are not authorized to see this resource's status | |
134 'x';; a conference room in which you are not participating | |
135 'C';; a conference room in which you are participating | |
199 | 136 |
854 | 137 The authorization status indicates whether a resource is authorized to receive |
138 your online status updates, and is displayed by the brackets surrounding the | |
139 resource's online status. Square brackets, like '[o]', indicate that this | |
140 resource is authorized to receive your status. Curly braces, like '\{o\}', | |
141 indicate that they are not authorized to receive your status. | |
142 | |
143 When there are unread messages from the resource which you have not looked at, | |
144 a hash mark ('#') appears in the leftmost section of the roster for that | |
145 resource. The hash mark disappears once you view that resource's message log. | |
146 | |
147 Examples: | |
148 | |
149 ' --- Buds';; This is a group named 'Buds' | |
150 '#[o] John';; John is online, can see your status, and sent you a message that you did not read yet | |
151 ' \{?\} Sally';; Neither you nor Sally have authorized each other to see your online status | |
152 ' \{a\} Jane';; Jane is away, but she cannot see your online status | |
153 '#[C] x@y.c';; You are participating in x@y.c conference room, and there are unread messages | |
154 | |
155 COMMANDS RELATED TO MCABBER | |
156 --------------------------- | |
870 | 157 /alias [name [= command line]]:: |
289 | 158 Add "name" as an alias for "command line". + |
159 Aliases are expanded only once, thus they can not be chained. + | |
870 | 160 "/alias name" displays the value associated with the "name" alias; + |
289 | 161 "/alias name =" unsets the "name" alias. + |
870 | 162 "/alias" displays a list of the existing aliases. + |
286
a3d65d7f0bc3
Add /alias documentation
Mikael Berthe <mikael@lilotux.net>
parents:
277
diff
changeset
|
163 Example: "/alias away = status away". |
289 | 164 |
870 | 165 /bind [keycode [= command line]]:: |
289 | 166 Bind a command line to the key with the "keycode" code number. + |
432 | 167 Keycodes of unused keys are displayed by `mcabber` in the log window |
289 | 168 when pressing the key, for example "Unknown key=265". + |
870 | 169 "/bind keycode" displays the command line bound to the given keycode; + |
170 "/bind keycode =" unbinds the given keycode. + | |
171 "/bind" displays a list of the bound keycodes. + | |
289 | 172 Note: aliases can be used in key bindings. + |
450 | 173 Example: "/bind 265 = status online" (265 is F1 for me, but it may |
289 | 174 depend on your ncurses installation). |
286
a3d65d7f0bc3
Add /alias documentation
Mikael Berthe <mikael@lilotux.net>
parents:
277
diff
changeset
|
175 |
870 | 176 /buffer clear|purge|top|bottom|date|%|search_backward|search_forward:: |
202 | 177 The 'buffer' command manipulates the current buddy's buffer |
178 (chat window). | |
199 | 179 |
465
52171a3dc199
Update manual page (/buffer command)
Mikael Berthe <mikael@lilotux.net>
parents:
450
diff
changeset
|
180 'clear';; clear the current buddy chat window |
870 | 181 'purge';; purge the current buddy chat window |
511 | 182 '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
|
183 'top';; jump to the top of the current buddy chat buffer |
511 | 184 'up' [n];; scroll the buffer up n lines (default: half a screen) |
185 'down' [n];; scroll the buffer down n lines (default: half a screen) | |
618 | 186 '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) |
187 '%' n;; jump to position %n of the buddy chat buffer | |
491 | 188 'search_backward' text;; search for "text" in the current buddy chat buffer |
189 'search_forward' text;; search for "text" in the current buddy chat buffer | |
199 | 190 |
191 /clear:: | |
206 | 192 The 'clear' command is actually an alias for "/buffer clear". |
199 | 193 |
870 | 194 /help [command]:: |
195 Display generic help or help about a specific mcabber command. | |
196 | |
854 | 197 /quit:: |
198 Disconnect and leave `mcabber(1)`. | |
199 | |
200 /version:: | |
201 Display mcabber version | |
202 | |
203 COMMANDS RELATED TO THE SERVER AND CONNECTION | |
204 --------------------------------------------- | |
298
35cda94e570d
Add /connect and /disconnect commands
Mikael Berthe <mikael@lilotux.net>
parents:
290
diff
changeset
|
205 /connect:: |
35cda94e570d
Add /connect and /disconnect commands
Mikael Berthe <mikael@lilotux.net>
parents:
290
diff
changeset
|
206 Establish connection to the Jabber server. |
35cda94e570d
Add /connect and /disconnect commands
Mikael Berthe <mikael@lilotux.net>
parents:
290
diff
changeset
|
207 |
35cda94e570d
Add /connect and /disconnect commands
Mikael Berthe <mikael@lilotux.net>
parents:
290
diff
changeset
|
208 /disconnect:: |
35cda94e570d
Add /connect and /disconnect commands
Mikael Berthe <mikael@lilotux.net>
parents:
290
diff
changeset
|
209 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
|
210 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
|
211 buddylist is empty when disconnected. |
35cda94e570d
Add /connect and /disconnect commands
Mikael Berthe <mikael@lilotux.net>
parents:
290
diff
changeset
|
212 |
829 | 213 /event #n|* accept|ignore|reject:: |
775
b4befb3052e5
Update NEWS, ChangeLog and documentation
Mikael Berthe <mikael@lilotux.net>
parents:
710
diff
changeset
|
214 /event list:: |
829 | 215 Tell mcabber what to do about a pending event. + |
216 If the first parameter is "*", the command will apply to all | |
217 queued events. | |
775
b4befb3052e5
Update NEWS, ChangeLog and documentation
Mikael Berthe <mikael@lilotux.net>
parents:
710
diff
changeset
|
218 |
b4befb3052e5
Update NEWS, ChangeLog and documentation
Mikael Berthe <mikael@lilotux.net>
parents:
710
diff
changeset
|
219 'accept';; accept the event #n |
b4befb3052e5
Update NEWS, ChangeLog and documentation
Mikael Berthe <mikael@lilotux.net>
parents:
710
diff
changeset
|
220 'ignore';; remove the event #n from the list |
b4befb3052e5
Update NEWS, ChangeLog and documentation
Mikael Berthe <mikael@lilotux.net>
parents:
710
diff
changeset
|
221 'reject';; reject the event #n |
b4befb3052e5
Update NEWS, ChangeLog and documentation
Mikael Berthe <mikael@lilotux.net>
parents:
710
diff
changeset
|
222 'list';; list all pending events |
b4befb3052e5
Update NEWS, ChangeLog and documentation
Mikael Berthe <mikael@lilotux.net>
parents:
710
diff
changeset
|
223 |
854 | 224 /rawxml send:: |
225 '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. | |
226 | |
227 COMMANDS RELATED TO THE ROSTER AND JABBER RESOURCES | |
228 --------------------------------------------------- | |
229 /add [jid [nickname]]:: | |
230 Add the "jid" Jabber user to our roster (default group), and send a | |
231 notification request to this buddy. If no nickname is specified, the | |
232 jid is used. If no jid (or an empty string "") is provided or if jid | |
233 is ".", the current buddy is used. | |
234 | |
235 /authorization allow|cancel|request|request_unsubscribe [jid]:: | |
236 Manage the presence subscriptions. + | |
237 If no jid is provided, the current buddy is used. | |
238 | |
239 'allow';; allow the buddy to receive your presence updates | |
240 'cancel';; cancel the buddy' subscription to your presence updates | |
241 'request';; request a subscription to the buddy's presence updates | |
242 'request_unsubscribe';; request unsubscription from the buddy's presence updates | |
243 | |
244 /del:: | |
245 Delete the current buddy from our roster, unsubscribe from its presence | |
246 notification and unsubscribe it from ours. | |
247 | |
240 | 248 /group fold|unfold|toggle:: |
249 The 'group' command changes the current group display. | |
199 | 250 |
637 | 251 'fold';; fold (shrink) the current group tree in the roster |
240 | 252 'unfold';; unfold (expand) the current group tree in the roster |
253 'toggle';; toggle the state (fold/unfold) of the current tree | |
199 | 254 |
255 /info:: | |
440
264f40222872
Update documentation (/info command)
Mikael Berthe <mikael@lilotux.net>
parents:
436
diff
changeset
|
256 Display info on the selected entry (user, agent, group...). + |
264f40222872
Update documentation (/info command)
Mikael Berthe <mikael@lilotux.net>
parents:
436
diff
changeset
|
257 For users, resources are displayed with the status, priority and |
264f40222872
Update documentation (/info command)
Mikael Berthe <mikael@lilotux.net>
parents:
436
diff
changeset
|
258 status message (if available) of each resource. |
199 | 259 |
210 | 260 /move [groupname]:: |
261 Move the current buddy to the requested group. If no group is | |
623 | 262 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
|
263 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
|
264 to jump to the moved buddy. |
210 | 265 |
839 | 266 /msay begin|verbatim|send|send_to|toggle|toggle_verbatim|abort:: |
238 | 267 Send a multi-line message. To write a single message with several |
289 | 268 lines, the 'multi-line mode' should be used. + |
269 In multi-line mode, each line (except command lines) typed in the input | |
270 line will be added to the multi-line message. Once the message is | |
450 | 271 finished, it can be sent to the current selected buddy with the "/msay |
272 send" command. + | |
810 | 273 The 'begin' subcommand enables multi-line mode. Note that it allows |
274 a message subject to be specified. + | |
289 | 275 The 'verbatim' multi-line mode disables commands, so that it is |
276 possible to enter lines starting with a slash. Only the "/msay" | |
277 command (with send or abort parameters) can be used to exit verbatim | |
799 | 278 mode. + |
839 | 279 The 'toggle' and 'toggle_verbatim' subcommands can be bound to a key to |
280 use the multi-line mode quickly (for example, "bind M109 = msay toggle" | |
281 to switch using the Meta-m combination). | |
238 | 282 |
810 | 283 'begin' [subject];; enter multi-line mode |
284 'verbatim';; enter verbatim multi-line mode | |
285 'send';; send the current multi-line message to the currently selected buddy | |
286 'send_to' jid;; send the current multi-line message to "jid" | |
287 'toggle';; switch to/from multi-line mode (begin/send) | |
839 | 288 'toggle_verbatim';; same with verbatim multi-line mode |
810 | 289 'abort';; leave multi-line mode without sending the message |
238 | 290 |
208 | 291 /rename nickname:: |
292 Rename current buddy to the given nickname. | |
229 | 293 This command does not work for groups, at the moment (but you can move |
450 | 294 the buddies to another group with the "/move" command). |
295 | |
700 | 296 /request time|version [jid]:: |
297 Send a "IQ" query to the current buddy, or to the specified Jabber | |
298 user. If the resource is not provided with the jid, mcabber will | |
299 send the query to all known resources for this user. | |
300 | |
601 | 301 /room join|leave|names|nick|privmsg|remove|topic|unlock|destroy:: |
593 | 302 /room invite|kick|ban|role|affil:: |
450 | 303 The 'room' command handles Multi-User Chat room actions. |
304 | |
841
f8c0447beec2
Allow "/room join . [nick]" if the current item is a MUC room
Mikael Berthe <mikael@lilotux.net>
parents:
839
diff
changeset
|
305 'join' [room [nick]];; join "room", using "nick" as nickname. If no nickname is provided, the "nickname" option value is used (see sample configuration file). If the currently selected entry is correctly recognized as a room by mcabber, the shortcut "." can be used instead of the full room id. |
487 | 306 'leave' [message];; leave the current room |
307 'names';; display members of the current room | |
308 'nick' nick;; change your nickname in the current room | |
491 | 309 'privmsg' nick msg;; send private message "msg" to "nick" |
487 | 310 'remove';; remove the current room from the roster (you must have left this room before) |
311 'topic';; set topic for current room | |
312 'unlock';; unlock current room (if you are the owner) | |
601 | 313 'destroy' [reason];; destroy the current room (use with care!) |
573 | 314 'whois' nick;; display MUC information about "nick" |
593 | 315 'ban' jid [reason];; ban jid from the current room |
316 'invite' jid [reason];; invite jid to the current room | |
317 'kick' nick [reason];; kick "nick" from the current room | |
318 'role' jid role [reason];; change jid's role (role can be "none", "visitor", "participant", "moderator") | |
319 'affil' jid affil [reason];; change jid's affiliation (affil can be "none", "member", "admin", "owner") | |
199 | 320 |
330 | 321 /roster bottom|top|hide_offline|show_offline|toggle_offline:: |
710 | 322 /roster hide|show|toggle:: |
330 | 323 /roster alternate|unread_first|unread_next:: |
265 | 324 /roster search bud:: |
325 The 'roster' command manipulates the roster/buddylist. Here are the available parameters: | |
199 | 326 |
265 | 327 'bottom';; jump to the bottom of the roster |
328 '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
|
329 'up';; move up in the roster |
00809e3e327e
Add "/roster up" and "/roster down"
Mikael Berthe <mikael@lilotux.net>
parents:
372
diff
changeset
|
330 'down';; move down in the roster |
202 | 331 'hide_offline';; hide offline buddies |
332 'show_offline';; show offline buddies | |
290
f63839a4cb35
Add /roster toggle_offline
Mikael Berthe <mikael@lilotux.net>
parents:
289
diff
changeset
|
333 'toggle_offline';; toggle display of offline buddies |
710 | 334 'hide';; hide roster (full-width chat window) |
335 'show';; show roster | |
336 'toggle';; toggle roster visibility | |
265 | 337 'search' bud;; search for a buddy with a name or buddy containing "bud" (only in the displayed buddylist) |
330 | 338 '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 | 339 'unread_first';; jump to the first unread message |
340 'unread_next';; jump to the next unread message | |
199 | 341 |
342 /say text:: | |
491 | 343 Send the "text" message to the currently selected buddy. Can be useful |
199 | 344 if you want to send a message beginning with a slash, for example. |
345 | |
480 | 346 /say_to jid text:: |
491 | 347 Send the "text" message to the specified jid. |
480 | 348 Please note that this command doesn't set the default resource for |
349 a contact, so if you want to send several messages to a specific | |
350 ressource you will have to use "/say_to" for each message. | |
351 | |
522 | 352 /status [online|avail|invisible|free|dnd|notavail|away [-|StatusMessage]]:: |
353 Show or set the current status. + | |
354 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
|
355 If a status message is specified, it will overrride the message* |
522 | 356 variables (these variables can be set in the configuration file). |
357 If no relevant message* variable is set and no status message provided, | |
358 the current status message is kept. If StatusMessage is "-", the | |
359 current status message is cleared. | |
199 | 360 |
450 | 361 /status_to jid online|avail|invisible|free|dnd|notavail|away [StatusMessage]:: |
362 Send the requested status to the specified Jabber user. + | |
660 | 363 If the specified jid is ".", the current buddy is used. + |
450 | 364 Note: this status will be overridden by subsequent "/status" commands. |
365 If you are using the auto-away feature, the status will overridden | |
366 too. + | |
367 Note: The jid can include a resource (i.e. user@server/resource). | |
368 | |
199 | 369 CONFIGURATION FILE |
370 ------------------ | |
854 | 371 See the provided sample configuration file, which should be self-documenting. |
198 | 372 |
200 | 373 FILES |
374 ----- | |
202 | 375 The following files can be used by `mcabber(1)`: |
200 | 376 |
377 $HOME/.mcabber/mcabberrc Default configuration file | |
378 $HOME/.mcabberrc Configuration file used if no other has been found | |
379 $HOME/.mcabber/histo/ Default directory for storing chat history files, if enabled | |
380 | |
198 | 381 BUGS |
382 ---- | |
349 | 383 Certainly. Please tell me if you find one! :-) |
198 | 384 |
385 AUTHOR | |
386 ------ | |
222 | 387 Written by mailto:mcabber@lilotux.net[Mikael BERTHE]. + |
204 | 388 Originally based on http://cabber.sourceforge.net[Cabber], please |
198 | 389 consult the AUTHORS file for details. |
390 | |
391 RESOURCES | |
392 --------- | |
202 | 393 http://www.lilotux.net/~mikael/mcabber/[Main web site] |
198 | 394 |
395 COPYING | |
396 ------- | |
700 | 397 Copyright (C) 2005, 2006 Mikael Berthe. + |
202 | 398 Some portions are Copyright (C) 2002-2004 mailto:cabber@ajmacias.com[]. |
198 | 399 |
400 Free use of this software is granted under the terms of the GNU General Public | |
401 License (GPL). | |
402 |