Fix a typo in the manual.

[paraslash.git] / web / manual.m4

diff --git a/web/manual.m4 b/web/manual.m4
index 7eecdbb31ad09169666f4d2e353f215432e12961..e665ea7bf99f183ea0a1479386f580cba7feb113 100644 (file)
--- a/web/manual.m4
+++ b/web/manual.m4
@@ -115,6 +115,9 @@ All connections between para_server and para_client are encrypted
 with a symmetric RC4 session key. For each user of paraslash you must
 create a public/secret RSA key pair for authentication.
 
 with a symmetric RC4 session key. For each user of paraslash you must
 create a public/secret RSA key pair for authentication.
 

+If para_client is started without non-option arguments, an interactive
+session (shell) is started. Command history and command completion are
+supported through libreadline.

 
 *para_audiod*
 
 
 *para_audiod*
 


@@ -135,7 +138,8 @@ socket credentials, if available.
 
 The client program which talks to para_audiod. Used to control
 para_audiod, to receive status info, or to grab the stream at any
 
 The client program which talks to para_audiod. Used to control
 para_audiod, to receive status info, or to grab the stream at any

-point of the decoding process.
+point of the decoding process. Like para_client, para_audioc supports
+interactive sessions on systems with libreadline.

 
 *para_recv*
 
 
 *para_recv*
 


@@ -266,6 +270,10 @@ Optional:
        libao). Needed to build the ao writer (ESD, PulseAudio,...).
        Debian package: libao-dev.
 
        libao). Needed to build the ao writer (ESD, PulseAudio,...).
        Debian package: libao-dev.
 

+       - XREFERENCE(http://cnswww.cns.cwru.edu/php/chet/readline/rltop.html,
+       GNU Readline). If this library (libreadline-dev) is installed,
+       para_client and para_audioc support interactive sessions.
+

 Installation
 ~~~~~~~~~~~~
 
 Installation
 ~~~~~~~~~~~~
 


@@ -486,7 +494,7 @@ including ssh and gpg. An RSA key consists in fact of two keys,
 called the public key and the private key. A message can be encrypted
 with either key and only the counterpart of that key can decrypt
 the message. While RSA can be used for both signing and encrypting
 called the public key and the private key. A message can be encrypted
 with either key and only the counterpart of that key can decrypt
 the message. While RSA can be used for both signing and encrypting

-a message, paraslash only uses RSA only for the latter purpose. The
+a message, paraslash uses RSA only for the latter purpose. The

 RSA public key encryption and signatures algorithms are defined in
 detail in RFC 2437.
 
 RSA public key encryption and signatures algorithms are defined in
 detail in RFC 2437.