(@asynclink, @asyncdlink): New macros. Use them instead of @link

	where appropriate.
(Asynchronous Messages): Use @reqlink instead of @req.

doc/Protocol-A.texi

@@ -3,9 +3,8 @@
 @c FIXME: Explain how the garb works with nice and keep-commented
 @c FIXME: @i{Example:} is only used in front of some examples.
 @c FIXME: Make all types clickable in HTML (and info?)
-@c FIXME: create @asynklink and @asyncdlink, and substitute them for @async.
 @c
-@c $Id: Protocol-A.texi,v 1.120 2001/04/30 21:46:19 ceder Exp $
+@c $Id: Protocol-A.texi,v 1.121 2001/04/30 22:00:10 ceder Exp $
 @c %**start of header
 @setfilename protocol-a.info
 @settitle LysKOM Protocol A
@@ -97,6 +96,63 @@
 @code{\n\}
 @end macro
 
+@c @asynclink{async-login} is used for async names, that shuld be linked.
+
+@ifhtml
+@macro asynclink {n}
+@code{@ref{\n\}}
+@end macro
+@end ifhtml
+
+@ifnothtml
+@macro asynclink {n}
+@code{\n\} (@pxref{\n\})
+@end macro
+@end ifnothtml
+
+@c @asyncdlink{async-login}...@linkhere{} is used for async messages,
+@c that shuld be linked, where the link should occur a few words after
+@c the async name itself.
+
+@ifhtml
+
+@c HTML version: make the word a link.
+@macro asyncdlink {n}
+@code{@ref{\n\}}@c
+@unmacro linkhere
+@macro linkhere
+@end macro
+@end macro
+
+@end ifhtml
+
+@ifnothtml
+@ifnottex
+
+@c Info version: create linkhere as a macro that contains a reference.
+
+@macro asyncdlink {n}
+@code{\n\}@c
+@unmacro linkhere
+@macro linkhere
+(@pxref{\n\})
+@end macro
+@end macro
+@end ifnottex
+
+@iftex
+
+@c TeX version: this produces output similar to the Info version.
+
+@tex
+    \gdef\asyncdlink#1{%
+        \code{#1}%
+        \gdef\linkhere{ (\pxref{#1})}%
+    }
+@end tex
+@end iftex
+@end ifnothtml
+
 @c @type{Conference} is used for LysKOM types.
 @macro type {n}
 @code{\n\}
@@ -8042,7 +8098,7 @@ messages they want.  Servers are encouraged to preselect the
 @async{async-sync-db}, @async{async-leave-conf}, @async{async-login},
 @async{async-rejected-connection}, @async{async-send-message} and
 @async{async-logout} messages. These correspond to the useful messages
-that were sent prior to the introduction of @req{accept-async}.
+that were sent prior to the introduction of @reqlink{accept-async}.
 
 An asynchronous message is sent as a colon immediately followed by the
 number of message parameters, the message number and the message
@@ -8107,7 +8163,7 @@ In protocol version 10 this call has been superceded by @ref{async-new-text}.
 @end example
 
 This message was sent when @aarg{person} logged off. It has been
-replaced by @async{async-logout}, since this asynchronous message
+replaced by @asynclink{async-logout}, since this asynchronous message
 could not differentiate between sessions if the same person was logged
 in more than once.
 
@@ -8128,7 +8184,7 @@ This message was sent when @aarg{person} changed his
 @code{what-i-am-doing} string to @aarg{what-am-i-doing} or his working
 conference to @aarg{conference}. 
 
-It has been replaced by call number 6, @async{async-i-am-on}, since
+It has been replaced by call number 6, @asynclink{async-i-am-on}, since
 this asynchronous message could not differentiate between sessions if
 the same person was logged in more than once.
 
@@ -8237,8 +8293,8 @@ logging in is sent in @aarg{pers-no}, and the session number in
                                 message   :   HOLLERITH ));
 @end example
 
-This message has been superceded by @async{async-send-message} which
-is more flexible. It used to be sent when the administrator
+This message has been superceded by @asyncdlink{async-send-message} which
+is more flexible@linkhere{}. It used to be sent when the administrator
 (@aarg{sender}) broadcasted a string (@aarg{message}) to all LysKOM
 users, but is no longer used.