Mercurial > hg
annotate mcabber/doc/mcabber.1.html @ 1977:1d8f9135e000
Use smarter message flag in the main status line
The attention sign (!) is used when a personal message is unread,
or if we're highlighted in a MUC room.
author | Mikael Berthe <mikael@lilotux.net> |
---|---|
date | Sat, 26 Mar 2011 13:37:33 +0100 |
parents | 9fe1c0a54e73 |
children | 3f4c97805218 |
rev | line source |
---|---|
1759 | 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"> | |
229 | 4 <head> |
1759 | 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"> | |
9 /* Debug borders */ | |
10 p, li, dt, dd, div, pre, h1, h2, h3, h4, h5, h6 { | |
11 /* | |
12 border: 1px solid red; | |
13 */ | |
14 } | |
15 | |
16 body { | |
17 margin: 1em 5% 1em 5%; | |
18 } | |
19 | |
20 a { | |
21 color: blue; | |
22 text-decoration: underline; | |
23 } | |
24 a:visited { | |
25 color: fuchsia; | |
26 } | |
27 | |
28 em { | |
29 font-style: italic; | |
30 color: navy; | |
31 } | |
32 | |
33 strong { | |
34 font-weight: bold; | |
35 color: #083194; | |
36 } | |
37 | |
38 tt { | |
39 color: navy; | |
40 } | |
41 | |
42 h1, h2, h3, h4, h5, h6 { | |
43 color: #527bbd; | |
44 font-family: sans-serif; | |
45 margin-top: 1.2em; | |
46 margin-bottom: 0.5em; | |
47 line-height: 1.3; | |
48 } | |
49 | |
50 h1, h2, h3 { | |
51 border-bottom: 2px solid silver; | |
52 } | |
53 h2 { | |
54 padding-top: 0.5em; | |
55 } | |
56 h3 { | |
57 float: left; | |
58 } | |
59 h3 + * { | |
60 clear: left; | |
61 } | |
62 | |
63 div.sectionbody { | |
64 font-family: serif; | |
65 margin-left: 0; | |
66 } | |
67 | |
68 hr { | |
69 border: 1px solid silver; | |
70 } | |
71 | |
72 p { | |
73 margin-top: 0.5em; | |
74 margin-bottom: 0.5em; | |
75 } | |
76 | |
77 ul, ol, li > p { | |
78 margin-top: 0; | |
79 } | |
80 | |
81 pre { | |
82 padding: 0; | |
83 margin: 0; | |
84 } | |
85 | |
86 span#author { | |
87 color: #527bbd; | |
88 font-family: sans-serif; | |
89 font-weight: bold; | |
90 font-size: 1.1em; | |
91 } | |
92 span#email { | |
93 } | |
94 span#revnumber, span#revdate, span#revremark { | |
95 font-family: sans-serif; | |
96 } | |
97 | |
98 div#footer { | |
99 font-family: sans-serif; | |
100 font-size: small; | |
101 border-top: 2px solid silver; | |
102 padding-top: 0.5em; | |
103 margin-top: 4.0em; | |
104 } | |
105 div#footer-text { | |
106 float: left; | |
107 padding-bottom: 0.5em; | |
108 } | |
109 div#footer-badges { | |
110 float: right; | |
111 padding-bottom: 0.5em; | |
112 } | |
113 | |
114 div#preamble { | |
115 margin-top: 1.5em; | |
116 margin-bottom: 1.5em; | |
117 } | |
118 div.tableblock, div.imageblock, div.exampleblock, div.verseblock, | |
119 div.quoteblock, div.literalblock, div.listingblock, div.sidebarblock, | |
120 div.admonitionblock { | |
121 margin-top: 1.0em; | |
122 margin-bottom: 1.5em; | |
123 } | |
124 div.admonitionblock { | |
125 margin-top: 2.0em; | |
126 margin-bottom: 2.0em; | |
127 margin-right: 10%; | |
128 color: #606060; | |
129 } | |
130 | |
131 div.content { /* Block element content. */ | |
132 padding: 0; | |
133 } | |
134 | |
135 /* Block element titles. */ | |
136 div.title, caption.title { | |
137 color: #527bbd; | |
138 font-family: sans-serif; | |
139 font-weight: bold; | |
140 text-align: left; | |
141 margin-top: 1.0em; | |
142 margin-bottom: 0.5em; | |
143 } | |
144 div.title + * { | |
145 margin-top: 0; | |
146 } | |
147 | |
148 td div.title:first-child { | |
149 margin-top: 0.0em; | |
150 } | |
151 div.content div.title:first-child { | |
152 margin-top: 0.0em; | |
153 } | |
154 div.content + div.title { | |
155 margin-top: 0.0em; | |
156 } | |
157 | |
158 div.sidebarblock > div.content { | |
159 background: #ffffee; | |
160 border: 1px solid silver; | |
161 padding: 0.5em; | |
162 } | |
163 | |
164 div.listingblock > div.content { | |
165 border: 1px solid silver; | |
166 background: #f4f4f4; | |
167 padding: 0.5em; | |
168 } | |
169 | |
170 div.quoteblock, div.verseblock { | |
171 padding-left: 1.0em; | |
172 margin-left: 1.0em; | |
173 margin-right: 10%; | |
174 border-left: 5px solid #dddddd; | |
175 color: #777777; | |
176 } | |
177 | |
178 div.quoteblock > div.attribution { | |
179 padding-top: 0.5em; | |
180 text-align: right; | |
181 } | |
182 | |
183 div.verseblock > div.content { | |
184 white-space: pre; | |
185 } | |
186 div.verseblock > div.attribution { | |
187 padding-top: 0.75em; | |
188 text-align: left; | |
189 } | |
190 /* DEPRECATED: Pre version 8.2.7 verse style literal block. */ | |
191 div.verseblock + div.attribution { | |
192 text-align: left; | |
193 } | |
194 | |
195 div.admonitionblock .icon { | |
196 vertical-align: top; | |
197 font-size: 1.1em; | |
198 font-weight: bold; | |
199 text-decoration: underline; | |
200 color: #527bbd; | |
201 padding-right: 0.5em; | |
202 } | |
203 div.admonitionblock td.content { | |
204 padding-left: 0.5em; | |
205 border-left: 3px solid #dddddd; | |
206 } | |
207 | |
208 div.exampleblock > div.content { | |
209 border-left: 3px solid #dddddd; | |
210 padding-left: 0.5em; | |
211 } | |
212 | |
213 div.imageblock div.content { padding-left: 0; } | |
214 span.image img { border-style: none; } | |
215 a.image:visited { color: white; } | |
216 | |
217 dl { | |
218 margin-top: 0.8em; | |
219 margin-bottom: 0.8em; | |
220 } | |
221 dt { | |
222 margin-top: 0.5em; | |
223 margin-bottom: 0; | |
224 font-style: normal; | |
225 color: navy; | |
226 } | |
227 dd > *:first-child { | |
228 margin-top: 0.1em; | |
229 } | |
230 | |
231 ul, ol { | |
232 list-style-position: outside; | |
233 } | |
234 ol.arabic { | |
235 list-style-type: decimal; | |
236 } | |
237 ol.loweralpha { | |
238 list-style-type: lower-alpha; | |
239 } | |
240 ol.upperalpha { | |
241 list-style-type: upper-alpha; | |
242 } | |
243 ol.lowerroman { | |
244 list-style-type: lower-roman; | |
245 } | |
246 ol.upperroman { | |
247 list-style-type: upper-roman; | |
248 } | |
249 | |
250 div.compact ul, div.compact ol, | |
251 div.compact p, div.compact p, | |
252 div.compact div, div.compact div { | |
253 margin-top: 0.1em; | |
254 margin-bottom: 0.1em; | |
255 } | |
256 | |
257 div.tableblock > table { | |
258 border: 3px solid #527bbd; | |
259 } | |
260 thead, p.table.header { | |
261 font-family: sans-serif; | |
262 font-weight: bold; | |
263 } | |
264 tfoot { | |
265 font-weight: bold; | |
266 } | |
267 td > div.verse { | |
268 white-space: pre; | |
269 } | |
270 p.table { | |
271 margin-top: 0; | |
272 } | |
273 /* Because the table frame attribute is overriden by CSS in most browsers. */ | |
274 div.tableblock > table[frame="void"] { | |
275 border-style: none; | |
276 } | |
277 div.tableblock > table[frame="hsides"] { | |
278 border-left-style: none; | |
279 border-right-style: none; | |
280 } | |
281 div.tableblock > table[frame="vsides"] { | |
282 border-top-style: none; | |
283 border-bottom-style: none; | |
284 } | |
285 | |
286 | |
287 div.hdlist { | |
288 margin-top: 0.8em; | |
289 margin-bottom: 0.8em; | |
290 } | |
291 div.hdlist tr { | |
292 padding-bottom: 15px; | |
293 } | |
294 dt.hdlist1.strong, td.hdlist1.strong { | |
295 font-weight: bold; | |
296 } | |
297 td.hdlist1 { | |
298 vertical-align: top; | |
299 font-style: normal; | |
300 padding-right: 0.8em; | |
301 color: navy; | |
302 } | |
303 td.hdlist2 { | |
304 vertical-align: top; | |
305 } | |
306 div.hdlist.compact tr { | |
307 margin: 0; | |
308 padding-bottom: 0; | |
309 } | |
310 | |
311 .comment { | |
312 background: yellow; | |
313 } | |
314 | |
315 .footnote, .footnoteref { | |
316 font-size: 0.8em; | |
317 } | |
318 | |
319 span.footnote, span.footnoteref { | |
320 vertical-align: super; | |
321 } | |
322 | |
323 #footnotes { | |
324 margin: 20px 0 20px 0; | |
325 padding: 7px 0 0 0; | |
326 } | |
327 | |
328 #footnotes div.footnote { | |
329 margin: 0 0 5px 0; | |
330 } | |
331 | |
332 #footnotes hr { | |
333 border: none; | |
334 border-top: 1px solid silver; | |
335 height: 1px; | |
336 text-align: left; | |
337 margin-left: 0; | |
338 width: 20%; | |
339 min-width: 100px; | |
340 } | |
341 | |
342 | |
343 @media print { | |
344 div#footer-badges { display: none; } | |
345 } | |
346 | |
347 div#toc { | |
348 margin-bottom: 2.5em; | |
349 } | |
350 | |
351 div#toctitle { | |
352 color: #527bbd; | |
353 font-family: sans-serif; | |
354 font-size: 1.1em; | |
355 font-weight: bold; | |
356 margin-top: 1.0em; | |
357 margin-bottom: 0.1em; | |
358 } | |
359 | |
360 div.toclevel1, div.toclevel2, div.toclevel3, div.toclevel4 { | |
361 margin-top: 0; | |
362 margin-bottom: 0; | |
363 } | |
364 div.toclevel2 { | |
365 margin-left: 2em; | |
366 font-size: 0.9em; | |
367 } | |
368 div.toclevel3 { | |
369 margin-left: 4em; | |
370 font-size: 0.9em; | |
371 } | |
372 div.toclevel4 { | |
373 margin-left: 6em; | |
374 font-size: 0.9em; | |
375 } | |
376 /* Overrides for manpage documents */ | |
377 h1 { | |
378 padding-top: 0.5em; | |
379 padding-bottom: 0.5em; | |
380 border-top: 2px solid silver; | |
381 border-bottom: 2px solid silver; | |
382 } | |
383 h2 { | |
384 border-style: none; | |
385 } | |
386 div.sectionbody { | |
387 margin-left: 5%; | |
388 } | |
389 | |
390 @media print { | |
391 div#toc { display: none; } | |
392 } | |
393 | |
394 /* Workarounds for IE6's broken and incomplete CSS2. */ | |
395 | |
396 div.sidebar-content { | |
397 background: #ffffee; | |
398 border: 1px solid silver; | |
399 padding: 0.5em; | |
400 } | |
401 div.sidebar-title, div.image-title { | |
402 color: #527bbd; | |
403 font-family: sans-serif; | |
404 font-weight: bold; | |
405 margin-top: 0.0em; | |
406 margin-bottom: 0.5em; | |
407 } | |
408 | |
409 div.listingblock div.content { | |
410 border: 1px solid silver; | |
411 background: #f4f4f4; | |
412 padding: 0.5em; | |
413 } | |
414 | |
415 div.quoteblock-attribution { | |
416 padding-top: 0.5em; | |
417 text-align: right; | |
418 } | |
419 | |
420 div.verseblock-content { | |
421 white-space: pre; | |
422 } | |
423 div.verseblock-attribution { | |
424 padding-top: 0.75em; | |
425 text-align: left; | |
426 } | |
427 | |
428 div.exampleblock-content { | |
429 border-left: 3px solid #dddddd; | |
430 padding-left: 0.5em; | |
431 } | |
432 | |
433 /* IE6 sets dynamically generated links as visited. */ | |
434 div#toc a:visited { color: blue; } | |
435 </style> | |
436 <script type="text/javascript"> | |
437 /*<![CDATA[*/ | |
438 window.onload = function(){asciidoc.footnotes();} | |
439 var asciidoc = { // Namespace. | |
440 | |
441 ///////////////////////////////////////////////////////////////////// | |
442 // Table Of Contents generator | |
443 ///////////////////////////////////////////////////////////////////// | |
444 | |
445 /* Author: Mihai Bazon, September 2002 | |
446 * http://students.infoiasi.ro/~mishoo | |
447 * | |
448 * Table Of Content generator | |
449 * Version: 0.4 | |
450 * | |
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. | |
453 */ | |
454 | |
455 /* modified by Troy D. Hanson, September 2006. License: GPL */ | |
456 /* modified by Stuart Rackham, 2006, 2009. License: GPL */ | |
457 | |
458 // toclevels = 1..4. | |
459 toc: function (toclevels) { | |
460 | |
461 function getText(el) { | |
462 var text = ""; | |
463 for (var i = el.firstChild; i != null; i = i.nextSibling) { | |
464 if (i.nodeType == 3 /* Node.TEXT_NODE */) // IE doesn't speak constants. | |
465 text += i.data; | |
466 else if (i.firstChild != null) | |
467 text += getText(i); | |
468 } | |
469 return text; | |
470 } | |
471 | |
472 function TocEntry(el, text, toclevel) { | |
473 this.element = el; | |
474 this.text = text; | |
475 this.toclevel = toclevel; | |
476 } | |
477 | |
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 | |
483 // browsers). | |
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); | |
490 } | |
491 iterate(i); | |
492 } | |
493 } | |
494 } | |
495 iterate(el); | |
496 return result; | |
497 } | |
498 | |
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"); | |
509 div.appendChild(a); | |
510 div.className = "toclevel" + entry.toclevel; | |
511 toc.appendChild(div); | |
512 } | |
513 if (entries.length == 0) | |
514 toc.parentNode.removeChild(toc); | |
515 }, | |
516 | |
517 | |
518 ///////////////////////////////////////////////////////////////////// | |
519 // Footnotes generator | |
520 ///////////////////////////////////////////////////////////////////// | |
521 | |
522 /* Based on footnote generation code from: | |
523 * http://www.brandspankingnew.net/archive/2005/07/format_footnote.html | |
524 */ | |
525 | |
526 footnotes: function () { | |
527 var cont = document.getElementById("content"); | |
528 var noteholder = document.getElementById("footnotes"); | |
529 var spans = cont.getElementsByTagName("span"); | |
530 var refs = {}; | |
531 var n = 0; | |
532 for (i=0; i<spans.length; i++) { | |
533 if (spans[i].className == "footnote") { | |
534 n++; | |
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>"; | |
542 spans[i].innerHTML = | |
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; | |
547 } | |
548 } | |
549 if (n == 0) | |
550 noteholder.parentNode.removeChild(noteholder); | |
551 else { | |
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. | |
557 n = refs[href]; | |
558 spans[i].innerHTML = | |
559 "[<a href='#_footnote_" + n + | |
560 "' title='View footnote' class='footnote'>" + n + "</a>]"; | |
561 } | |
562 } | |
563 } | |
564 } | |
565 | |
566 } | |
567 /*]]>*/ | |
568 </script> | |
229 | 569 </head> |
570 <body> | |
1759 | 571 <div id="header"> |
572 <h1> | |
573 MCABBER(1) Manual Page | |
574 </h1> | |
229 | 575 <h2>NAME</h2> |
1759 | 576 <div class="sectionbody"> |
229 | 577 <p>mcabber - |
1759 | 578 a simple Jabber (XMPP) console client |
229 | 579 </p> |
1759 | 580 </div> |
581 </div> | |
582 <div id="content"> | |
583 <h2 id="_synopsis">SYNOPSIS</h2> | |
584 <div class="sectionbody"> | |
585 <div class="paragraph"><p><em>mcabber</em> [ -h | -V | -f configfile ]</p></div> | |
229 | 586 </div> |
1759 | 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 /> | |
229 | 590 For now it needs a configuration file to start, so please copy the sample |
1759 | 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> | |
229 | 596 <li> |
597 <p> | |
1759 | 598 <em>SASL/SSL/TLS support</em>. |
229 | 599 </p> |
600 </li> | |
601 <li> | |
602 <p> | |
1759 | 603 <em>MUC support</em> (Multi-User Chat). |
467 | 604 </p> |
605 </li> | |
606 <li> | |
607 <p> | |
1759 | 608 <em>PGP, OTR support</em> |
1096 | 609 </p> |
610 </li> | |
611 <li> | |
612 <p> | |
1759 | 613 <em>Chat States</em> support (typing notifications) |
1096 | 614 </p> |
615 </li> | |
616 <li> | |
617 <p> | |
1759 | 618 <em>History logging:</em> If enabled (see the CONFIGURATION FILE section), |
619 <tt>mcabber</tt> can save discussions to text history log files. | |
229 | 620 </p> |
621 </li> | |
622 <li> | |
623 <p> | |
1759 | 624 <em>Commands completion:</em> If possible, <tt>mcabber</tt> will try to complete your |
229 | 625 command line if you hit the Tab key. |
626 </p> | |
627 </li> | |
628 <li> | |
629 <p> | |
1759 | 630 <em>Input line history:</em> Any message or command entered is in the input line |
618 | 631 history and can be reused easily. |
632 </p> | |
633 </li> | |
634 <li> | |
635 <p> | |
1759 | 636 <em>External actions:</em> Some events (like receiving a message) can trigger an |
854 | 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 | |
432 | 639 <tt>mcabber</tt> source code, in the contrib directory. |
229 | 640 </p> |
641 </li> | |
1759 | 642 <li> |
643 <p> | |
644 <em>Modules:</em> <tt>mcabber</tt> can load modules (a.k.a. plugins) at runtime that | |
645 extend its features. | |
646 </p> | |
647 </li> | |
648 </ul></div> | |
649 </div> | |
650 <h2 id="_options">OPTIONS</h2> | |
651 <div class="sectionbody"> | |
652 <div class="dlist"><dl> | |
653 <dt class="hdlist1"> | |
654 -h | |
655 </dt> | |
229 | 656 <dd> |
1759 | 657 <p> |
229 | 658 Quick help usage message |
1759 | 659 </p> |
229 | 660 </dd> |
1759 | 661 <dt class="hdlist1"> |
662 -V | |
663 </dt> | |
664 <dd> | |
665 <p> | |
666 Displays <tt>mcabber</tt> version and compile-time definitions. | |
667 </p> | |
668 </dd> | |
669 <dt class="hdlist1"> | |
229 | 670 -f configfile |
1759 | 671 </dt> |
229 | 672 <dd> |
1759 | 673 <p> |
674 Use configuration file <em>configfile</em> | |
675 </p> | |
229 | 676 </dd> |
1759 | 677 </dl></div> |
678 </div> | |
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 | |
854 | 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 | |
1759 | 688 buddy.</p></div> |
689 <div class="paragraph"><p>To display buddies chat buffers, you will have to enter <em>chat mode</em>. | |
854 | 690 You can enter chat mode by pressing enter, and leave chat mode with the ESC |
1759 | 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 | |
854 | 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 | |
1759 | 697 the few buddies with whom you are conversing with the <em>/roster alternate</em> |
854 | 698 command described in another section, without having to manually scroll |
1759 | 699 back and forth.</p></div> |
700 </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 | |
618 | 707 jump to the previous/next line from the history beginning with the same string |
1759 | 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 | |
229 | 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 | |
1759 | 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> | |
715 <dt class="hdlist1"> | |
1096 | 716 Esc |
1759 | 717 </dt> |
718 <dd> | |
719 <p> | |
1096 | 720 Disable chat mode |
1759 | 721 </p> |
722 </dd> | |
723 <dt class="hdlist1"> | |
229 | 724 Ctrl-a |
1759 | 725 </dt> |
726 <dd> | |
727 <p> | |
229 | 728 Go to the beginning of the input line |
1759 | 729 </p> |
730 </dd> | |
731 <dt class="hdlist1"> | |
229 | 732 Ctrl-e |
1759 | 733 </dt> |
734 <dd> | |
735 <p> | |
229 | 736 Go to the end of the input line |
1759 | 737 </p> |
738 </dd> | |
739 <dt class="hdlist1"> | |
229 | 740 Ctrl-l |
1759 | 741 </dt> |
742 <dd> | |
743 <p> | |
618 | 744 Force a refresh |
1759 | 745 </p> |
746 </dd> | |
747 <dt class="hdlist1"> | |
618 | 748 Up/Down |
1759 | 749 </dt> |
750 <dd> | |
751 <p> | |
618 | 752 Move in the input line history |
1759 | 753 </p> |
754 </dd> | |
755 <dt class="hdlist1"> | |
229 | 756 PgUp/PgDown |
1759 | 757 </dt> |
758 <dd> | |
759 <p> | |
229 | 760 Move inside the roster (buddylist) |
1759 | 761 </p> |
762 </dd> | |
763 <dt class="hdlist1"> | |
229 | 764 Tab |
1759 | 765 </dt> |
766 <dd> | |
767 <p> | |
229 | 768 Complete current word, in the input line |
1759 | 769 </p> |
770 </dd> | |
771 <dt class="hdlist1"> | |
229 | 772 Ctrl-g |
1759 | 773 </dt> |
774 <dd> | |
775 <p> | |
1096 | 776 Cancel completion |
1759 | 777 </p> |
778 </dd> | |
779 <dt class="hdlist1"> | |
1096 | 780 Ctrl-c |
1759 | 781 </dt> |
782 <dd> | |
783 <p> | |
1096 | 784 Abort multi-line messages and completions |
1759 | 785 </p> |
786 </dd> | |
787 <dt class="hdlist1"> | |
1096 | 788 Ctrl-d |
1759 | 789 </dt> |
790 <dd> | |
791 <p> | |
1096 | 792 Send/terminate a multi-line message |
1759 | 793 </p> |
794 </dd> | |
795 <dt class="hdlist1"> | |
229 | 796 Ctrl-p/Ctrl-n |
1759 | 797 </dt> |
798 <dd> | |
799 <p> | |
229 | 800 Scroll up/down half a screen in the buffer window (chat mode) |
1759 | 801 </p> |
802 </dd> | |
803 <dt class="hdlist1"> | |
775
b4befb3052e5
Update NEWS, ChangeLog and documentation
Mikael Berthe <mikael@lilotux.net>
parents:
710
diff
changeset
|
804 Ctrl-Left |
1759 | 805 </dt> |
806 <dd> | |
807 <p> | |
775
b4befb3052e5
Update NEWS, ChangeLog and documentation
Mikael Berthe <mikael@lilotux.net>
parents:
710
diff
changeset
|
808 Move the cursor back to the start of the current or previous word |
1759 | 809 </p> |
810 </dd> | |
811 <dt class="hdlist1"> | |
775
b4befb3052e5
Update NEWS, ChangeLog and documentation
Mikael Berthe <mikael@lilotux.net>
parents:
710
diff
changeset
|
812 Ctrl-Right |
1759 | 813 </dt> |
814 <dd> | |
815 <p> | |
775
b4befb3052e5
Update NEWS, ChangeLog and documentation
Mikael Berthe <mikael@lilotux.net>
parents:
710
diff
changeset
|
816 Move the cursor forward to the end of the current or next word |
1759 | 817 </p> |
818 </dd> | |
819 <dt class="hdlist1"> | |
229 | 820 Ctrl-u |
1759 | 821 </dt> |
822 <dd> | |
823 <p> | |
229 | 824 Delete from beginning of the line to the cursor |
1759 | 825 </p> |
826 </dd> | |
827 <dt class="hdlist1"> | |
229 | 828 Ctrl-k |
1759 | 829 </dt> |
830 <dd> | |
831 <p> | |
229 | 832 Delete from the cursor to the end of line |
1759 | 833 </p> |
834 </dd> | |
835 <dt class="hdlist1"> | |
229 | 836 Ctrl-w |
1759 | 837 </dt> |
838 <dd> | |
839 <p> | |
229 | 840 Backward kill word |
1759 | 841 </p> |
842 </dd> | |
843 <dt class="hdlist1"> | |
229 | 844 Ctrl-t |
1759 | 845 </dt> |
846 <dd> | |
847 <p> | |
229 | 848 Transpose chars |
1759 | 849 </p> |
850 </dd> | |
851 <dt class="hdlist1"> | |
263 | 852 Ctrl-o |
1759 | 853 </dt> |
854 <dd> | |
855 <p> | |
263 | 856 Accept line and put the next history line in the input line (accept-line-and-down-history) |
1759 | 857 </p> |
858 </dd> | |
859 </dl></div> | |
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> | |
862 </div> | |
863 <h2 id="_mcabber_8217_s_roster">MCABBER’S ROSTER</h2> | |
864 <div class="sectionbody"> | |
1842 | 865 <div class="paragraph"><p>The first listed item on the roster is <em>[status]</em>, which keeps a log of |
854 | 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 | |
1759 | 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> | |
1842 | 870 <div class="paragraph"><p>Group names are displayed above the items that are within them, and are |
1759 | 871 indicated by <em>---</em> to the left of the name.</p></div> |
1842 | 872 <div class="paragraph"><p>For every real Jabber contact, the roster displays four pieces of information: |
873 the buddy’s name or alias, its online status, its authorization status, and | |
874 whether there are unread messages from the buddy waiting for you.</p></div> | |
1759 | 875 <div class="paragraph"><p>The online status is one of the following:</p></div> |
876 <div class="dlist"><dl> | |
877 <dt class="hdlist1"> | |
878 <em>o</em> | |
879 </dt> | |
880 <dd> | |
881 <p> | |
854 | 882 online |
1759 | 883 </p> |
884 </dd> | |
885 <dt class="hdlist1"> | |
886 <em>f</em> | |
887 </dt> | |
888 <dd> | |
889 <p> | |
854 | 890 free for chat |
1759 | 891 </p> |
892 </dd> | |
893 <dt class="hdlist1"> | |
894 <em>a</em> | |
895 </dt> | |
896 <dd> | |
897 <p> | |
854 | 898 away |
1759 | 899 </p> |
900 </dd> | |
901 <dt class="hdlist1"> | |
902 <em>n</em> | |
903 </dt> | |
904 <dd> | |
905 <p> | |
906 not available (labeled <em>extended away</em> in some clients) | |
907 </p> | |
908 </dd> | |
909 <dt class="hdlist1"> | |
910 <em>d</em> | |
911 </dt> | |
912 <dd> | |
913 <p> | |
854 | 914 do not disturb |
1759 | 915 </p> |
916 </dd> | |
917 <dt class="hdlist1"> | |
918 <em>_</em> | |
919 </dt> | |
920 <dd> | |
921 <p> | |
854 | 922 offline (or invisible to you) |
1759 | 923 </p> |
924 </dd> | |
925 <dt class="hdlist1"> | |
926 <em>?</em> | |
927 </dt> | |
928 <dd> | |
929 <p> | |
1842 | 930 unknown, usually meaning you are not authorized to see this buddy’s status |
1759 | 931 </p> |
932 </dd> | |
933 <dt class="hdlist1"> | |
934 <em>x</em> | |
935 </dt> | |
936 <dd> | |
937 <p> | |
854 | 938 a conference room in which you are not participating |
1759 | 939 </p> |
940 </dd> | |
941 <dt class="hdlist1"> | |
942 <em>C</em> | |
943 </dt> | |
944 <dd> | |
945 <p> | |
854 | 946 a conference room in which you are participating |
1759 | 947 </p> |
948 </dd> | |
949 </dl></div> | |
1842 | 950 <div class="paragraph"><p>The authorization status indicates whether a buddy is authorized to receive |
854 | 951 your online status updates, and is displayed by the brackets surrounding the |
1842 | 952 buddy’s online status. Square brackets, like <em>[o]</em>, indicate that this |
953 buddy is authorized to receive your status. Curly braces, like <em>{o}</em>, | |
1759 | 954 indicate that they are not authorized to receive your status.</p></div> |
1842 | 955 <div class="paragraph"><p>When there are unread messages from a buddy which you have not looked at, |
1759 | 956 a hash mark (<em>#</em>) appears in the leftmost section of the roster for that |
1842 | 957 buddy. The hash mark disappears once you view that buddy’s message |
958 buffer. | |
959 When the user attention is requested (or when you receive a message containing | |
960 your nickname in a MUC room), the hash mark is replaced with the <em>attention | |
961 sign</em>, an exclamation mark (<em>!</em>).</p></div> | |
1759 | 962 <div class="paragraph"><p>Examples:</p></div> |
963 <div class="dlist"><dl> | |
964 <dt class="hdlist1"> | |
1842 | 965 ' --- Buds' |
1759 | 966 </dt> |
967 <dd> | |
968 <p> | |
969 This is a group named <em>Buds</em> | |
970 </p> | |
971 </dd> | |
972 <dt class="hdlist1"> | |
973 <em>#[o] John</em> | |
974 </dt> | |
975 <dd> | |
976 <p> | |
854 | 977 John is online, can see your status, and sent you a message that you did not read yet |
1759 | 978 </p> |
979 </dd> | |
980 <dt class="hdlist1"> | |
1842 | 981 <em> {?} Sally</em> |
1759 | 982 </dt> |
983 <dd> | |
984 <p> | |
854 | 985 Neither you nor Sally have authorized each other to see your online status |
1759 | 986 </p> |
987 </dd> | |
988 <dt class="hdlist1"> | |
1842 | 989 <em> {a} Jane</em> |
1759 | 990 </dt> |
991 <dd> | |
992 <p> | |
854 | 993 Jane is away, but she cannot see your online status |
1759 | 994 </p> |
995 </dd> | |
996 <dt class="hdlist1"> | |
997 <em>#[C] x@y.c</em> | |
998 </dt> | |
999 <dd> | |
1000 <p> | |
854 | 1001 You are participating in x@y.c conference room, and there are unread messages |
1759 | 1002 </p> |
1003 </dd> | |
1004 </dl></div> | |
1005 </div> | |
1006 <h2 id="_commands">COMMANDS</h2> | |
1007 <div class="sectionbody"> | |
1008 <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 /> | |
1009 You will find an overview of the <tt>mcabber</tt> commands in this manual.</p></div> | |
1010 </div> | |
1011 <h2 id="_commands_related_to_mcabber">COMMANDS RELATED TO MCABBER</h2> | |
1012 <div class="sectionbody"> | |
1013 <div class="dlist"><dl> | |
1014 <dt class="hdlist1"> | |
1015 /add [jid [nickname]] | |
1016 </dt> | |
1017 <dd> | |
1018 <p> | |
1019 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. | |
1020 </p> | |
1021 <div class="dlist"><dl> | |
1022 <dt class="hdlist1"> | |
1023 [<em>jid</em> [nickname]] | |
1024 </dt> | |
1025 <dd> | |
1026 <p> | |
1027 Add to our roster "jid" as "nickname" | |
1028 </p> | |
1029 <div class="literalblock"> | |
1030 <div class="content"> | |
1031 <pre><tt>Example: "/add somebody@jabber.server.com Somebody"</tt></pre> | |
1032 </div></div> | |
1033 </dd> | |
1034 </dl></div> | |
1035 </dd> | |
1036 <dt class="hdlist1"> | |
870 | 1037 /alias [name [= command line]] |
1759 | 1038 </dt> |
1039 <dd> | |
1040 <p> | |
1041 This command let you to add aliases which can simplify sophisticated commands.<br /> | |
1042 You can manage your aliases by: | |
1043 </p> | |
1044 <div class="dlist"><dl> | |
1045 <dt class="hdlist1"> | |
1046 (without arguments) | |
1047 </dt> | |
1048 <dd> | |
1049 <p> | |
1050 Print list of currently defined aliases | |
1051 </p> | |
1052 </dd> | |
1053 <dt class="hdlist1"> | |
1054 <em>name</em> | |
1055 </dt> | |
1056 <dd> | |
1057 <p> | |
1058 Print the value of alias called "name" | |
1059 </p> | |
1060 </dd> | |
1061 <dt class="hdlist1"> | |
1062 <em>name</em>= | |
1063 </dt> | |
1064 <dd> | |
1065 <p> | |
1066 Unset alias called "name" | |
1067 </p> | |
1068 </dd> | |
1069 <dt class="hdlist1"> | |
1070 <em>name</em> = command line | |
1071 </dt> | |
1072 <dd> | |
1073 <p> | |
1074 Set alias called "name" with value "command line" | |
1075 </p> | |
1076 <div class="literalblock"> | |
1077 <div class="content"> | |
1078 <pre><tt>Example: "/alias away = status away"</tt></pre> | |
1079 </div></div> | |
1080 </dd> | |
1081 </dl></div> | |
1082 </dd> | |
1083 <dt class="hdlist1"> | |
1084 /authorization allow|cancel|request|request_unsubscribe [jid] | |
1085 </dt> | |
1086 <dd> | |
1087 <p> | |
1088 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 /> | |
1089 If no JID is provided, the currently-selected buddy is used. | |
1090 </p> | |
1091 <div class="dlist"><dl> | |
1092 <dt class="hdlist1"> | |
1093 <em>allow</em> | |
1094 </dt> | |
1095 <dd> | |
1096 <p> | |
1097 Allow the buddy to receive your presence updates | |
1098 </p> | |
1099 </dd> | |
1100 <dt class="hdlist1"> | |
1101 <em>cancel</em> | |
1102 </dt> | |
1103 <dd> | |
1104 <p> | |
1105 Cancel the buddy’s subscription to your presence updates | |
1106 </p> | |
1107 </dd> | |
1108 <dt class="hdlist1"> | |
1109 <em>request</em> | |
1110 </dt> | |
1111 <dd> | |
1112 <p> | |
1113 Request a subscription to the buddy’s presence updates | |
1114 </p> | |
1115 </dd> | |
1116 <dt class="hdlist1"> | |
1117 <em>request_unsubscribe</em> | |
1118 </dt> | |
1119 <dd> | |
1120 <p> | |
1121 Request unsubscription from the buddy’s presence updates | |
1122 </p> | |
1123 </dd> | |
1124 </dl></div> | |
1125 </dd> | |
1126 <dt class="hdlist1"> | |
1127 /bind [keycode [= command line]] | |
1128 </dt> | |
1129 <dd> | |
1130 <p> | |
1131 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. | |
1132 </p> | |
1133 <div class="dlist"><dl> | |
1134 <dt class="hdlist1"> | |
1135 (without arguments) | |
1136 </dt> | |
1137 <dd> | |
1138 <p> | |
1139 Display list of current bindings | |
1140 </p> | |
1141 </dd> | |
1142 <dt class="hdlist1"> | |
1143 <em>keycode</em> | |
1144 </dt> | |
1145 <dd> | |
1146 <p> | |
1147 Display the command line bound to this key | |
1148 </p> | |
1149 </dd> | |
1150 <dt class="hdlist1"> | |
1151 <em>keycode</em>= | |
1152 </dt> | |
1153 <dd> | |
1154 <p> | |
1155 Unbind key with code "keycode" | |
1156 </p> | |
1157 </dd> | |
1158 <dt class="hdlist1"> | |
1159 <em>keycode</em> = command line | |
1160 </dt> | |
286
a3d65d7f0bc3
Add /alias documentation
Mikael Berthe <mikael@lilotux.net>
parents:
277
diff
changeset
|
1161 <dd> |
1759 | 1162 <p> |
1163 Bind "command line" to the key with code "keycode" | |
1164 </p> | |
1165 <div class="literalblock"> | |
1166 <div class="content"> | |
1167 <pre><tt>Example: "/bind 265 = status away" (265 is F1). + | |
1168 Note: keycodes can be different depending on your ncurses configuration. + | |
1169 Tip: aliases also can be used instead of commands.</tt></pre> | |
1170 </div></div> | |
1171 </dd> | |
1172 </dl></div> | |
1173 </dd> | |
1174 <dt class="hdlist1"> | |
1175 /buffer clear|close|close_all|purge|list | |
1176 </dt> | |
1177 <dt class="hdlist1"> | |
1178 /buffer top|bottom|date|%|search_backward|search_forward | |
1179 </dt> | |
1180 <dt class="hdlist1"> | |
1181 /buffer scroll_lock|scroll_unlock|scroll_toggle | |
1182 </dt> | |
1183 <dt class="hdlist1"> | |
1184 /buffer save filename | |
1185 </dt> | |
1186 <dd> | |
1187 <p> | |
1842 | 1188 Buddy’s buffer manipulation command. E.g. you can search through buffer for "text", clear chat window etc. |
1759 | 1189 </p> |
1190 <div class="dlist"><dl> | |
1191 <dt class="hdlist1"> | |
1192 <em>clear</em> | |
1193 </dt> | |
1194 <dd> | |
1195 <p> | |
1196 Clear the current buddy chat window | |
1197 </p> | |
289 | 1198 </dd> |
1759 | 1199 <dt class="hdlist1"> |
1200 <em>close</em> [jid] | |
1201 </dt> | |
1202 <dd> | |
1203 <p> | |
1204 Empty all contents of the buffer and close the current buddy chat window | |
1205 </p> | |
1206 </dd> | |
1207 <dt class="hdlist1"> | |
1208 <em>close_all</em> | |
1209 </dt> | |
1210 <dd> | |
1211 <p> | |
1212 Empty all contents of the chat buffers and close the chat windows | |
1213 </p> | |
1214 </dd> | |
1215 <dt class="hdlist1"> | |
1216 <em>purge</em> [jid] | |
1217 </dt> | |
1218 <dd> | |
1219 <p> | |
1220 Clear the current buddy chat window and empty all contents of the chat buffer | |
1221 </p> | |
1222 </dd> | |
1223 <dt class="hdlist1"> | |
1224 <em>list</em> | |
1225 </dt> | |
1226 <dd> | |
1227 <p> | |
1228 Display the list of existing buffers, with their length (lines/blocks) | |
1229 </p> | |
1230 </dd> | |
1231 <dt class="hdlist1"> | |
1232 <em>top</em> | |
1233 </dt> | |
1234 <dd> | |
1235 <p> | |
1236 Jump to the top of the current buddy chat buffer | |
1237 </p> | |
1238 </dd> | |
1239 <dt class="hdlist1"> | |
1240 <em>bottom</em> | |
1241 </dt> | |
289 | 1242 <dd> |
1759 | 1243 <p> |
1244 Jump to the bottom of the current buddy chat buffer | |
1245 </p> | |
1246 </dd> | |
1247 <dt class="hdlist1"> | |
1248 <em>up</em> [n] | |
1249 </dt> | |
1250 <dd> | |
1251 <p> | |
1252 Scroll the buffer up [n] lines (default: half a screen) | |
1253 </p> | |
1254 </dd> | |
1255 <dt class="hdlist1"> | |
1256 <em>down</em> [n] | |
1257 </dt> | |
1258 <dd> | |
1259 <p> | |
1260 Scroll the buffer down [n] lines (default: half a screen) | |
1261 </p> | |
1262 </dd> | |
1263 <dt class="hdlist1"> | |
1264 <em>date</em> [date] | |
1265 </dt> | |
1266 <dd> | |
1267 <p> | |
1268 Jump to the first line after the specified [date] in the chat buffer (date format: "YYYY-mm-dd") | |
1269 </p> | |
1270 </dd> | |
1271 <dt class="hdlist1"> | |
1272 % n | |
1273 </dt> | |
1274 <dd> | |
1275 <p> | |
1276 Jump to position %n of the buddy chat buffer | |
1277 </p> | |
1278 </dd> | |
1279 <dt class="hdlist1"> | |
1280 <em>search_backward</em> text | |
1281 </dt> | |
1282 <dd> | |
1283 <p> | |
1284 Search for [text] in the current buddy chat buffer | |
1285 </p> | |
286
a3d65d7f0bc3
Add /alias documentation
Mikael Berthe <mikael@lilotux.net>
parents:
277
diff
changeset
|
1286 </dd> |
1759 | 1287 <dt class="hdlist1"> |
1288 <em>search_forward</em> text | |
1289 </dt> | |
1290 <dd> | |
1291 <p> | |
1292 Search for [text] in the current buddy chat buffer | |
1293 </p> | |
1294 </dd> | |
1295 <dt class="hdlist1"> | |
1296 <em>scroll_lock</em> | |
1297 </dt> | |
1298 <dd> | |
1299 <p> | |
1300 Lock buffer scrolling | |
1301 </p> | |
1302 </dd> | |
1303 <dt class="hdlist1"> | |
1304 <em>scroll_unlock</em> | |
1305 </dt> | |
1306 <dd> | |
1307 <p> | |
1308 Unlock buffer scrolling | |
1309 </p> | |
1310 </dd> | |
1311 <dt class="hdlist1"> | |
1312 <em>scroll_toggle</em> | |
1313 </dt> | |
1314 <dd> | |
1315 <p> | |
1316 Toggle buffer scrolling (lock/unlock) | |
1317 </p> | |
1318 </dd> | |
1319 <dt class="hdlist1"> | |
1320 <em>save</em> filename | |
1321 </dt> | |
1322 <dd> | |
1323 <p> | |
1324 Save the contents of the current buffer to the file "filename" | |
1325 </p> | |
1326 </dd> | |
1327 </dl></div> | |
1328 </dd> | |
1329 <dt class="hdlist1"> | |
1330 /chat_disable [--show-roster] | |
1331 </dt> | |
229 | 1332 <dd> |
1759 | 1333 <p> |
1334 Disable chat mode.<br /> | |
1335 With --show-roster, the fullscreen mode will be disabled. | |
1336 </p> | |
1337 </dd> | |
1338 <dt class="hdlist1"> | |
1339 /clear | |
1340 </dt> | |
1341 <dd> | |
1342 <p> | |
1343 This command is actually an alias for "/buffer clear". It clears the current buddy chat window. | |
1344 </p> | |
1345 </dd> | |
1346 <dt class="hdlist1"> | |
1347 /color roster (status wildcard (color|-)|clear) | |
1348 </dt> | |
1349 <dt class="hdlist1"> | |
1350 /color mucnick nick (color|-) | |
1351 </dt> | |
1352 <dt class="hdlist1"> | |
1353 /color muc (jid|.|*) [on|preset|off|-] | |
1354 </dt> | |
1355 <dd> | |
1356 <p> | |
1357 The <em>color</em> command allows setting dynamic color properties of the screen. | |
1358 </p> | |
1359 <div class="dlist"><dl> | |
1360 <dt class="hdlist1"> | |
1361 <em>roster</em> clear | |
1362 </dt> | |
1363 <dd> | |
1364 <p> | |
1842 | 1365 Remove all color rules for the roster. All roster items will get its default color. |
1759 | 1366 </p> |
1367 </dd> | |
1368 <dt class="hdlist1"> | |
1369 <em>roster</em> status wildcard color | |
1370 </dt> | |
1371 <dd> | |
1372 <p> | |
1842 | 1373 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. |
1759 | 1374 </p> |
1375 </dd> | |
1376 <dt class="hdlist1"> | |
1377 <em>mucnick</em> nick (color|-) | |
1378 </dt> | |
1379 <dd> | |
1380 <p> | |
1842 | 1381 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. |
1759 | 1382 </p> |
1383 </dd> | |
1384 <dt class="hdlist1"> | |
1385 <em>muc</em> (jid|.|*) [on|preset|off|-] | |
1386 </dt> | |
1387 <dd> | |
1388 <p> | |
1842 | 1389 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>. |
1759 | 1390 </p> |
1391 </dd> | |
1392 </dl></div> | |
1393 </dd> | |
1394 <dt class="hdlist1"> | |
1395 /connect | |
1396 </dt> | |
1397 <dd> | |
1398 <p> | |
1399 Establish connection to the Jabber server. | |
1400 </p> | |
1401 </dd> | |
1402 <dt class="hdlist1"> | |
1403 /del | |
1404 </dt> | |
1405 <dd> | |
1406 <p> | |
1407 Delete the current buddy from our roster, unsubscribe from its presence notification and unsubscribe it from ours. | |
1408 </p> | |
1409 </dd> | |
1410 <dt class="hdlist1"> | |
1411 /disconnect | |
1412 </dt> | |
1413 <dd> | |
1414 <p> | |
1415 Terminate the connection to the Jabber server.<br /> | |
1416 Note: the roster is only available when the connection to the server is active, so the buddylist is empty when disconnected. | |
1417 </p> | |
1418 </dd> | |
1419 <dt class="hdlist1"> | |
1420 /echo message | |
1421 </dt> | |
1422 <dd> | |
1423 <p> | |
1424 Display "message" in the log window. | |
1425 </p> | |
1426 </dd> | |
1427 <dt class="hdlist1"> | |
1428 /event #n|* accept|ignore|reject [event-specific arguments] | |
1429 </dt> | |
1430 <dt class="hdlist1"> | |
1431 /event list | |
1432 </dt> | |
1433 <dd> | |
1434 <p> | |
1435 Tell mcabber what to do about pending events.<br /> | |
1436 If the first parameter is <em>*</em>, the command will apply to all queued events.<br /> | |
1842 | 1437 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. |
1759 | 1438 </p> |
1439 <div class="dlist"><dl> | |
1440 <dt class="hdlist1"> | |
1441 #N|* accept [event-specific arguments] | |
1442 </dt> | |
1443 <dd> | |
1444 <p> | |
1445 Event number #N/All events will be accepted | |
1446 </p> | |
229 | 1447 </dd> |
1759 | 1448 <dt class="hdlist1"> |
1449 #N|* ignore [event-specific arguments] | |
1450 </dt> | |
229 | 1451 <dd> |
1759 | 1452 <p> |
1453 Event number #N/All events will be ignored | |
1454 </p> | |
229 | 1455 </dd> |
1759 | 1456 <dt class="hdlist1"> |
1457 #N|* reject [event-specific arguments] | |
1458 </dt> | |
1459 <dd> | |
1460 <p> | |
1461 Event number #N/All events will be rejected | |
1462 </p> | |
1463 </dd> | |
1464 <dt class="hdlist1"> | |
1465 <em>list</em> | |
1466 </dt> | |
870 | 1467 <dd> |
1759 | 1468 <p> |
1469 List all pending events | |
1470 </p> | |
870 | 1471 </dd> |
1759 | 1472 </dl></div> |
1473 </dd> | |
1474 <dt class="hdlist1"> | |
1475 /group fold|unfold|toggle [groupname] | |
1476 </dt> | |
854 | 1477 <dd> |
1759 | 1478 <p> |
1479 This command changes the current group display. | |
1480 </p> | |
1481 <div class="dlist"><dl> | |
1482 <dt class="hdlist1"> | |
1483 <em>fold</em> [groupname] | |
1484 </dt> | |
1485 <dd> | |
1486 <p> | |
1487 Fold (shrink) the current/specified group tree in the roster | |
1488 </p> | |
854 | 1489 </dd> |
1759 | 1490 <dt class="hdlist1"> |
1491 <em>unfold</em> [groupname] | |
1492 </dt> | |
1493 <dd> | |
1494 <p> | |
1495 Unfold (expand) the current/specified group tree in the roster | |
1496 </p> | |
1497 </dd> | |
1498 <dt class="hdlist1"> | |
1499 <em>toggle</em> [groupname] | |
1500 </dt> | |
1242 | 1501 <dd> |
1759 | 1502 <p> |
1503 Toggle the state (fold/unfold) of the current/specified tree | |
1504 </p> | |
1505 </dd> | |
1506 </dl></div> | |
1242 | 1507 </dd> |
1759 | 1508 <dt class="hdlist1"> |
1509 /help [command|+topic] | |
1510 </dt> | |
1242 | 1511 <dd> |
1759 | 1512 <p> |
1513 Display help for command "command" or topic "topic".<br /> | |
1514 Example: "/help buffer" | |
1515 </p> | |
1242 | 1516 </dd> |
1759 | 1517 <dt class="hdlist1"> |
1518 /iline fchar|bchar|char_fdel|char_bdel|char_swap | |
1519 </dt> | |
1520 <dt class="hdlist1"> | |
1521 /iline fword|bword|word_bdel|word_fdel | |
1522 </dt> | |
1523 <dt class="hdlist1"> | |
1524 /iline word_upcase|word_downcase|word_capit | |
1525 </dt> | |
1526 <dt class="hdlist1"> | |
1527 /iline hist_beginning_search_bwd|hist_beginning_search_fwd | |
1528 </dt> | |
1529 <dt class="hdlist1"> | |
1530 /iline hist_prev|hist_next | |
1531 </dt> | |
1532 <dt class="hdlist1"> | |
1533 /iline iline_start|iline_end|iline_fdel|iline_bdel | |
1534 </dt> | |
1535 <dt class="hdlist1"> | |
1536 /iline iline_accept|iline_accept_down_hist | |
1537 </dt> | |
1538 <dt class="hdlist1"> | |
1539 /iline compl_do|compl_cancel | |
1540 </dt> | |
1541 <dt class="hdlist1"> | |
1542 /iline send_multiline | |
1543 </dt> | |
854 | 1544 <dd> |
1759 | 1545 <p> |
1546 Input line commands | |
1547 </p> | |
1548 <div class="dlist"><dl> | |
1549 <dt class="hdlist1"> | |
1550 <em>fchar</em> | |
1551 </dt> | |
1552 <dd> | |
1553 <p> | |
1554 Move to the next letter | |
1555 </p> | |
854 | 1556 </dd> |
1759 | 1557 <dt class="hdlist1"> |
1558 <em>bchar</em> | |
1559 </dt> | |
298
35cda94e570d
Add /connect and /disconnect commands
Mikael Berthe <mikael@lilotux.net>
parents:
290
diff
changeset
|
1560 <dd> |
1759 | 1561 <p> |
1562 Move to the previous letter | |
1563 </p> | |
1564 </dd> | |
1565 <dt class="hdlist1"> | |
1566 <em>char_fdel</em> | |
1567 </dt> | |
1568 <dd> | |
1569 <p> | |
1570 Delete the letter at cursor position | |
1571 </p> | |
298
35cda94e570d
Add /connect and /disconnect commands
Mikael Berthe <mikael@lilotux.net>
parents:
290
diff
changeset
|
1572 </dd> |
1759 | 1573 <dt class="hdlist1"> |
1574 <em>char_bdel</em> | |
1575 </dt> | |
1576 <dd> | |
1577 <p> | |
1578 Delete the letter before cursor position | |
1579 </p> | |
1580 </dd> | |
1581 <dt class="hdlist1"> | |
1582 <em>char_swap</em> | |
1583 </dt> | |
1584 <dd> | |
1585 <p> | |
1586 Transpose chars | |
1587 </p> | |
1588 </dd> | |
1589 <dt class="hdlist1"> | |
1590 <em>fword</em> | |
1591 </dt> | |
298
35cda94e570d
Add /connect and /disconnect commands
Mikael Berthe <mikael@lilotux.net>
parents:
290
diff
changeset
|
1592 <dd> |
1759 | 1593 <p> |
1594 Move the cursor forward to the end of the current or next word | |
1595 </p> | |
1596 </dd> | |
1597 <dt class="hdlist1"> | |
1598 <em>bword</em> | |
1599 </dt> | |
1600 <dd> | |
1601 <p> | |
1602 Move the cursor back to the start of the current or previous word | |
1603 </p> | |
298
35cda94e570d
Add /connect and /disconnect commands
Mikael Berthe <mikael@lilotux.net>
parents:
290
diff
changeset
|
1604 </dd> |
1759 | 1605 <dt class="hdlist1"> |
1606 <em>word_bdel</em> | |
1607 </dt> | |
1608 <dd> | |
1609 <p> | |
1610 Delete the word from cursor position to its start | |
1611 </p> | |
1612 </dd> | |
1613 <dt class="hdlist1"> | |
1614 <em>word_fdel</em> | |
1615 </dt> | |
1616 <dd> | |
1617 <p> | |
1618 Delete the word from cursor position to its end | |
1619 </p> | |
1620 </dd> | |
1621 <dt class="hdlist1"> | |
1622 <em>word_upcase</em> | |
1623 </dt> | |
775
b4befb3052e5
Update NEWS, ChangeLog and documentation
Mikael Berthe <mikael@lilotux.net>
parents:
710
diff
changeset
|
1624 <dd> |
1759 | 1625 <p> |
1626 Convert the word from cursor position to its end to upper case | |
1627 </p> | |
1628 </dd> | |
1629 <dt class="hdlist1"> | |
1630 <em>word_downcase</em> | |
1631 </dt> | |
1632 <dd> | |
1633 <p> | |
1634 Convert the word from cursor position to its end to down case | |
1635 </p> | |
1636 </dd> | |
1637 <dt class="hdlist1"> | |
1638 <em>word_capit</em> | |
1639 </dt> | |
1640 <dd> | |
1641 <p> | |
1642 Capitalize the word from cursor position to its end | |
1643 </p> | |
1644 </dd> | |
1645 <dt class="hdlist1"> | |
1646 <em>hist_beginning_search_bwd</em> | |
1647 </dt> | |
1648 <dd> | |
1649 <p> | |
1650 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) | |
1651 </p> | |
775
b4befb3052e5
Update NEWS, ChangeLog and documentation
Mikael Berthe <mikael@lilotux.net>
parents:
710
diff
changeset
|
1652 </dd> |
1759 | 1653 <dt class="hdlist1"> |
1654 <em>hist_beginning_search_fwd</em> | |
1655 </dt> | |
854 | 1656 <dd> |
1759 | 1657 <p> |
1658 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) | |
1659 </p> | |
1660 </dd> | |
1661 <dt class="hdlist1"> | |
1662 <em>hist_prev</em> | |
1663 </dt> | |
1664 <dd> | |
1665 <p> | |
1666 Previous line of input line history | |
1667 </p> | |
854 | 1668 </dd> |
1759 | 1669 <dt class="hdlist1"> |
1670 <em>hist_next</em> | |
1671 </dt> | |
854 | 1672 <dd> |
1759 | 1673 <p> |
1674 Next line of input line history | |
1675 </p> | |
854 | 1676 </dd> |
1759 | 1677 <dt class="hdlist1"> |
1678 <em>iline_start</em> | |
1679 </dt> | |
1680 <dd> | |
1681 <p> | |
1682 Go to the beginning of the input line | |
1683 </p> | |
1684 </dd> | |
1685 <dt class="hdlist1"> | |
1686 <em>iline_end</em> | |
1687 </dt> | |
854 | 1688 <dd> |
1759 | 1689 <p> |
1690 Go to the end of the input line | |
1691 </p> | |
1692 </dd> | |
1693 <dt class="hdlist1"> | |
1694 <em>iline_fdel</em> | |
1695 </dt> | |
1696 <dd> | |
1697 <p> | |
1698 Delete from the cursor to the end of line | |
1699 </p> | |
1700 </dd> | |
1701 <dt class="hdlist1"> | |
1702 <em>iline_bdel</em> | |
1703 </dt> | |
1704 <dd> | |
1705 <p> | |
1706 Delete from beginning of the line to the cursor | |
1707 </p> | |
1708 </dd> | |
1709 <dt class="hdlist1"> | |
1710 <em>iline_accept</em> | |
1711 </dt> | |
1712 <dd> | |
1713 <p> | |
1714 Accept line | |
1715 </p> | |
854 | 1716 </dd> |
1759 | 1717 <dt class="hdlist1"> |
1718 <em>iline_accept_down_hist</em> | |
1719 </dt> | |
1720 <dd> | |
1721 <p> | |
1722 Accept line and put the next history line in the input line | |
1723 </p> | |
1724 </dd> | |
1725 <dt class="hdlist1"> | |
1726 <em>compl_do</em> | |
1727 </dt> | |
854 | 1728 <dd> |
1759 | 1729 <p> |
1730 Complete current word, in the input line | |
1731 </p> | |
854 | 1732 </dd> |
1759 | 1733 <dt class="hdlist1"> |
1734 <em>compl_cancel</em> | |
1735 </dt> | |
1736 <dd> | |
1737 <p> | |
1738 Cancel completion | |
1739 </p> | |
1740 </dd> | |
1741 <dt class="hdlist1"> | |
1742 <em>send_multiline</em> | |
1743 </dt> | |
229 | 1744 <dd> |
1759 | 1745 <p> |
1746 Send/terminate a multi-line message | |
1747 </p> | |
1748 </dd> | |
1749 </dl></div> | |
1750 </dd> | |
1751 <dt class="hdlist1"> | |
1752 /info | |
1753 </dt> | |
1754 <dd> | |
1755 <p> | |
1756 Display info on the selected entry (user, agent, group…).<br /> | |
1757 For users, resources are displayed with the status, priority and status message (if available) of each resource. | |
1758 </p> | |
1759 </dd> | |
1760 <dt class="hdlist1"> | |
1761 /module load|unload [-f] module | |
1762 </dt> | |
1763 <dt class="hdlist1"> | |
1764 /module info module | |
1765 </dt> | |
1766 <dt class="hdlist1"> | |
1767 /module [list] | |
1768 </dt> | |
1769 <dd> | |
1770 <p> | |
1771 Load, unload or show info on module. | |
1772 </p> | |
1773 <div class="dlist"><dl> | |
1774 <dt class="hdlist1"> | |
1775 <em>load</em> [-f] module | |
1776 </dt> | |
1777 <dd> | |
1778 <p> | |
1842 | 1779 Loads specified module. If -f flag is specified, most of module loading errors will be ignored. |
1759 | 1780 </p> |
229 | 1781 </dd> |
1759 | 1782 <dt class="hdlist1"> |
1783 <em>unload</em> [-f] module | |
1784 </dt> | |
1785 <dd> | |
1786 <p> | |
1842 | 1787 Unloads specified module. Note: The force flag will not remove any dependency on this module! |
1759 | 1788 </p> |
1789 </dd> | |
1790 <dt class="hdlist1"> | |
1791 <em>info</em> module | |
1792 </dt> | |
229 | 1793 <dd> |
1759 | 1794 <p> |
1795 Shows available information about this module. | |
1796 </p> | |
229 | 1797 </dd> |
1759 | 1798 <dt class="hdlist1"> |
1799 [<em>list</em>] | |
1800 </dt> | |
1801 <dd> | |
1802 <p> | |
1803 Lists modules in a format: [modulename] [reference count] ([Manually/Automatically loaded]) [any extra info, like version or dependencies] | |
1804 </p> | |
1805 </dd> | |
1806 </dl></div> | |
1807 </dd> | |
1808 <dt class="hdlist1"> | |
229 | 1809 /move [groupname] |
1759 | 1810 </dt> |
229 | 1811 <dd> |
1759 | 1812 <p> |
1813 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 /> | |
1814 Tip: if the chatmode is enabled, you can use "/roster alternate" to jump to the moved buddy. | |
1815 </p> | |
229 | 1816 </dd> |
1759 | 1817 <dt class="hdlist1"> |
839 | 1818 /msay begin|verbatim|send|send_to|toggle|toggle_verbatim|abort |
1759 | 1819 </dt> |
1820 <dd> | |
1821 <p> | |
1822 Send a multi-line message. To write a single message with several lines, the <em>multi-line mode</em> should be used.<br /> | |
1823 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 /> | |
1824 The <em>begin</em> subcommand enables multi-line mode. Note that it allows a message subject to be specified.<br /> | |
1825 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 /> | |
1826 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). | |
1827 </p> | |
1828 <div class="dlist"><dl> | |
1829 <dt class="hdlist1"> | |
1830 <em>begin</em> [subject] | |
1831 </dt> | |
1832 <dd> | |
1833 <p> | |
1834 Enter multi-line mode | |
1835 </p> | |
1836 </dd> | |
1837 <dt class="hdlist1"> | |
1838 <em>verbatim</em> | |
1839 </dt> | |
1840 <dd> | |
1841 <p> | |
1842 Enter verbatim multi-line mode | |
1843 </p> | |
1844 </dd> | |
1845 <dt class="hdlist1"> | |
1846 <em>send</em> [-n|-h] | |
1847 </dt> | |
1848 <dd> | |
1849 <p> | |
1850 Send the current multi-line message to the currently selected buddy | |
1851 </p> | |
1852 </dd> | |
1853 <dt class="hdlist1"> | |
1854 <em>send_to</em> [-n|-h] jid | |
1855 </dt> | |
1856 <dd> | |
1857 <p> | |
1858 Send the current multi-line message to "jid" | |
1859 </p> | |
1860 </dd> | |
1861 <dt class="hdlist1"> | |
1862 <em>toggle</em>|<em>toggle_verbatim</em> | |
1863 </dt> | |
1864 <dd> | |
1865 <p> | |
1866 Switch to/from multi-line mode (begin/send) | |
1867 </p> | |
1868 </dd> | |
1869 <dt class="hdlist1"> | |
1870 <em>abort</em> | |
1871 </dt> | |
1872 <dd> | |
1873 <p> | |
1874 Leave multi-line mode without sending the message | |
1875 </p> | |
1876 <div class="literalblock"> | |
1877 <div class="content"> | |
1878 <pre><tt>The -n or -h flags turn the message to "normal" or "headline" accordingly, as opposed to default "chat" message.</tt></pre> | |
1879 </div></div> | |
1880 </dd> | |
1881 </dl></div> | |
1882 </dd> | |
1883 <dt class="hdlist1"> | |
1884 /otr key | |
1885 </dt> | |
1886 <dt class="hdlist1"> | |
1887 /otr start|stop|info [jid] | |
1888 </dt> | |
1889 <dt class="hdlist1"> | |
1890 /otr fingerprint [jid [fpr]] | |
1891 </dt> | |
1892 <dt class="hdlist1"> | |
1893 /otr smpq|smpr [jid] secret | |
1894 </dt> | |
1895 <dt class="hdlist1"> | |
1896 /otr smpa [jid] | |
1897 </dt> | |
1898 <dd> | |
1899 <p> | |
1900 You can use the shortcut-jid "." for the currently selected contact. | |
1901 </p> | |
1902 <div class="dlist"><dl> | |
1903 <dt class="hdlist1"> | |
1904 <em>key</em> | |
1905 </dt> | |
238 | 1906 <dd> |
1759 | 1907 <p> |
1908 Print the fingerprint of your private key to the Status Buffer | |
1909 </p> | |
1910 </dd> | |
1911 <dt class="hdlist1"> | |
1912 <em>start</em> [jid] | |
1913 </dt> | |
1914 <dd> | |
1915 <p> | |
1916 Open an OTR channel to the specified jid (or the currently selected contact) | |
1917 </p> | |
1918 </dd> | |
1919 <dt class="hdlist1"> | |
1920 <em>stop</em> [jid] | |
1921 </dt> | |
1922 <dd> | |
1923 <p> | |
1924 Close the OTR channel to the specified jid (or the currently selected contact) | |
1925 </p> | |
1926 </dd> | |
1927 <dt class="hdlist1"> | |
1928 <em>info</em> [jid] | |
1929 </dt> | |
1930 <dd> | |
1931 <p> | |
1932 Show current OTR status for the specified jid (or the currently selected contact) | |
1933 </p> | |
1934 </dd> | |
1935 <dt class="hdlist1"> | |
1936 <em>fingerprint</em> [jid [fpr]] | |
1937 </dt> | |
1938 <dd> | |
1939 <p> | |
1842 | 1940 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. |
1759 | 1941 </p> |
1942 </dd> | |
1943 <dt class="hdlist1"> | |
1944 <em>smpq</em> [jid] secret | |
1945 </dt> | |
1946 <dd> | |
1947 <p> | |
1948 Initiate the Socialist Millionaires Protocol with the secret and the buddy | |
1949 </p> | |
1950 </dd> | |
1951 <dt class="hdlist1"> | |
1952 <em>smpr</em> [jid] secret | |
1953 </dt> | |
1954 <dd> | |
1955 <p> | |
1956 Respond to the Initiation of the jid with the secret | |
1957 </p> | |
1958 </dd> | |
1959 <dt class="hdlist1"> | |
1960 <em>smpa</em> [jid] | |
1961 </dt> | |
1962 <dd> | |
1963 <p> | |
1964 Abort the running Socialist Millionaires Protocol | |
1965 </p> | |
1966 </dd> | |
1967 </dl></div> | |
1968 </dd> | |
1969 <dt class="hdlist1"> | |
1970 /otrpolicy | |
1971 </dt> | |
1972 <dt class="hdlist1"> | |
1973 /otrpolicy (default|jid) (plain|manual|opportunistic|always) | |
1974 </dt> | |
1975 <dd> | |
1976 <p> | |
1977 You can use the shortcut-jid "." for the currently selected contact. | |
1978 </p> | |
1979 <div class="dlist"><dl> | |
1980 <dt class="hdlist1"> | |
1981 (without arguments) | |
1982 </dt> | |
1983 <dd> | |
1984 <p> | |
1985 Prints all OTR policies to the status buffer | |
1986 </p> | |
1987 </dd> | |
1988 <dt class="hdlist1"> | |
1989 (<em>default</em>|<em>jid</em>) (plain|manual|opportunistic|always) | |
1990 </dt> | |
1991 <dd> | |
1992 <p> | |
1842 | 1993 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. |
1759 | 1994 </p> |
1995 </dd> | |
1996 </dl></div> | |
238 | 1997 </dd> |
1759 | 1998 <dt class="hdlist1"> |
1242 | 1999 /pgp disable|enable|force|info [jid] |
1759 | 2000 </dt> |
2001 <dt class="hdlist1"> | |
1096 | 2002 /pgp setkey [jid [key]] |
1759 | 2003 </dt> |
2004 <dd> | |
2005 <p> | |
2006 This command manipulates PGP settings for the specified jid (by default the currently selected contact).<br /> | |
2007 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. | |
2008 </p> | |
2009 <div class="dlist"><dl> | |
2010 <dt class="hdlist1"> | |
2011 <em>disable</em> [jid] | |
2012 </dt> | |
2013 <dd> | |
2014 <p> | |
2015 Disable PGP encryption for jid (or the currently selected contact) | |
2016 </p> | |
2017 </dd> | |
2018 <dt class="hdlist1"> | |
2019 <em>enable</em> [jid] | |
2020 </dt> | |
2021 <dd> | |
2022 <p> | |
2023 Enable PGP encryption for jid (or the currently selected contact) | |
2024 </p> | |
2025 </dd> | |
2026 <dt class="hdlist1"> | |
2027 <em style="color:+|-;">force</em> [jid] | |
2028 </dt> | |
2029 <dd> | |
2030 <p> | |
2031 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. | |
2032 </p> | |
2033 </dd> | |
2034 <dt class="hdlist1"> | |
2035 <em>info</em> [jid] | |
2036 </dt> | |
2037 <dd> | |
2038 <p> | |
2039 Show current PGP settings for the contact | |
2040 </p> | |
2041 </dd> | |
2042 <dt class="hdlist1"> | |
2043 <em>setkey</em> [jid [key]] | |
2044 </dt> | |
2045 <dd> | |
2046 <p> | |
2047 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. | |
2048 </p> | |
2049 </dd> | |
2050 </dl></div> | |
2051 </dd> | |
2052 <dt class="hdlist1"> | |
2053 /quit | |
2054 </dt> | |
2055 <dd> | |
2056 <p> | |
2057 This command closes all connections and quit mcabber. | |
2058 </p> | |
2059 </dd> | |
2060 <dt class="hdlist1"> | |
2061 /rawxml send string | |
2062 </dt> | |
2063 <dd> | |
2064 <p> | |
2065 Send "string" (raw XML format) to the Jabber server.<br /> | |
2066 No check is done on the string provided.<br /> | |
2067 BEWARE! | |
2068 Use this only if you know what you are doing, or you could terminate the connection.<br /> | |
2069 Example: "/rawxml send <presence><show>away</show></presence>" | |
2070 </p> | |
2071 </dd> | |
2072 <dt class="hdlist1"> | |
2073 /rename name | |
2074 </dt> | |
2075 <dd> | |
2076 <p> | |
2077 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). | |
2078 </p> | |
2079 </dd> | |
2080 <dt class="hdlist1"> | |
2081 /request last|ping|time|vcard|version [jid] | |
2082 </dt> | |
2083 <dd> | |
2084 <p> | |
2085 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. | |
2086 </p> | |
2087 <div class="dlist"><dl> | |
2088 <dt class="hdlist1"> | |
2089 <em>last</em> | |
2090 </dt> | |
2091 <dd> | |
2092 <p> | |
2093 Request "last" information (usually idle time) | |
2094 </p> | |
2095 </dd> | |
2096 <dt class="hdlist1"> | |
2097 <em>ping</em> | |
2098 </dt> | |
1096 | 2099 <dd> |
1759 | 2100 <p> |
2101 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. | |
2102 </p> | |
2103 </dd> | |
2104 <dt class="hdlist1"> | |
2105 <em>time</em> | |
2106 </dt> | |
2107 <dd> | |
2108 <p> | |
2109 Request time from the buddy | |
2110 </p> | |
2111 </dd> | |
2112 <dt class="hdlist1"> | |
2113 <em>vcard</em> | |
2114 </dt> | |
2115 <dd> | |
2116 <p> | |
2117 Request VCard from the buddy | |
2118 </p> | |
2119 </dd> | |
2120 <dt class="hdlist1"> | |
2121 <em>version</em> | |
2122 </dt> | |
2123 <dd> | |
2124 <p> | |
2125 Request version from the buddy | |
2126 </p> | |
2127 </dd> | |
2128 </dl></div> | |
2129 </dd> | |
2130 <dt class="hdlist1"> | |
2131 /room join|leave|names|nick|remove|topic|unlock|destroy | |
2132 </dt> | |
2133 <dt class="hdlist1"> | |
2134 /room privmsg|invite|whois|kick|ban|unban|role|affil | |
2135 </dt> | |
2136 <dt class="hdlist1"> | |
2137 /room setopt print_status|auto_whois [value] | |
2138 </dt> | |
2139 <dt class="hdlist1"> | |
2140 /room bookmark [add|del] [-autojoin|+autojoin] [-|nick] | |
2141 </dt> | |
2142 <dd> | |
2143 <p> | |
2144 The <em>room</em> command handles Multi-User Chat room actions. | |
2145 </p> | |
2146 <div class="dlist"><dl> | |
2147 <dt class="hdlist1"> | |
2148 <em>join</em> [room [nick [pass]]] | |
2149 </dt> | |
2150 <dd> | |
2151 <p> | |
2152 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. | |
2153 </p> | |
1096 | 2154 </dd> |
1759 | 2155 <dt class="hdlist1"> |
2156 <em>leave</em> [message] | |
2157 </dt> | |
2158 <dd> | |
2159 <p> | |
2160 Leave the current room | |
2161 </p> | |
2162 </dd> | |
2163 <dt class="hdlist1"> | |
2164 <em>names</em> [--detail|--short|--quiet|--compact] | |
2165 </dt> | |
229 | 2166 <dd> |
1759 | 2167 <p> |
2168 Display members of the current room | |
2169 </p> | |
450 | 2170 </dd> |
1759 | 2171 <dt class="hdlist1"> |
2172 <em>nick</em> newnick | |
2173 </dt> | |
2174 <dd> | |
2175 <p> | |
2176 Change your nickname in the current room | |
2177 </p> | |
2178 </dd> | |
2179 <dt class="hdlist1"> | |
2180 <em>privmsg</em> nick msg | |
2181 </dt> | |
700 | 2182 <dd> |
1759 | 2183 <p> |
2184 Send private message "msg" to "nick" | |
2185 </p> | |
2186 </dd> | |
2187 <dt class="hdlist1"> | |
2188 <em>remove</em> | |
2189 </dt> | |
2190 <dd> | |
2191 <p> | |
2192 Remove the current room from the roster (you must have left this room before) | |
2193 </p> | |
700 | 2194 </dd> |
1759 | 2195 <dt class="hdlist1"> |
2196 <em>topic</em> -|newtopic | |
2197 </dt> | |
2198 <dd> | |
2199 <p> | |
2200 Set topic for current room | |
2201 </p> | |
2202 </dd> | |
2203 <dt class="hdlist1"> | |
2204 <em>unlock</em> | |
2205 </dt> | |
2206 <dd> | |
2207 <p> | |
2208 Unlock current room (if you are the owner) | |
2209 </p> | |
2210 </dd> | |
2211 <dt class="hdlist1"> | |
2212 <em>destroy</em> [reason] | |
2213 </dt> | |
450 | 2214 <dd> |
1759 | 2215 <p> |
2216 Destroy the current room (use with care!) | |
2217 </p> | |
2218 </dd> | |
2219 <dt class="hdlist1"> | |
2220 <em>whois</em> nick | |
2221 </dt> | |
2222 <dd> | |
2223 <p> | |
2224 Display MUC information about "nick" | |
2225 </p> | |
2226 </dd> | |
2227 <dt class="hdlist1"> | |
2228 <em>ban</em> jid [reason] | |
2229 </dt> | |
2230 <dd> | |
2231 <p> | |
2232 Ban jid from the current room | |
2233 </p> | |
2234 </dd> | |
2235 <dt class="hdlist1"> | |
2236 <em>unban</em> jid | |
2237 </dt> | |
2238 <dd> | |
2239 <p> | |
2240 Unban jid from the current room | |
2241 </p> | |
2242 </dd> | |
2243 <dt class="hdlist1"> | |
2244 <em>invite</em> jid [reason] | |
2245 </dt> | |
2246 <dd> | |
2247 <p> | |
2248 Invite jid to the current room | |
2249 </p> | |
2250 </dd> | |
2251 <dt class="hdlist1"> | |
2252 <em>kick</em> nick [reason] | |
2253 </dt> | |
2254 <dd> | |
2255 <p> | |
2256 Kick "nick" from the current room | |
2257 </p> | |
2258 </dd> | |
2259 <dt class="hdlist1"> | |
2260 <em>role</em> jid role [reason] | |
2261 </dt> | |
2262 <dd> | |
2263 <p> | |
2264 Change jid’s role (role can be "none", "visitor", "participant", "moderator") | |
2265 </p> | |
2266 </dd> | |
2267 <dt class="hdlist1"> | |
2268 <em>affil</em> jid affil [reason] | |
2269 </dt> | |
2270 <dd> | |
2271 <p> | |
2272 Change jid’s affiliation (affil can be "none", "member", "admin", "owner") | |
2273 </p> | |
2274 </dd> | |
2275 <dt class="hdlist1"> | |
2276 <em>setopt</em> print_status|auto_whois [value] | |
2277 </dt> | |
2278 <dd> | |
2279 <p> | |
2280 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. | |
2281 </p> | |
2282 </dd> | |
2283 <dt class="hdlist1"> | |
2284 <em>bookmark</em> [add|del] [-autojoin|+autojoin] [-|nick] | |
2285 </dt> | |
2286 <dd> | |
2287 <p> | |
2288 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. | |
2289 </p> | |
2290 </dd> | |
2291 </dl></div> | |
229 | 2292 </dd> |
1759 | 2293 <dt class="hdlist1"> |
1096 | 2294 /roster bottom|top|up|down|group_prev|group_next |
1759 | 2295 </dt> |
2296 <dt class="hdlist1"> | |
360
20283b69db99
Doc: Say a Jabber account should already exist for using mcabber
Mikael Berthe <mikael@lilotux.net>
parents:
345
diff
changeset
|
2297 /roster alternate|unread_first|unread_next |
1759 | 2298 </dt> |
2299 <dt class="hdlist1"> | |
265 | 2300 /roster search bud |
1759 | 2301 </dt> |
2302 <dt class="hdlist1"> | |
2303 /roster display|hide_offline|show_offline|toggle_offline | |
2304 </dt> | |
2305 <dt class="hdlist1"> | |
2306 /roster item_lock|item_unlock|item_toggle_lock | |
2307 </dt> | |
2308 <dt class="hdlist1"> | |
1096 | 2309 /roster hide|show|toggle |
1759 | 2310 </dt> |
2311 <dt class="hdlist1"> | |
1096 | 2312 /roster note [-|text] |
1759 | 2313 </dt> |
2314 <dd> | |
2315 <p> | |
2316 The <em>roster</em> command manipulates the roster/buddylist.<br /> | |
2317 Here are the available parameters: | |
2318 </p> | |
2319 <div class="dlist"><dl> | |
2320 <dt class="hdlist1"> | |
2321 <em>bottom</em> | |
2322 </dt> | |
2323 <dd> | |
2324 <p> | |
2325 Jump to the bottom of the roster | |
2326 </p> | |
2327 </dd> | |
2328 <dt class="hdlist1"> | |
2329 <em>top</em> | |
2330 </dt> | |
2331 <dd> | |
2332 <p> | |
2333 Jump to the top of the roster | |
2334 </p> | |
2335 </dd> | |
2336 <dt class="hdlist1"> | |
2337 <em>up</em> [n] | |
2338 </dt> | |
2339 <dd> | |
2340 <p> | |
2341 Move up [n lines] in the roster | |
2342 </p> | |
2343 </dd> | |
2344 <dt class="hdlist1"> | |
2345 <em>down</em> [n] | |
2346 </dt> | |
2347 <dd> | |
2348 <p> | |
2349 Move down [n lines] in the roster | |
2350 </p> | |
2351 </dd> | |
2352 <dt class="hdlist1"> | |
2353 <em>group_prev</em> | |
2354 </dt> | |
2355 <dd> | |
2356 <p> | |
2357 Jump to the previous group in the roster | |
2358 </p> | |
2359 </dd> | |
2360 <dt class="hdlist1"> | |
2361 <em>group_next</em> | |
2362 </dt> | |
2363 <dd> | |
2364 <p> | |
2365 Jump to the next group in the roster | |
2366 </p> | |
2367 </dd> | |
2368 <dt class="hdlist1"> | |
2369 <em>alternate</em> | |
2370 </dt> | |
2371 <dd> | |
2372 <p> | |
2373 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). | |
2374 </p> | |
2375 </dd> | |
2376 <dt class="hdlist1"> | |
2377 <em>unread_first</em> | |
2378 </dt> | |
2379 <dd> | |
2380 <p> | |
2381 Jump to the first unread message | |
2382 </p> | |
2383 </dd> | |
2384 <dt class="hdlist1"> | |
2385 <em>unread_next</em> | |
2386 </dt> | |
2387 <dd> | |
2388 <p> | |
2389 Jump to the next unread message | |
2390 </p> | |
2391 </dd> | |
2392 <dt class="hdlist1"> | |
2393 <em>search</em> bud | |
2394 </dt> | |
2395 <dd> | |
2396 <p> | |
2397 Search for a buddy with a name or jid containing "bud" (only in the displayed buddylist) | |
2398 </p> | |
2399 </dd> | |
2400 <dt class="hdlist1"> | |
2401 <em>display</em> [mask] | |
2402 </dt> | |
2403 <dd> | |
2404 <p> | |
2405 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. | |
2406 </p> | |
2407 </dd> | |
2408 <dt class="hdlist1"> | |
2409 <em>hide_offline</em> | |
2410 </dt> | |
229 | 2411 <dd> |
1759 | 2412 <p> |
2413 Hide offline buddies (same as /roster display ofdna) | |
2414 </p> | |
2415 </dd> | |
2416 <dt class="hdlist1"> | |
2417 <em>show_offline</em> | |
2418 </dt> | |
2419 <dd> | |
2420 <p> | |
2421 Show offline buddies (same as /roster display ofdna_) | |
2422 </p> | |
2423 </dd> | |
2424 <dt class="hdlist1"> | |
2425 <em>toggle_offline</em> | |
2426 </dt> | |
2427 <dd> | |
2428 <p> | |
2429 Toggle display of offline buddies | |
2430 </p> | |
2431 </dd> | |
2432 <dt class="hdlist1"> | |
2433 <em>item_lock</em> [jid] | |
2434 </dt> | |
2435 <dd> | |
2436 <p> | |
2437 Lock the roster item so it remains visible regardless of its status | |
2438 </p> | |
2439 </dd> | |
2440 <dt class="hdlist1"> | |
2441 <em>item_unlock</em> [jid] | |
2442 </dt> | |
2443 <dd> | |
2444 <p> | |
2445 Undo the effects of item_lock | |
2446 </p> | |
2447 </dd> | |
2448 <dt class="hdlist1"> | |
2449 <em>item_toggle_lock</em> [jid] | |
2450 </dt> | |
2451 <dd> | |
2452 <p> | |
2453 Invert the current lock flag | |
2454 </p> | |
2455 </dd> | |
2456 <dt class="hdlist1"> | |
2457 <em>hide</em> | |
2458 </dt> | |
2459 <dd> | |
2460 <p> | |
2461 Hide roster (full-width chat window) | |
2462 </p> | |
2463 </dd> | |
2464 <dt class="hdlist1"> | |
2465 <em>show</em> | |
2466 </dt> | |
2467 <dd> | |
2468 <p> | |
2469 Show roster | |
2470 </p> | |
2471 </dd> | |
2472 <dt class="hdlist1"> | |
2473 <em>toggle</em> | |
2474 </dt> | |
2475 <dd> | |
2476 <p> | |
2477 Toggle roster visibility | |
2478 </p> | |
2479 </dd> | |
2480 <dt class="hdlist1"> | |
2481 <em>note</em> [-|text] | |
2482 </dt> | |
2483 <dd> | |
2484 <p> | |
2485 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. | |
2486 </p> | |
2487 </dd> | |
2488 </dl></div> | |
2489 </dd> | |
2490 <dt class="hdlist1"> | |
2491 /say [-n|-h|--] text | |
2492 </dt> | |
2493 <dd> | |
2494 <p> | |
2495 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 /> | |
1842 | 2496 The "-n" flag turns the message to "normal" type, "-h" to "headline". "--" can be used to send chat message beginning with -n or -h. |
1759 | 2497 </p> |
2498 </dd> | |
2499 <dt class="hdlist1"> | |
2500 /say_to [-n|-h] [-q] [-f file] jid text | |
2501 </dt> | |
2502 <dd> | |
2503 <p> | |
2504 Send the "text" message to the specified jid.<br /> | |
2505 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 /> | |
1924
57c352ed37f9
Update help/documentation
Mikael Berthe <mikael@lilotux.net>
parents:
1891
diff
changeset
|
2506 You can send a message to a specific resource of the currently selected contact by using /say_to ./resourcename message.<br /> |
1759 | 2507 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 /> |
2508 When "-q" is used, the message will be sent in the background and will not change the current active window.<br /> | |
2509 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). | |
2510 </p> | |
229 | 2511 </dd> |
1759 | 2512 <dt class="hdlist1"> |
2513 /screen_refresh | |
2514 </dt> | |
229 | 2515 <dd> |
1759 | 2516 <p> |
2517 Refresh the mcabber screen. | |
2518 </p> | |
229 | 2519 </dd> |
1759 | 2520 <dt class="hdlist1"> |
1842 | 2521 /set [option [= value]] |
1759 | 2522 </dt> |
480 | 2523 <dd> |
1759 | 2524 <p> |
1842 | 2525 Display or set an option value.<br /> |
2526 Without arguments prints a list of all set options with their values | |
1759 | 2527 </p> |
480 | 2528 </dd> |
1759 | 2529 <dt class="hdlist1"> |
2530 /source pattern | |
2531 </dt> | |
2532 <dd> | |
2533 <p> | |
2534 Read configuration files, that match glob pattern (sorted in alphabetical order). | |
2535 </p> | |
2536 </dd> | |
2537 <dt class="hdlist1"> | |
1973 | 2538 /status [online|avail|free|dnd|notavail|away [-|statusmessage]] |
1759 | 2539 </dt> |
2540 <dt class="hdlist1"> | |
2541 /status message -|statusmessage | |
2542 </dt> | |
229 | 2543 <dd> |
1759 | 2544 <p> |
2545 Show or set the current status.<br /> | |
2546 If no status is specified, display the current status.<br /> | |
2547 If a status message is specified, it will overrride the message* variables (these variables can be set in the configuration file).<br /> | |
2548 If no relevant message* variable is set and no status message provided, the current status message is kept.<br /> | |
2549 If StatusMessage is "-", the current status message is cleared.<br /> | |
2550 With the "/status message" command, mcabber will update the message while preserving the status. | |
2551 </p> | |
229 | 2552 </dd> |
1759 | 2553 <dt class="hdlist1"> |
1973 | 2554 /status_to jid online|avail|free|dnd|notavail|away [statusmessage] |
1759 | 2555 </dt> |
2556 <dt class="hdlist1"> | |
2557 /status_to jid message statusmessage | |
2558 </dt> | |
450 | 2559 <dd> |
1759 | 2560 <p> |
2561 Send the requested status to the specified Jabber user.<br /> | |
2562 If the specified jid is ".", the current buddy is used.<br /> | |
2563 Note: this status will be overridden by subsequent "/status" commands. If you are using the auto-away feature, the status will overridden too.<br /> | |
450 | 2564 Note: The jid can include a resource (i.e. user@server/resource). |
1759 | 2565 </p> |
450 | 2566 </dd> |
1759 | 2567 <dt class="hdlist1"> |
2568 /version | |
2569 </dt> | |
2570 <dd> | |
2571 <p> | |
2572 Display current version of mcabber. | |
2573 </p> | |
2574 </dd> | |
2575 </dl></div> | |
2576 </div> | |
2577 <h2 id="_configuration_file">CONFIGURATION FILE</h2> | |
2578 <div class="sectionbody"> | |
2579 <div class="paragraph"><p>See the provided sample configuration file, which should be self-documenting.</p></div> | |
2580 </div> | |
2581 <h2 id="_files">FILES</h2> | |
2582 <div class="sectionbody"> | |
2583 <div class="paragraph"><p>The following files can be used by <tt>mcabber(1)</tt>:</p></div> | |
2584 <div class="literalblock"> | |
2585 <div class="content"> | |
2586 <pre><tt>$HOME/.mcabber/mcabberrc Default configuration file | |
229 | 2587 $HOME/.mcabberrc Configuration file used if no other has been found |
1759 | 2588 $HOME/.mcabber/histo/ Default directory for storing chat history files, if enabled |
2589 /usr/share/mcabber/help/ Default directory for online help files | |
2590 /usr/lib/mcabber/ Default directory for modules</tt></pre> | |
2591 </div></div> | |
2592 </div> | |
2593 <h2 id="_bugs">BUGS</h2> | |
2594 <div class="sectionbody"> | |
2595 <div class="paragraph"><p>Certainly. Please tell me if you find one! :-)<br /> | |
2596 Please visit our website to find out about the MUC room and the bug tracker.</p></div> | |
2597 </div> | |
2598 <h2 id="_author">AUTHOR</h2> | |
2599 <div class="sectionbody"> | |
2600 <div class="paragraph"><p>Written by <a href="mailto:mikael@lilotux.net">Mikael BERTHE</a> and others | |
2601 (see AUTHORS file).<br /></p></div> | |
2602 </div> | |
2603 <h2 id="_resources">RESOURCES</h2> | |
2604 <div class="sectionbody"> | |
1842 | 2605 <div class="paragraph"><p><a href="http://mcabber.com/">Main web site</a><br /> |
2606 <a href="http://wiki.mcabber.com/">Official wiki</a><br /> | |
2607 <a href="xmpp:mcabber@conf.lilotux.net">MCabber MUC room</a></p></div> | |
1759 | 2608 </div> |
2609 <h2 id="_copying">COPYING</h2> | |
2610 <div class="sectionbody"> | |
1973 | 2611 <div class="paragraph"><p>Copyright (C) 2005-2011 Mikael Berthe and others.<br /></p></div> |
1759 | 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> | |
2614 </div> | |
2615 </div> | |
2616 <div id="footnotes"><hr /></div> | |
229 | 2617 <div id="footer"> |
1759 | 2618 <div id="footer-text"> |
1933 | 2619 Version 0.10.2-dev<br /> |
1973 | 2620 Last updated 2011-03-19 13:18:41 CEST |
229 | 2621 </div> |
2622 </div> | |
2623 </body> | |
2624 </html> |