gui: Don't exit without shutting down curses on config reload.

[paraslash.git] / ggo / dccp_recv.ggo

diff --git a/ggo/dccp_recv.ggo b/ggo/dccp_recv.ggo
index 2c7f364ca7f296f7bbbcf175aa9fd79d39b3651b..80d312338b8811a48b3a9ac1da7c1fa888e0be40 100644 (file)
--- a/ggo/dccp_recv.ggo
+++ b/ggo/dccp_recv.ggo
@@ -24,18 +24,14 @@ optional multiple(-10)
 # - CCID-248 ... CCID-254 are experimental (RFC 4340, 19.5)
 values="2", "3", "4", "248", "249", "250", "251", "252", "253", "254"
 details="
-       Depends on the CCIDs available on the server; this information
-       can be seen in the display of 'para_client si'.
+       When present exactly once, this option mandates the CCID for the
+       sender-receiver connection. If it is passed more than once, it sets
+       a preference list where the order of appearance signifies descending
+       priority. For example, passing 4, 2, 3 creates the preference list
+       (CCID-4, CCID-2, CCID-3), assigning CCID-4 highest preference.
 
-       When present exactly once, this option mandates the CCID
-       to use for the sender-receiver connection.
+       The request is reconciled with the CCIDs on the server through the
+       'server-priority' mechanism of RFC 4340 6.3.1/10. The server CCIDs
+       can be listed by calling 'para_client si'.
 
-       If it is passed more than once, it sets a preference list
-       of CCIDs for this connection. The order of appearance here
-       signifies descending priority. For example,
-                   --ccid 4   --c 2   --ccid 3
-       generates the preference list (CCID-4, CCID-2, CCID-3).
-
-       The request is reconciled with the CCIDs on the server via
-       the 'server-priority' mechanism of RFC 4340 6.3.1/10.
 "