mcabber: mcabber/doc/mcabber.1.html comparison

comparison mcabber/doc/mcabber.1.html @ 1842:cec7cbeb1c2e

Update manpage

author	Mikael Berthe <mikael@lilotux.net>
date	Sun, 28 Mar 2010 11:55:34 +0200
parents	921429804e20
children	41699679b121

comparison

equal deleted inserted replaced

-:8ad982f83fd6
+:cec7cbeb1c2e
 <div class="paragraph"><p>Additional key bindings may be specified using the <em>/bind</em> command described
 in the COMMANDS section.</p></div>
 </div>
 <h2 id="_mcabber_8217_s_roster">MCABBER&#8217;S ROSTER</h2>
 <div class="sectionbody">
-<div class="paragraph"><p>The first listed resource on the roster is <em>[status]</em>, which keeps a log of
+<div class="paragraph"><p>The first listed item on the roster is <em>[status]</em>, which keeps a log of
 everything that appears in the short log window below the main chat area.
 While the log window was designed for showing the latest few elements, the
 dedicated <em>[status]</em> buffer allows more comfortable viewing of the log, as
 well as scrolling it in a standard manner.</p></div>
-<div class="paragraph"><p>Group names are displayed above the resources that are within them, and are
+<div class="paragraph"><p>Group names are displayed above the items that are within them, and are
 indicated by <em>---</em> to the left of the name.</p></div>
-<div class="paragraph"><p>For every real Jabber resource, the roster displays four pieces of information:
+<div class="paragraph"><p>For every real Jabber contact, the roster displays four pieces of information:
-the resource&#8217;s name or alias, its online status, its authorization status, and
+the buddy&#8217;s name or alias, its online status, its authorization status, and
-whether there are unread messages from the resource waiting for you.</p></div>
+whether there are unread messages from the buddy waiting for you.</p></div>
 <div class="paragraph"><p>The online status is one of the following:</p></div>
 <div class="dlist"><dl>
 <dt class="hdlist1">
 <em>o</em>
 </dt>
 <dt class="hdlist1">
 <em>?</em>
 </dt>
 <dd>
 <p>
-unknown, usually meaning you are not authorized to see this resource&#8217;s status
+unknown, usually meaning you are not authorized to see this buddy&#8217;s status
 </p>
 </dd>
 <dt class="hdlist1">
 <em>x</em>
 </dt>
 <p>
 a conference room in which you are participating
 </p>
 </dd>
 </dl></div>
-<div class="paragraph"><p>The authorization status indicates whether a resource is authorized to receive
+<div class="paragraph"><p>The authorization status indicates whether a buddy is authorized to receive
 your online status updates, and is displayed by the brackets surrounding the
-resource&#8217;s online status.  Square brackets, like <em>[o]</em>, indicate that this
+buddy&#8217;s online status.  Square brackets, like <em>[o]</em>, indicate that this
-resource is authorized to receive your status.  Curly braces, like <em>{o}</em>,
+buddy is authorized to receive your status.  Curly braces, like <em>{o}</em>,
 indicate that they are not authorized to receive your status.</p></div>
-<div class="paragraph"><p>When there are unread messages from the resource which you have not looked at,
+<div class="paragraph"><p>When there are unread messages from a buddy which you have not looked at,
 a hash mark (<em>#</em>) appears in the leftmost section of the roster for that
-resource.  The hash mark disappears once you view that resource&#8217;s message log.</p></div>
+buddy.  The hash mark disappears once you view that buddy&#8217;s message
+buffer.
+When the user attention is requested (or when you receive a message containing
+your nickname in a MUC room), the hash mark is replaced with the <em>attention
+sign</em>, an exclamation mark (<em>!</em>).</p></div>
 <div class="paragraph"><p>Examples:</p></div>
 <div class="dlist"><dl>
 <dt class="hdlist1">
-<em>--- Buds</em>
+' --- Buds'
 </dt>
 <dd>
 <p>
 This is a group named <em>Buds</em>
 </p>
 <p>
 John is online, can see your status, and sent you a message that you did not read yet
 </p>
 </dd>
 <dt class="hdlist1">
-<em>{?} Sally</em>
+<em> {?} Sally</em>
 </dt>
 <dd>
 <p>
 Neither you nor Sally have authorized each other to see your online status
 </p>
 </dd>
 <dt class="hdlist1">
-<em>{a} Jane</em>
+<em> {a} Jane</em>
 </dt>
 <dd>
 <p>
 Jane is away, but she cannot see your online status
 </p>
 <dt class="hdlist1">
 /buffer save filename
 </dt>
 <dd>
 <p>
-Buddy&#8217;s buffer manipulation command.  Eg. you can search through buffer for "text", clear chat window etc.
+Buddy&#8217;s buffer manipulation command.  E.g. you can search through buffer for "text", clear chat window etc.
 </p>
 <div class="dlist"><dl>
 <dt class="hdlist1">
 <em>clear</em>
 </dt>
 <dt class="hdlist1">
 <em>roster</em> clear
 </dt>
 <dd>
 <p>
-Remove all color rules for the roster. All roster items will get its default color.
+Remove all color rules for the roster.  All roster items will get its default color.
 </p>
 </dd>
 <dt class="hdlist1">
 <em>roster</em> status wildcard color
 </dt>
 <dd>
 <p>
-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.
+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.
 </p>
 </dd>
 <dt class="hdlist1">
 <em>mucnick</em> nick (color|-)
 </dt>
 <dd>
 <p>
-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.
+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.
 </p>
 </dd>
 <dt class="hdlist1">
 <em>muc</em> (jid|.|*) [on|preset|off|-]
 </dt>
 <dd>
 <p>
-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>.
+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>.
 </p>
 </dd>
 </dl></div>
 </dd>
 <dt class="hdlist1">
 </dt>
 <dd>
 <p>
 Tell mcabber what to do about pending events.<br />
 If the first parameter is <em>*</em>, the command will apply to all queued events.<br />
-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.
+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.
 </p>
 <div class="dlist"><dl>
 <dt class="hdlist1">
 #N|* accept [event-specific arguments]
 </dt>
 <dt class="hdlist1">
 <em>load</em> [-f] module
 </dt>
 <dd>
 <p>
-Loads specified module. If -f flag is specified, most of module loading errors will be ignored.
+Loads specified module.  If -f flag is specified, most of module loading errors will be ignored.
 </p>
 </dd>
 <dt class="hdlist1">
 <em>unload</em> [-f] module
 </dt>
 <dd>
 <p>
-Unloads specified module. Note: The force flag will not remove any dependent on this modules!
+Unloads specified module. Note: The force flag will not remove any dependency on this module!
 </p>
 </dd>
 <dt class="hdlist1">
 <em>info</em> module
 </dt>
 <dt class="hdlist1">
 <em>fingerprint</em> [jid [fpr]]
 </dt>
 <dd>
 <p>
-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.
+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.
 </p>
 </dd>
 <dt class="hdlist1">
 <em>smpq</em> [jid] secret
 </dt>
 <dt class="hdlist1">
 (<em>default</em>|<em>jid</em>) (plain|manual|opportunistic|always)
 </dt>
 <dd>
 <p>
-Sets either the default policy or the policy for the given jid The plain policy should never be used, because you won&#8217;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&#8217;ll be able to read the message but it won&#8217;t be saved to the history.
+Sets either the default policy or the policy for the given jid The plain policy should never be used, because you won&#8217;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&#8217;ll be able to read the message but it won&#8217;t be saved to the history.
 </p>
 </dd>
 </dl></div>
 </dd>
 <dt class="hdlist1">
 /say [-n|-h|--] text
 </dt>
 <dd>
 <p>
 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 />
-The "-n" flag turns the message to "normal" type, "-h" to "headline". "--" can be used to send chat message beginning with -n or -h.
+The "-n" flag turns the message to "normal" type, "-h" to "headline".  "--" can be used to send chat message beginning with -n or -h.
 </p>
 </dd>
 <dt class="hdlist1">
 /say_to [-n|-h] [-q] [-f file] jid text
 </dt>
 <p>
 Refresh the mcabber screen.
 </p>
 </dd>
 <dt class="hdlist1">
-/set option [= value]
+/set [option [= value]]
 </dt>
 <dd>
 <p>
-Display or set an option value.
+Display or set an option value.<br />
+Without arguments prints a list of all set options with their values
 </p>
 </dd>
 <dt class="hdlist1">
 /source pattern
 </dt>
 <div class="paragraph"><p>Written by <a href="mailto:mikael@lilotux.net">Mikael BERTHE</a> and others
 (see AUTHORS file).<br /></p></div>
 </div>
 <h2 id="_resources">RESOURCES</h2>
 <div class="sectionbody">
-<div class="paragraph"><p><a href="http://mcabber.com/">Main web site</a></p></div>
+<div class="paragraph"><p><a href="http://mcabber.com/">Main web site</a><br />
+<a href="http://wiki.mcabber.com/">Official wiki</a><br />
+<a href="xmpp:mcabber@conf.lilotux.net">MCabber MUC room</a></p></div>
 </div>
 <h2 id="_copying">COPYING</h2>
 <div class="sectionbody">
 <div class="paragraph"><p>Copyright (C) 2005-2010 Mikael Berthe and others.<br /></p></div>
 <div class="paragraph"><p>Free use of this software is granted under the terms of the GNU General Public
 </div>
 <div id="footnotes"><hr /></div>
 <div id="footer">
 <div id="footer-text">
 Version 0.10.0-dev<br />
-Last updated 2010-03-13 17:43:30 CEST
+Last updated 2010-03-28 11:48:11 CEST
 </div>
 </div>
 </body>
 </html>

Mercurial > ~mikael > mcabber > hg

comparison mcabber/doc/mcabber.1.html @ 1842:cec7cbeb1c2e