tmac: introduce real manual reference macro instead of overloading IR

The overloading of IR emits magic \X'...' sequences that turn into HTML manual links.
But not all such IR invocations should be manual links;
those had to be written to avoid the IR macro before.
Worse, the \X'...' ending the IR causes troff to emit only a single space after a period.

Defining a new IM macro for manual references fixes both problems.

Fixes #441.

man/man9/0intro.9p

@@ -21,7 +21,7 @@ such a machine is called, somewhat confusingly, a
 Another possibility for a server is to synthesize
 files on demand, perhaps based on information on data structures
 maintained in memory; the
-.IR plumber (4)
+.IM plumber (4)
 server is an example of such a server.
 .PP
 A
@@ -63,7 +63,7 @@ bytes of data.
 Text strings are represented this way,
 with the text itself stored as a UTF-8
 encoded sequence of Unicode characters (see
-.IR utf (7)).
+.IM utf (7) ).
 Text strings in 9P messages are not
 .SM NUL\c
 -terminated:
@@ -114,7 +114,7 @@ Plan 9 names may contain any printable character (that is, any character
 outside hexadecimal 00-1F and 80-9F)
 except slash.)
 Messages are transported in byte form to allow for machine independence;
-.IR fcall (3)
+.IM fcall (3)
 describes routines that convert to and from this form into a machine-dependent
 C structure.
 .SH MESSAGES
@@ -348,7 +348,7 @@ a ``current file'' on the server.
 Fids are somewhat like file descriptors in a user process,
 but they are not restricted to files open for I/O:
 directories being examined, files being accessed by
-.IR stat (3)
+.IM stat (3)
 calls, and so on \(em all files being manipulated by the operating
 system \(em are identified by fids.
 Fids are chosen by the client.
@@ -461,7 +461,7 @@ to have their input or output attached to fids on 9P servers.
 See
 .IR openfd (9p)
 and
-.IR 9pclient (3)
+.IM 9pclient (3)
 for details.
 .PP
 The
@@ -475,7 +475,7 @@ access permissions (read, write and execute for owner, group and public),
 access and modification times, and
 owner and group identifications
 (see
-.IR stat (3)).
+.IM stat (3) ).
 The owner and group identifications are textual names.
 The
 .B wstat
@@ -523,12 +523,12 @@ into 9P messages.
 .SS Unix
 On Unix, 9P services are posted as Unix domain sockets in a
 well-known directory (see
-.IR getns (3)
+.IM getns (3)
 and
-.IR 9pserve (4)).
+.IM 9pserve (4) ).
 Clients connect to these servers using a 9P client library
 (see
-.IR 9pclient (3)).
+.IM 9pclient (3) ).
 .SH DIRECTORIES
 Directories are created by
 .B create

man/man9/attach.9p

@@ -122,7 +122,7 @@ and
 and
 .I fsauth
 (see
-.IR 9pclient (3))
+.IM 9pclient (3) )
 generate
 .B attach
 and
@@ -163,6 +163,6 @@ transactions.
 .\" .B mount
 .\" system call on an uninitialized connection.
 .SH SEE ALSO
-.IR 9pclient (3),
+.IM 9pclient (3) ,
 .IR version (9P),
 Plan 9's \fIauthsrv\fR(6)

man/man9/clunk.9p

@@ -41,7 +41,7 @@ generated by
 and
 .I fsunmount
 (see
-.IR 9pclient (3))
+.IM 9pclient (3) )
 and indirectly by other actions such as failed
 .I fsopen
 calls.

man/man9/flush.9p

@@ -99,11 +99,11 @@ flushing a
 and flushing an invalid tag.
 .SH ENTRY POINTS
 The
-.IR 9pclient (3)
+.IM 9pclient (3)
 library does not generate
 .B flush
 transactions..
-.IR 9pserve (4)
+.IM 9pserve (4)
 generates
 .B flush
 transactions to cancel transactions pending when a client hangs up.

man/man9/open.9p

@@ -160,7 +160,7 @@ in this case, the
 .I fscreate
 call
 (see
-.IR 9pclient (3))
+.IM 9pclient (3) )
 uses
 .B open
 with truncation.
@@ -209,7 +209,7 @@ again.
 and
 .I fscreate
 (see
-.IR 9pclient (3))
+.IM 9pclient (3) )
 both generate
 .B open
 messages; only

man/man9/openfd.9p

@@ -43,18 +43,18 @@ it cannot be
 .PP
 .I Openfd
 is implemented by
-.IR 9pserve (4).
+.IM 9pserve (4) .
 9P servers that post their services using
-.IR 9pserve (4)
+.IM 9pserve (4)
 (or indirectly via
-.IR post9pservice (3))
+.IM post9pservice (3) )
 will never see a
 .B Topenfd
 message.
 .SH ENTRY POINTS
 .I Fsopenfd
 (see
-.IR 9pclient (3))
+.IM 9pclient (3) )
 generates an
 .B openfd
 message.

man/man9/read.9p

@@ -114,7 +114,7 @@ to be transferred atomically.
 and
 .I fswrite
 (see
-.IR 9pclient (3))
+.IM 9pclient (3) )
 generate the corresponding messages.
 Because they take an offset parameter, the
 .I fspread

man/man9/remove.9p

@@ -45,7 +45,7 @@ so other fids typically remain usable.
 .SH ENTRY POINTS
 .I Fsremove
 (see
-.IR 9pclient (3))
+.IM 9pclient (3) )
 generates
 .B remove
 messages.

man/man9/stat.9p

@@ -88,7 +88,7 @@ The
 and
 .I convD2M
 routines (see
-.IR fcall (3))
+.IM fcall (3) )
 convert between directory entries and a C structure called a
 .BR Dir .
 .PP
@@ -263,7 +263,7 @@ messages are generated by
 and
 .IR fsdirstat
 (see
-.IR 9pclient (3)).
+.IM 9pclient (3) ).
 .PP
 .B Wstat
 messages are generated by

man/man9/version.9p

@@ -91,7 +91,7 @@ requests is called a
 .SH ENTRY POINTS
 .I Fsversion
 (see
-.IR 9pclient (3))
+.IM 9pclient (3) )
 generates
 .B version
 messages;

man/man9/walk.9p

@@ -149,13 +149,13 @@ may be packed in a single message.
 This constant is called
 .B MAXWELEM
 in
-.IR fcall (3).
+.IM fcall (3) .
 Despite this restriction, the system imposes no limit on the number of elements in a file name,
 only the number that may be transmitted in a single message.
 .SH ENTRY POINTS
 .I Fswalk
 (see
-.IR 9pclient (3))
+.IM 9pclient (3) )
 generates walk messages.
 One or more walk messages may be generated by
 any call that evaluates file names: