1 <!DOCTYPE html PUBLIC
"-//W3C//DTD XHTML 1.1//EN"
2 "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
3 <html xmlns=
"http://www.w3.org/1999/xhtml" xml:
lang=
"en">
5 <meta http-equiv=
"Content-Type" content=
"text/html; charset=UTF-8" />
6 <meta name=
"generator" content=
"AsciiDoc 8.5.2" />
7 <title>MCABBER(
1)
</title>
8 <style type=
"text/css">
10 p
, li
, dt
, dd
, div
, pre
, h1
, h2
, h3
, h4
, h5
, h6
{
12 border: 1px solid red;
17 margin: 1em 5% 1em 5%;
22 text-decoration: underline
;
42 h1
, h2
, h3
, h4
, h5
, h6
{
44 font-family: sans-serif
;
51 border-bottom: 2px solid silver
;
69 border: 1px solid silver
;
88 font-family: sans-serif
;
94 span#revnumber
, span#revdate
, span#revremark
{
95 font-family: sans-serif
;
99 font-family: sans-serif
;
101 border-top: 2px solid silver
;
107 padding-bottom: 0.5em;
111 padding-bottom: 0.5em;
116 margin-bottom: 1.5em;
118 div
.tableblock
, div
.imageblock
, div
.exampleblock
, div
.verseblock
,
119 div
.quoteblock
, div
.literalblock
, div
.listingblock
, div
.sidebarblock
,
120 div
.admonitionblock
{
122 margin-bottom: 1.5em;
124 div
.admonitionblock
{
126 margin-bottom: 2.0em;
131 div
.content
{ /* Block element content. */
135 /* Block element titles. */
136 div
.title
, caption
.title
{
138 font-family: sans-serif
;
142 margin-bottom: 0.5em;
148 td div
.title:first-child
{
151 div
.content div
.title:first-child
{
154 div
.content
+ div
.title
{
158 div
.sidebarblock
> div
.content
{
160 border: 1px solid silver
;
164 div
.listingblock
> div
.content
{
165 border: 1px solid silver
;
170 div
.quoteblock
, div
.verseblock
{
174 border-left: 5px solid
#dddddd;
178 div
.quoteblock
> div
.attribution
{
183 div
.verseblock
> div
.content
{
186 div
.verseblock
> div
.attribution
{
190 /* DEPRECATED: Pre version 8.2.7 verse style literal block. */
191 div
.verseblock
+ div
.attribution
{
195 div
.admonitionblock
.icon
{
199 text-decoration: underline
;
201 padding-right: 0.5em;
203 div
.admonitionblock td
.content
{
205 border-left: 3px solid
#dddddd;
208 div
.exampleblock
> div
.content
{
209 border-left: 3px solid
#dddddd;
213 div
.imageblock div
.content
{ padding-left: 0; }
214 span
.image img
{ border-style: none
; }
215 a
.image:visited
{ color: white
; }
219 margin-bottom: 0.8em;
232 list-style-position: outside
;
235 list-style-type: decimal
;
238 list-style-type: lower-alpha
;
241 list-style-type: upper-alpha
;
244 list-style-type: lower-roman
;
247 list-style-type: upper-roman
;
250 div
.compact ul
, div
.compact ol
,
251 div
.compact p
, div
.compact p
,
252 div
.compact div
, div
.compact div
{
254 margin-bottom: 0.1em;
257 div
.tableblock
> table
{
258 border: 3px solid
#527bbd;
260 thead
, p
.table
.header
{
261 font-family: sans-serif
;
273 /* Because the table frame attribute is overriden by CSS in most browsers. */
274 div
.tableblock
> table
[frame
="void"] {
277 div
.tableblock
> table
[frame
="hsides"] {
278 border-left-style: none
;
279 border-right-style: none
;
281 div
.tableblock
> table
[frame
="vsides"] {
282 border-top-style: none
;
283 border-bottom-style: none
;
289 margin-bottom: 0.8em;
292 padding-bottom: 15px;
294 dt
.hdlist1
.strong
, td
.hdlist1
.strong
{
300 padding-right: 0.8em;
306 div
.hdlist
.compact tr
{
315 .footnote, .footnoteref {
319 span
.footnote
, span
.footnoteref
{
320 vertical-align: super
;
324 margin: 20px 0 20px 0;
328 #footnotes div
.footnote
{
334 border-top: 1px solid silver
;
344 div#footer-badges
{ display: none
; }
348 margin-bottom: 2.5em;
353 font-family: sans-serif
;
357 margin-bottom: 0.1em;
360 div
.toclevel1
, div
.toclevel2
, div
.toclevel3
, div
.toclevel4
{
376 /* Overrides for manpage documents */
379 padding-bottom: 0.5em;
380 border-top: 2px solid silver
;
381 border-bottom: 2px solid silver
;
391 div#toc
{ display: none
; }
394 /* Workarounds for IE6's broken and incomplete CSS2. */
396 div
.sidebar-content
{
398 border: 1px solid silver
;
401 div
.sidebar-title
, div
.image-title
{
403 font-family: sans-serif
;
406 margin-bottom: 0.5em;
409 div
.listingblock div
.content
{
410 border: 1px solid silver
;
415 div
.quoteblock-attribution
{
420 div
.verseblock-content
{
423 div
.verseblock-attribution
{
428 div
.exampleblock-content
{
429 border-left: 3px solid
#dddddd;
433 /* IE6 sets dynamically generated links as visited. */
434 div#toc
a:visited
{ color: blue
; }
436 <script type=
"text/javascript">
438 window
.onload = function(){asciidoc
.footnotes();}
439 var asciidoc
= { // Namespace.
441 /////////////////////////////////////////////////////////////////////
442 // Table Of Contents generator
443 /////////////////////////////////////////////////////////////////////
445 /* Author: Mihai Bazon, September 2002
446 * http://students.infoiasi.ro/~mishoo
448 * Table Of Content generator
451 * Feel free to use this script under the terms of the GNU General Public
452 * License, as long as you do not remove or alter this notice.
455 /* modified by Troy D. Hanson, September 2006. License: GPL */
456 /* modified by Stuart Rackham, 2006, 2009. License: GPL */
459 toc: function (toclevels
) {
461 function getText(el
) {
463 for (var i
= el
.firstChild
; i
!= null; i
= i
.nextSibling
) {
464 if (i
.nodeType
== 3 /* Node.TEXT_NODE */) // IE doesn't speak constants.
466 else if (i
.firstChild
!= null)
472 function TocEntry(el
, text
, toclevel
) {
475 this.toclevel
= toclevel
;
478 function tocEntries(el
, toclevels
) {
479 var result
= new Array
;
480 var re
= new RegExp('[hH]([2-'+(toclevels
+1)+'])');
481 // Function that scans the DOM tree for header elements (the DOM2
482 // nodeIterator API would be a better technique but not supported by all
484 var iterate = function (el
) {
485 for (var i
= el
.firstChild
; i
!= null; i
= i
.nextSibling
) {
486 if (i
.nodeType
== 1 /* Node.ELEMENT_NODE */) {
487 var mo
= re
.exec(i
.tagName
);
488 if (mo
&& (i
.getAttribute("class") || i
.getAttribute("className")) != "float") {
489 result
[result
.length
] = new TocEntry(i
, getText(i
), mo
[1]-1);
499 var toc
= document
.getElementById("toc");
500 var entries
= tocEntries(document
.getElementById("content"), toclevels
);
501 for (var i
= 0; i
< entries
.length
; ++i
) {
502 var entry
= entries
[i
];
503 if (entry
.element
.id
== "")
504 entry
.element
.id
= "_toc_" + i
;
505 var a
= document
.createElement("a");
506 a
.href
= "#" + entry
.element
.id
;
507 a
.appendChild(document
.createTextNode(entry
.text
));
508 var div
= document
.createElement("div");
510 div
.className
= "toclevel" + entry
.toclevel
;
511 toc
.appendChild(div
);
513 if (entries
.length
== 0)
514 toc
.parentNode
.removeChild(toc
);
518 /////////////////////////////////////////////////////////////////////
519 // Footnotes generator
520 /////////////////////////////////////////////////////////////////////
522 /* Based on footnote generation code from:
523 * http://www.brandspankingnew.net/archive/2005/07/format_footnote.html
526 footnotes: function () {
527 var cont
= document
.getElementById("content");
528 var noteholder
= document
.getElementById("footnotes");
529 var spans
= cont
.getElementsByTagName("span");
532 for (i
=0; i
<spans
.length
; i
++) {
533 if (spans
[i
].className
== "footnote") {
535 // Use [\s\S] in place of . so multi-line matches work.
536 // Because JavaScript has no s (dotall) regex flag.
537 note
= spans
[i
].innerHTML
.match(/\s*\[([\s\S]*)]\s*/)[1];
538 noteholder
.innerHTML
+=
539 "<div class='footnote' id='_footnote_" + n
+ "'>" +
540 "<a href='#_footnoteref_" + n
+ "' title='Return to text'>" +
541 n
+ "</a>. " + note
+ "</div>";
543 "[<a id='_footnoteref_" + n
+ "' href='#_footnote_" + n
+
544 "' title='View footnote' class='footnote'>" + n
+ "</a>]";
545 var id
=spans
[i
].getAttribute("id");
546 if (id
!= null) refs
["#"+id
] = n
;
550 noteholder
.parentNode
.removeChild(noteholder
);
552 // Process footnoterefs.
553 for (i
=0; i
<spans
.length
; i
++) {
554 if (spans
[i
].className
== "footnoteref") {
555 var href
= spans
[i
].getElementsByTagName("a")[0].getAttribute("href");
556 href
= href
.match(/#.*/)[0]; // Because IE return full URL.
559 "[<a href='#_footnote_" + n
+
560 "' title='View footnote' class='footnote'>" + n
+ "</a>]";
573 MCABBER(
1) Manual Page
576 <div class=
"sectionbody">
578 a simple Jabber (XMPP) console client
583 <h2 id=
"_synopsis">SYNOPSIS
</h2>
584 <div class=
"sectionbody">
585 <div class=
"paragraph"><p><em>mcabber
</em> [ -h | -V | -f configfile ]
</p></div>
587 <h2 id=
"_description">DESCRIPTION
</h2>
588 <div class=
"sectionbody">
589 <div class=
"paragraph"><p><tt>mcabber(
1)
</tt> is a small Jabber (XMPP) console client.
<br />
590 For now it needs a configuration file to start, so please copy the sample
591 mcabberrc file and adapt your connection settings.
</p></div>
592 <div class=
"paragraph"><p>You also need to have an existing Jabber account to use this software, as
593 it cannot (un)register accounts yet.
</p></div>
594 <div class=
"paragraph"><p>Here are some of the features of
<tt>mcabber
</tt>:
</p></div>
595 <div class=
"ulist"><ul>
598 <em>SASL/SSL/TLS support
</em>.
603 <em>MUC support
</em> (Multi-User Chat).
608 <em>PGP, OTR support
</em>
613 <em>Chat States
</em> support (typing notifications)
618 <em>History logging:
</em> If enabled (see the CONFIGURATION FILE section),
619 <tt>mcabber
</tt> can save discussions to text history log files.
624 <em>Commands completion:
</em> If possible,
<tt>mcabber
</tt> will try to complete your
625 command line if you hit the Tab key.
630 <em>Input line history:
</em> Any message or command entered is in the input line
631 history and can be reused easily.
636 <em>External actions:
</em> Some events (like receiving a message) can trigger an
637 external action such as a shell script if you enable it in your
638 configuration file. A sample events script (
"eventcmd") is provided with
639 <tt>mcabber
</tt> source code, in the contrib directory.
644 <em>Modules:
</em> <tt>mcabber
</tt> can load modules (a.k.a. plugins) at runtime that
650 <h2 id=
"_options">OPTIONS
</h2>
651 <div class=
"sectionbody">
652 <div class=
"dlist"><dl>
658 Quick help usage message
666 Displays
<tt>mcabber
</tt> version and compile-time definitions.
674 Use configuration file
<em>configfile
</em>
679 <h2 id=
"_windows_panes">WINDOWS/PANES
</h2>
680 <div class=
"sectionbody">
681 <div class=
"paragraph"><p>The
<tt>mcabber(
1)
</tt> screen is divided into
4 regions.
682 The
<em>roster
</em>, alias
<em>buddylist
</em>, is on the left. The
<em>chat window
</em>, or chat
683 buffer, is on the right. The
<em>input line
</em> lies at the bottom of the screen,
684 under a small
<em>log window
</em>.
</p></div>
685 <div class=
"paragraph"><p>Two status lines surround the log window. The bottom status line is the
686 "main status line" and reflects mcabber general status. The other line
687 is the
"chat status line" and shows the status of the currently selected
689 <div class=
"paragraph"><p>To display buddies chat buffers, you will have to enter
<em>chat mode
</em>.
690 You can enter chat mode by pressing enter, and leave chat mode with the ESC
691 key. Simply sending a message will also enable chat mode.
</p></div>
692 <div class=
"paragraph"><p>There are several advantages to the two-mode implementation: first, it allows
693 accurate
"unread" message functionality, as described in the next section;
694 without this, merely scrolling to a specific buddy will
"read" the new
695 messages of all buddies in-between. Second, it allows quickly hiding the
696 conversation with a single keystroke. Third, it allows jumping between
697 the few buddies with whom you are conversing with the
<em>/roster alternate
</em>
698 command described in another section, without having to manually scroll
699 back and forth.
</p></div>
701 <h2 id=
"_keys">KEYS
</h2>
702 <div class=
"sectionbody">
703 <div class=
"paragraph"><p>Text typing occurs in the
<em>input line
</em>; basic operations are supported
704 (left arrow, right arrow, home/end keys, insert, delete, backspace
…).
</p></div>
705 <div class=
"paragraph"><p>PageUp and PageDown keys are used to move in the roster.
</p></div>
706 <div class=
"paragraph"><p>Up and Down arrow keys can be used to move in the input line history; they
707 jump to the previous/next line from the history beginning with the same string
708 (from first column to the cursor column).
</p></div>
709 <div class=
"paragraph"><p>To send a message, move to the chosen buddy in the buddylist, type your
710 message and hit enter. If the line begins with a slash, this will be
711 interpreted as a command (see the COMMAND section below). Hit escape to
712 leave the chat mode.
</p></div>
713 <div class=
"paragraph"><p>Here is a quick description of the default key bindings:
</p></div>
714 <div class=
"dlist"><dl>
728 Go to the beginning of the input line
736 Go to the end of the input line
752 Move in the input line history
760 Move inside the roster (buddylist)
768 Complete current word, in the input line
784 Abort multi-line messages and completions
792 Send/terminate a multi-line message
800 Scroll up/down half a screen in the buffer window (chat mode)
808 Move the cursor back to the start of the current or previous word
816 Move the cursor forward to the end of the current or next word
824 Delete from beginning of the line to the cursor
832 Delete from the cursor to the end of line
856 Accept line and put the next history line in the input line (accept-line-and-down-history)
860 <div class=
"paragraph"><p>Additional key bindings may be specified using the
<em>/bind
</em> command described
861 in the COMMANDS section.
</p></div>
863 <h2 id=
"_mcabber_8217_s_roster">MCABBER
’S ROSTER
</h2>
864 <div class=
"sectionbody">
865 <div class=
"paragraph"><p>The first listed resource on the roster is
<em>[status]
</em>, which keeps a log of
866 everything that appears in the short log window below the main chat area.
867 While the log window was designed for showing the latest few elements, the
868 dedicated
<em>[status]
</em> buffer allows more comfortable viewing of the log, as
869 well as scrolling it in a standard manner.
</p></div>
870 <div class=
"paragraph"><p>Group names are displayed above the resources that are within them, and are
871 indicated by
<em>---
</em> to the left of the name.
</p></div>
872 <div class=
"paragraph"><p>For every real Jabber resource, the roster displays four pieces of information:
873 the resource
’s name or alias, its online status, its authorization status, and
874 whether there are unread messages from the resource waiting for you.
</p></div>
875 <div class=
"paragraph"><p>The online status is one of the following:
</p></div>
876 <div class=
"dlist"><dl>
906 not available (labeled
<em>extended away
</em> in some clients)
922 invisible (displayed only for your resource)
930 offline (or invisible to you)
938 unknown, usually meaning you are not authorized to see this resource
’s status
946 a conference room in which you are not participating
954 a conference room in which you are participating
958 <div class=
"paragraph"><p>The authorization status indicates whether a resource is authorized to receive
959 your online status updates, and is displayed by the brackets surrounding the
960 resource
’s online status. Square brackets, like
<em>[o]
</em>, indicate that this
961 resource is authorized to receive your status. Curly braces, like
<em>{o}
</em>,
962 indicate that they are not authorized to receive your status.
</p></div>
963 <div class=
"paragraph"><p>When there are unread messages from the resource which you have not looked at,
964 a hash mark (
<em>#
</em>) appears in the leftmost section of the roster for that
965 resource. The hash mark disappears once you view that resource
’s message log.
</p></div>
966 <div class=
"paragraph"><p>Examples:
</p></div>
967 <div class=
"dlist"><dl>
973 This is a group named
<em>Buds
</em>
981 John is online, can see your status, and sent you a message that you did not read yet
989 Neither you nor Sally have authorized each other to see your online status
997 Jane is away, but she cannot see your online status
1000 <dt class=
"hdlist1">
1005 You are participating in x@y.c conference room, and there are unread messages
1010 <h2 id=
"_commands">COMMANDS
</h2>
1011 <div class=
"sectionbody">
1012 <div class=
"paragraph"><p>Please refer to the online help (command /help), it is probably more up-to-date than this manpage. Furthermore, help files have been translated into several languages.
<br />
1013 You will find an overview of the
<tt>mcabber
</tt> commands in this manual.
</p></div>
1015 <h2 id=
"_commands_related_to_mcabber">COMMANDS RELATED TO MCABBER
</h2>
1016 <div class=
"sectionbody">
1017 <div class=
"dlist"><dl>
1018 <dt class=
"hdlist1">
1019 /add [jid [nickname]]
1023 Add the
"jid" Jabber user to our roster (default group), and send a notification request to this buddy. If no nickname is specified, the jid is used. If no jid (or an empty string
"") is provided or if jid is
".", the current buddy is used.
1025 <div class=
"dlist"><dl>
1026 <dt class=
"hdlist1">
1027 [
<em>jid
</em> [nickname]]
1031 Add to our roster
"jid" as
"nickname"
1033 <div class=
"literalblock">
1034 <div class=
"content">
1035 <pre><tt>Example:
"/add somebody@jabber.server.com Somebody"</tt></pre>
1040 <dt class=
"hdlist1">
1041 /alias [name [= command line]]
1045 This command let you to add aliases which can simplify sophisticated commands.
<br />
1046 You can manage your aliases by:
1048 <div class=
"dlist"><dl>
1049 <dt class=
"hdlist1">
1054 Print list of currently defined aliases
1057 <dt class=
"hdlist1">
1062 Print the value of alias called
"name"
1065 <dt class=
"hdlist1">
1070 Unset alias called
"name"
1073 <dt class=
"hdlist1">
1074 <em>name
</em> = command line
1078 Set alias called
"name" with value
"command line"
1080 <div class=
"literalblock">
1081 <div class=
"content">
1082 <pre><tt>Example:
"/alias away = status away"</tt></pre>
1087 <dt class=
"hdlist1">
1088 /authorization allow|cancel|request|request_unsubscribe [jid]
1092 This command manages presence subscriptions: it allows you to request presence subscriptions from others on your roster, and allows you to control who receives your presence notifications.
<br />
1093 If no JID is provided, the currently-selected buddy is used.
1095 <div class=
"dlist"><dl>
1096 <dt class=
"hdlist1">
1101 Allow the buddy to receive your presence updates
1104 <dt class=
"hdlist1">
1109 Cancel the buddy
’s subscription to your presence updates
1112 <dt class=
"hdlist1">
1117 Request a subscription to the buddy
’s presence updates
1120 <dt class=
"hdlist1">
1121 <em>request_unsubscribe
</em>
1125 Request unsubscription from the buddy
’s presence updates
1130 <dt class=
"hdlist1">
1131 /bind [keycode [= command line]]
1135 Bind the command to the key given as
"keycode". To examine which keys are currently not used look at
<tt>mcabber
</tt> log window and press examined key. For example:
"Unknown key=265" means that you can bind some command to key #
265.
1137 <div class=
"dlist"><dl>
1138 <dt class=
"hdlist1">
1143 Display list of current bindings
1146 <dt class=
"hdlist1">
1151 Display the command line bound to this key
1154 <dt class=
"hdlist1">
1159 Unbind key with code
"keycode"
1162 <dt class=
"hdlist1">
1163 <em>keycode
</em> = command line
1167 Bind
"command line" to the key with code
"keycode"
1169 <div class=
"literalblock">
1170 <div class=
"content">
1171 <pre><tt>Example:
"/bind 265 = status away" (
265 is F1). +
1172 Note: keycodes can be different depending on your ncurses configuration. +
1173 Tip: aliases also can be used instead of commands.
</tt></pre>
1178 <dt class=
"hdlist1">
1179 /buffer clear|close|close_all|purge|list
1181 <dt class=
"hdlist1">
1182 /buffer top|bottom|date|%|search_backward|search_forward
1184 <dt class=
"hdlist1">
1185 /buffer scroll_lock|scroll_unlock|scroll_toggle
1187 <dt class=
"hdlist1">
1188 /buffer save filename
1192 Buddy
’s buffer manipulation command. Eg. you can search through buffer for
"text", clear chat window etc.
1194 <div class=
"dlist"><dl>
1195 <dt class=
"hdlist1">
1200 Clear the current buddy chat window
1203 <dt class=
"hdlist1">
1204 <em>close
</em> [jid]
1208 Empty all contents of the buffer and close the current buddy chat window
1211 <dt class=
"hdlist1">
1216 Empty all contents of the chat buffers and close the chat windows
1219 <dt class=
"hdlist1">
1220 <em>purge
</em> [jid]
1224 Clear the current buddy chat window and empty all contents of the chat buffer
1227 <dt class=
"hdlist1">
1232 Display the list of existing buffers, with their length (lines/blocks)
1235 <dt class=
"hdlist1">
1240 Jump to the top of the current buddy chat buffer
1243 <dt class=
"hdlist1">
1248 Jump to the bottom of the current buddy chat buffer
1251 <dt class=
"hdlist1">
1256 Scroll the buffer up [n] lines (default: half a screen)
1259 <dt class=
"hdlist1">
1264 Scroll the buffer down [n] lines (default: half a screen)
1267 <dt class=
"hdlist1">
1268 <em>date
</em> [date]
1272 Jump to the first line after the specified [date] in the chat buffer (date format:
"YYYY-mm-dd")
1275 <dt class=
"hdlist1">
1280 Jump to position %n of the buddy chat buffer
1283 <dt class=
"hdlist1">
1284 <em>search_backward
</em> text
1288 Search for [text] in the current buddy chat buffer
1291 <dt class=
"hdlist1">
1292 <em>search_forward
</em> text
1296 Search for [text] in the current buddy chat buffer
1299 <dt class=
"hdlist1">
1300 <em>scroll_lock
</em>
1304 Lock buffer scrolling
1307 <dt class=
"hdlist1">
1308 <em>scroll_unlock
</em>
1312 Unlock buffer scrolling
1315 <dt class=
"hdlist1">
1316 <em>scroll_toggle
</em>
1320 Toggle buffer scrolling (lock/unlock)
1323 <dt class=
"hdlist1">
1324 <em>save
</em> filename
1328 Save the contents of the current buffer to the file
"filename"
1333 <dt class=
"hdlist1">
1334 /chat_disable [--show-roster]
1338 Disable chat mode.
<br />
1339 With --show-roster, the fullscreen mode will be disabled.
1342 <dt class=
"hdlist1">
1347 This command is actually an alias for
"/buffer clear". It clears the current buddy chat window.
1350 <dt class=
"hdlist1">
1351 /color roster (status wildcard (color|-)|clear)
1353 <dt class=
"hdlist1">
1354 /color mucnick nick (color|-)
1356 <dt class=
"hdlist1">
1357 /color muc (jid|.|*) [on|preset|off|-]
1361 The
<em>color
</em> command allows setting dynamic color properties of the screen.
1363 <div class=
"dlist"><dl>
1364 <dt class=
"hdlist1">
1365 <em>roster
</em> clear
1369 Remove all color rules for the roster. All roster items will get its default color.
1372 <dt class=
"hdlist1">
1373 <em>roster
</em> status wildcard color
1377 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.
1380 <dt class=
"hdlist1">
1381 <em>mucnick
</em> nick (color|-)
1385 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
<em>preset
</em> coloring mode, but will stay the same in
<em>on
</em> coloring mode.
1388 <dt class=
"hdlist1">
1389 <em>muc
</em> (jid|.|*) [on|preset|off|-]
1393 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
<em>on
</em> colors all nicks,
<em>preset
</em> only the ones manually set by /color mucnick command and
<em>off
</em> colors none. If not specified, defaults to
<em>on
</em>. Mode
<em>-
</em> 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
<em>off
</em>.
1398 <dt class=
"hdlist1">
1403 Establish connection to the Jabber server.
1406 <dt class=
"hdlist1">
1411 Delete the current buddy from our roster, unsubscribe from its presence notification and unsubscribe it from ours.
1414 <dt class=
"hdlist1">
1419 Terminate the connection to the Jabber server.
<br />
1420 Note: the roster is only available when the connection to the server is active, so the buddylist is empty when disconnected.
1423 <dt class=
"hdlist1">
1428 Display
"message" in the log window.
1431 <dt class=
"hdlist1">
1432 /event #n|* accept|ignore|reject [event-specific arguments]
1434 <dt class=
"hdlist1">
1439 Tell mcabber what to do about pending events.
<br />
1440 If the first parameter is
<em>*
</em>, the command will apply to all queued events.
<br />
1441 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.
1443 <div class=
"dlist"><dl>
1444 <dt class=
"hdlist1">
1445 #N|* accept [event-specific arguments]
1449 Event number #N/All events will be accepted
1452 <dt class=
"hdlist1">
1453 #N|* ignore [event-specific arguments]
1457 Event number #N/All events will be ignored
1460 <dt class=
"hdlist1">
1461 #N|* reject [event-specific arguments]
1465 Event number #N/All events will be rejected
1468 <dt class=
"hdlist1">
1473 List all pending events
1478 <dt class=
"hdlist1">
1479 /group fold|unfold|toggle [groupname]
1483 This command changes the current group display.
1485 <div class=
"dlist"><dl>
1486 <dt class=
"hdlist1">
1487 <em>fold
</em> [groupname]
1491 Fold (shrink) the current/specified group tree in the roster
1494 <dt class=
"hdlist1">
1495 <em>unfold
</em> [groupname]
1499 Unfold (expand) the current/specified group tree in the roster
1502 <dt class=
"hdlist1">
1503 <em>toggle
</em> [groupname]
1507 Toggle the state (fold/unfold) of the current/specified tree
1512 <dt class=
"hdlist1">
1513 /help [command|+topic]
1517 Display help for command
"command" or topic
"topic".
<br />
1518 Example:
"/help buffer"
1521 <dt class=
"hdlist1">
1522 /iline fchar|bchar|char_fdel|char_bdel|char_swap
1524 <dt class=
"hdlist1">
1525 /iline fword|bword|word_bdel|word_fdel
1527 <dt class=
"hdlist1">
1528 /iline word_upcase|word_downcase|word_capit
1530 <dt class=
"hdlist1">
1531 /iline hist_beginning_search_bwd|hist_beginning_search_fwd
1533 <dt class=
"hdlist1">
1534 /iline hist_prev|hist_next
1536 <dt class=
"hdlist1">
1537 /iline iline_start|iline_end|iline_fdel|iline_bdel
1539 <dt class=
"hdlist1">
1540 /iline iline_accept|iline_accept_down_hist
1542 <dt class=
"hdlist1">
1543 /iline compl_do|compl_cancel
1545 <dt class=
"hdlist1">
1546 /iline send_multiline
1552 <div class=
"dlist"><dl>
1553 <dt class=
"hdlist1">
1558 Move to the next letter
1561 <dt class=
"hdlist1">
1566 Move to the previous letter
1569 <dt class=
"hdlist1">
1574 Delete the letter at cursor position
1577 <dt class=
"hdlist1">
1582 Delete the letter before cursor position
1585 <dt class=
"hdlist1">
1593 <dt class=
"hdlist1">
1598 Move the cursor forward to the end of the current or next word
1601 <dt class=
"hdlist1">
1606 Move the cursor back to the start of the current or previous word
1609 <dt class=
"hdlist1">
1614 Delete the word from cursor position to its start
1617 <dt class=
"hdlist1">
1622 Delete the word from cursor position to its end
1625 <dt class=
"hdlist1">
1626 <em>word_upcase
</em>
1630 Convert the word from cursor position to its end to upper case
1633 <dt class=
"hdlist1">
1634 <em>word_downcase
</em>
1638 Convert the word from cursor position to its end to down case
1641 <dt class=
"hdlist1">
1646 Capitalize the word from cursor position to its end
1649 <dt class=
"hdlist1">
1650 <em>hist_beginning_search_bwd
</em>
1654 Search backward in the history for a line beginning with the current line up to the cursor (this leaves the cursor in its original position)
1657 <dt class=
"hdlist1">
1658 <em>hist_beginning_search_fwd
</em>
1662 Search forward in the history for a line beginning with the current line up to the cursor (this leaves the cursor in its original position)
1665 <dt class=
"hdlist1">
1670 Previous line of input line history
1673 <dt class=
"hdlist1">
1678 Next line of input line history
1681 <dt class=
"hdlist1">
1682 <em>iline_start
</em>
1686 Go to the beginning of the input line
1689 <dt class=
"hdlist1">
1694 Go to the end of the input line
1697 <dt class=
"hdlist1">
1702 Delete from the cursor to the end of line
1705 <dt class=
"hdlist1">
1710 Delete from beginning of the line to the cursor
1713 <dt class=
"hdlist1">
1714 <em>iline_accept
</em>
1721 <dt class=
"hdlist1">
1722 <em>iline_accept_down_hist
</em>
1726 Accept line and put the next history line in the input line
1729 <dt class=
"hdlist1">
1734 Complete current word, in the input line
1737 <dt class=
"hdlist1">
1738 <em>compl_cancel
</em>
1745 <dt class=
"hdlist1">
1746 <em>send_multiline
</em>
1750 Send/terminate a multi-line message
1755 <dt class=
"hdlist1">
1760 Display info on the selected entry (user, agent, group
…).
<br />
1761 For users, resources are displayed with the status, priority and status message (if available) of each resource.
1764 <dt class=
"hdlist1">
1765 /module load|unload [-f] module
1767 <dt class=
"hdlist1">
1770 <dt class=
"hdlist1">
1775 Load, unload or show info on module.
1777 <div class=
"dlist"><dl>
1778 <dt class=
"hdlist1">
1779 <em>load
</em> [-f] module
1783 Loads specified module. If -f flag is specified, most of module loading errors will be ignored.
1786 <dt class=
"hdlist1">
1787 <em>unload
</em> [-f] module
1791 Unloads specified module. Note: The force flag will not remove any dependent on this modules!
1794 <dt class=
"hdlist1">
1795 <em>info
</em> module
1799 Shows available information about this module.
1802 <dt class=
"hdlist1">
1807 Lists modules in a format: [modulename] [reference count] ([Manually/Automatically loaded]) [any extra info, like version or dependencies]
1812 <dt class=
"hdlist1">
1817 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.
<br />
1818 Tip: if the chatmode is enabled, you can use
"/roster alternate" to jump to the moved buddy.
1821 <dt class=
"hdlist1">
1822 /msay begin|verbatim|send|send_to|toggle|toggle_verbatim|abort
1826 Send a multi-line message. To write a single message with several lines, the
<em>multi-line mode
</em> should be used.
<br />
1827 In multi-line mode, each line (except command lines) typed in the input line will be added to the multi-line message. Once the message is finished, it can be sent to the current selected buddy with the
"/msay send" command.
<br />
1828 The
<em>begin
</em> subcommand enables multi-line mode. Note that it allows a message subject to be specified.
<br />
1829 The
<em>verbatim
</em> multi-line mode disables commands, so that it is possible to enter lines starting with a slash. Only the
"/msay" command (with send or abort parameters) can be used to exit verbatim mode.
<br />
1830 The
<em>toggle
</em> subcommand can be bound to a key to use the multi-line mode quickly (for example,
"bind M13 = msay toggle" to switch using the Meta-Enter combination).
1832 <div class=
"dlist"><dl>
1833 <dt class=
"hdlist1">
1834 <em>begin
</em> [subject]
1838 Enter multi-line mode
1841 <dt class=
"hdlist1">
1846 Enter verbatim multi-line mode
1849 <dt class=
"hdlist1">
1850 <em>send
</em> [-n|-h]
1854 Send the current multi-line message to the currently selected buddy
1857 <dt class=
"hdlist1">
1858 <em>send_to
</em> [-n|-h] jid
1862 Send the current multi-line message to
"jid"
1865 <dt class=
"hdlist1">
1866 <em>toggle
</em>|
<em>toggle_verbatim
</em>
1870 Switch to/from multi-line mode (begin/send)
1873 <dt class=
"hdlist1">
1878 Leave multi-line mode without sending the message
1880 <div class=
"literalblock">
1881 <div class=
"content">
1882 <pre><tt>The -n or -h flags turn the message to
"normal" or
"headline" accordingly, as opposed to default
"chat" message.
</tt></pre>
1887 <dt class=
"hdlist1">
1890 <dt class=
"hdlist1">
1891 /otr start|stop|info [jid]
1893 <dt class=
"hdlist1">
1894 /otr fingerprint [jid [fpr]]
1896 <dt class=
"hdlist1">
1897 /otr smpq|smpr [jid] secret
1899 <dt class=
"hdlist1">
1904 You can use the shortcut-jid
"." for the currently selected contact.
1906 <div class=
"dlist"><dl>
1907 <dt class=
"hdlist1">
1912 Print the fingerprint of your private key to the Status Buffer
1915 <dt class=
"hdlist1">
1916 <em>start
</em> [jid]
1920 Open an OTR channel to the specified jid (or the currently selected contact)
1923 <dt class=
"hdlist1">
1928 Close the OTR channel to the specified jid (or the currently selected contact)
1931 <dt class=
"hdlist1">
1936 Show current OTR status for the specified jid (or the currently selected contact)
1939 <dt class=
"hdlist1">
1940 <em>fingerprint
</em> [jid [fpr]]
1944 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.
1947 <dt class=
"hdlist1">
1948 <em>smpq
</em> [jid] secret
1952 Initiate the Socialist Millionaires Protocol with the secret and the buddy
1955 <dt class=
"hdlist1">
1956 <em>smpr
</em> [jid] secret
1960 Respond to the Initiation of the jid with the secret
1963 <dt class=
"hdlist1">
1968 Abort the running Socialist Millionaires Protocol
1973 <dt class=
"hdlist1">
1976 <dt class=
"hdlist1">
1977 /otrpolicy (default|jid) (plain|manual|opportunistic|always)
1981 You can use the shortcut-jid
"." for the currently selected contact.
1983 <div class=
"dlist"><dl>
1984 <dt class=
"hdlist1">
1989 Prints all OTR policies to the status buffer
1992 <dt class=
"hdlist1">
1993 (
<em>default
</em>|
<em>jid
</em>) (plain|manual|opportunistic|always)
1997 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.
2002 <dt class=
"hdlist1">
2003 /pgp disable|enable|force|info [jid]
2005 <dt class=
"hdlist1">
2006 /pgp setkey [jid [key]]
2010 This command manipulates PGP settings for the specified jid (by default the currently selected contact).
<br />
2011 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.
2013 <div class=
"dlist"><dl>
2014 <dt class=
"hdlist1">
2015 <em>disable
</em> [jid]
2019 Disable PGP encryption for jid (or the currently selected contact)
2022 <dt class=
"hdlist1">
2023 <em>enable
</em> [jid]
2027 Enable PGP encryption for jid (or the currently selected contact)
2030 <dt class=
"hdlist1">
2031 <em style=
"color:+|-;">force
</em> [jid]
2035 Enforce PGP encryption, even for offline messages, and always assume the recipient has PGP support. If a message can
’t be encrypted (missing key or key id), the messages won
’t be sent at all. This option is ignored when PGP is disabled.
2038 <dt class=
"hdlist1">
2043 Show current PGP settings for the contact
2046 <dt class=
"hdlist1">
2047 <em>setkey
</em> [jid [key]]
2051 Set the PGP key to be used to encrypt message for this contact. If no key is provided, the current key is erased. You can use the shortcut-jid
"." for the currently selected contact.
2056 <dt class=
"hdlist1">
2061 This command closes all connections and quit mcabber.
2064 <dt class=
"hdlist1">
2069 Send
"string" (raw XML format) to the Jabber server.
<br />
2070 No check is done on the string provided.
<br />
2072 Use this only if you know what you are doing, or you could terminate the connection.
<br />
2073 Example:
"/rawxml send <presence><show>away</show></presence>"
2076 <dt class=
"hdlist1">
2081 Rename the current buddy or group to the given
"name". If
"name" is -, the name is removed from the roster (and mcabber will display the JID or username).
2084 <dt class=
"hdlist1">
2085 /request last|ping|time|vcard|version [jid]
2089 Send a
"IQ" query to the current buddy, or to the specified Jabber user. If the resource is not provided with the jid, mcabber will send the query to all known resources for this user.
2091 <div class=
"dlist"><dl>
2092 <dt class=
"hdlist1">
2097 Request
"last" information (usually idle time)
2100 <dt class=
"hdlist1">
2105 Send an XMPP Ping request. Note that you should use the full JID since a ping sent to a bare JID will be handled by the server.
2108 <dt class=
"hdlist1">
2113 Request time from the buddy
2116 <dt class=
"hdlist1">
2121 Request VCard from the buddy
2124 <dt class=
"hdlist1">
2129 Request version from the buddy
2134 <dt class=
"hdlist1">
2135 /room join|leave|names|nick|remove|topic|unlock|destroy
2137 <dt class=
"hdlist1">
2138 /room privmsg|invite|whois|kick|ban|unban|role|affil
2140 <dt class=
"hdlist1">
2141 /room setopt print_status|auto_whois [value]
2143 <dt class=
"hdlist1">
2144 /room bookmark [add|del] [-autojoin|+autojoin] [-|nick]
2148 The
<em>room
</em> command handles Multi-User Chat room actions.
2150 <div class=
"dlist"><dl>
2151 <dt class=
"hdlist1">
2152 <em>join
</em> [room [nick [pass]]]
2156 Join
"room", using
"nick" as nickname. If no nickname is provided (or if it is an empty string), 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. A password can be provided to enter protected rooms. If your nickname contains space characters, use quotes.
2159 <dt class=
"hdlist1">
2160 <em>leave
</em> [message]
2164 Leave the current room
2167 <dt class=
"hdlist1">
2168 <em>names
</em> [--detail|--short|--quiet|--compact]
2172 Display members of the current room
2175 <dt class=
"hdlist1">
2176 <em>nick
</em> newnick
2180 Change your nickname in the current room
2183 <dt class=
"hdlist1">
2184 <em>privmsg
</em> nick msg
2188 Send private message
"msg" to
"nick"
2191 <dt class=
"hdlist1">
2196 Remove the current room from the roster (you must have left this room before)
2199 <dt class=
"hdlist1">
2200 <em>topic
</em> -|newtopic
2204 Set topic for current room
2207 <dt class=
"hdlist1">
2212 Unlock current room (if you are the owner)
2215 <dt class=
"hdlist1">
2216 <em>destroy
</em> [reason]
2220 Destroy the current room (use with care!)
2223 <dt class=
"hdlist1">
2228 Display MUC information about
"nick"
2231 <dt class=
"hdlist1">
2232 <em>ban
</em> jid [reason]
2236 Ban jid from the current room
2239 <dt class=
"hdlist1">
2244 Unban jid from the current room
2247 <dt class=
"hdlist1">
2248 <em>invite
</em> jid [reason]
2252 Invite jid to the current room
2255 <dt class=
"hdlist1">
2256 <em>kick
</em> nick [reason]
2260 Kick
"nick" from the current room
2263 <dt class=
"hdlist1">
2264 <em>role
</em> jid role [reason]
2268 Change jid
’s role (role can be
"none",
"visitor",
"participant",
"moderator")
2271 <dt class=
"hdlist1">
2272 <em>affil
</em> jid affil [reason]
2276 Change jid
’s affiliation (affil can be
"none",
"member",
"admin",
"owner")
2279 <dt class=
"hdlist1">
2280 <em>setopt
</em> print_status|auto_whois [value]
2284 Change settings for the current room For print_status, the possible values are
"default",
"none",
"in_and_out",
"all". For auto_whois, the possible values are
"default",
"off",
"on". When the value is
"default", the options muc_print_status / muc_auto_whois is used.
2287 <dt class=
"hdlist1">
2288 <em>bookmark
</em> [add|del] [-autojoin|+autojoin] [-|nick]
2292 Add, remove or update a bookmark (default is add). If autojoin is set, mcabber will automatically join the MUC room when it connects to the server. To see the list of bookmarks, use /room bookmark in the status buffer.
2297 <dt class=
"hdlist1">
2298 /roster bottom|top|up|down|group_prev|group_next
2300 <dt class=
"hdlist1">
2301 /roster alternate|unread_first|unread_next
2303 <dt class=
"hdlist1">
2306 <dt class=
"hdlist1">
2307 /roster display|hide_offline|show_offline|toggle_offline
2309 <dt class=
"hdlist1">
2310 /roster item_lock|item_unlock|item_toggle_lock
2312 <dt class=
"hdlist1">
2313 /roster hide|show|toggle
2315 <dt class=
"hdlist1">
2316 /roster note [-|text]
2320 The
<em>roster
</em> command manipulates the roster/buddylist.
<br />
2321 Here are the available parameters:
2323 <div class=
"dlist"><dl>
2324 <dt class=
"hdlist1">
2329 Jump to the bottom of the roster
2332 <dt class=
"hdlist1">
2337 Jump to the top of the roster
2340 <dt class=
"hdlist1">
2345 Move up [n lines] in the roster
2348 <dt class=
"hdlist1">
2353 Move down [n lines] in the roster
2356 <dt class=
"hdlist1">
2361 Jump to the previous group in the roster
2364 <dt class=
"hdlist1">
2369 Jump to the next group in the roster
2372 <dt class=
"hdlist1">
2377 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_next" (Ctrl-q).
2380 <dt class=
"hdlist1">
2381 <em>unread_first
</em>
2385 Jump to the first unread message
2388 <dt class=
"hdlist1">
2389 <em>unread_next
</em>
2393 Jump to the next unread message
2396 <dt class=
"hdlist1">
2401 Search for a buddy with a name or jid containing
"bud" (only in the displayed buddylist)
2404 <dt class=
"hdlist1">
2405 <em>display
</em> [mask]
2409 See or update the roster filter. The mask should contain the shortcut letters of the status you want to see ([o]nline, [f]ree_for_chat, [d]o_not_disturb, [n]ot_available, [a]way, [_]offline). For example
"ofdna" to display only connected buddies.
2412 <dt class=
"hdlist1">
2413 <em>hide_offline
</em>
2417 Hide offline buddies (same as /roster display ofdna)
2420 <dt class=
"hdlist1">
2421 <em>show_offline
</em>
2425 Show offline buddies (same as /roster display ofdna_)
2428 <dt class=
"hdlist1">
2429 <em>toggle_offline
</em>
2433 Toggle display of offline buddies
2436 <dt class=
"hdlist1">
2437 <em>item_lock
</em> [jid]
2441 Lock the roster item so it remains visible regardless of its status
2444 <dt class=
"hdlist1">
2445 <em>item_unlock
</em> [jid]
2449 Undo the effects of item_lock
2452 <dt class=
"hdlist1">
2453 <em>item_toggle_lock
</em> [jid]
2457 Invert the current lock flag
2460 <dt class=
"hdlist1">
2465 Hide roster (full-width chat window)
2468 <dt class=
"hdlist1">
2476 <dt class=
"hdlist1">
2481 Toggle roster visibility
2484 <dt class=
"hdlist1">
2485 <em>note
</em> [-|text]
2489 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.
2494 <dt class=
"hdlist1">
2495 /say [-n|-h|--] text
2499 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.
<br />
2500 The
"-n" flag turns the message to
"normal" type,
"-h" to
"headline".
"--" can be used to send chat message beginning with -n or -h.
2503 <dt class=
"hdlist1">
2504 /say_to [-n|-h] [-q] [-f file] jid text
2508 Send the
"text" message to the specified jid.
<br />
2509 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.
<br />
2510 The
"-n" flag turns the message to
"normal" type,
"-h" to
"headline".
"--" can be used to send chat messages beginning with -n or -h.
<br />
2511 When
"-q" is used, the message will be sent in the background and will not change the current active window.
<br />
2512 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).
2515 <dt class=
"hdlist1">
2520 Refresh the mcabber screen.
2523 <dt class=
"hdlist1">
2524 /set option [= value]
2528 Display or set an option value.
2531 <dt class=
"hdlist1">
2536 Read configuration files, that match glob pattern (sorted in alphabetical order).
2539 <dt class=
"hdlist1">
2540 /status [online|avail|invisible|free|dnd|notavail|away [-|statusmessage]]
2542 <dt class=
"hdlist1">
2543 /status message -|statusmessage
2547 Show or set the current status.
<br />
2548 If no status is specified, display the current status.
<br />
2549 If a status message is specified, it will overrride the message* variables (these variables can be set in the configuration file).
<br />
2550 If no relevant message* variable is set and no status message provided, the current status message is kept.
<br />
2551 If StatusMessage is
"-", the current status message is cleared.
<br />
2552 With the
"/status message" command, mcabber will update the message while preserving the status.
2555 <dt class=
"hdlist1">
2556 /status_to jid online|avail|invisible|free|dnd|notavail|away [statusmessage]
2558 <dt class=
"hdlist1">
2559 /status_to jid message statusmessage
2563 Send the requested status to the specified Jabber user.
<br />
2564 If the specified jid is
".", the current buddy is used.
<br />
2565 Note: this status will be overridden by subsequent
"/status" commands. If you are using the auto-away feature, the status will overridden too.
<br />
2566 Note: The jid can include a resource (i.e. user@server/resource).
2569 <dt class=
"hdlist1">
2574 Display current version of mcabber.
2579 <h2 id=
"_configuration_file">CONFIGURATION FILE
</h2>
2580 <div class=
"sectionbody">
2581 <div class=
"paragraph"><p>See the provided sample configuration file, which should be self-documenting.
</p></div>
2583 <h2 id=
"_files">FILES
</h2>
2584 <div class=
"sectionbody">
2585 <div class=
"paragraph"><p>The following files can be used by
<tt>mcabber(
1)
</tt>:
</p></div>
2586 <div class=
"literalblock">
2587 <div class=
"content">
2588 <pre><tt>$HOME/.mcabber/mcabberrc Default configuration file
2589 $HOME/.mcabberrc Configuration file used if no other has been found
2590 $HOME/.mcabber/histo/ Default directory for storing chat history files, if enabled
2591 /usr/share/mcabber/help/ Default directory for online help files
2592 /usr/lib/mcabber/ Default directory for modules
</tt></pre>
2595 <h2 id=
"_bugs">BUGS
</h2>
2596 <div class=
"sectionbody">
2597 <div class=
"paragraph"><p>Certainly. Please tell me if you find one! :-)
<br />
2598 Please visit our website to find out about the MUC room and the bug tracker.
</p></div>
2600 <h2 id=
"_author">AUTHOR
</h2>
2601 <div class=
"sectionbody">
2602 <div class=
"paragraph"><p>Written by
<a href=
"mailto:mikael@lilotux.net">Mikael BERTHE
</a> and others
2603 (see AUTHORS file).
<br /></p></div>
2605 <h2 id=
"_resources">RESOURCES
</h2>
2606 <div class=
"sectionbody">
2607 <div class=
"paragraph"><p><a href=
"http://mcabber.com/">Main web site
</a></p></div>
2609 <h2 id=
"_copying">COPYING
</h2>
2610 <div class=
"sectionbody">
2611 <div class=
"paragraph"><p>Copyright (C)
2005-
2010 Mikael Berthe and others.
<br /></p></div>
2612 <div class=
"paragraph"><p>Free use of this software is granted under the terms of the GNU General Public
2613 License (GPL).
</p></div>
2616 <div id=
"footnotes"><hr /></div>
2618 <div id=
"footer-text">
2619 Version
0.10.0-dev
<br />
2620 Last updated
2010-
03-
13 17:
43:
30 CEST