diff options
| author | Dmitri Vereshchagin <dmitri.vereshchagin@gmail.com> | 2024-01-31 20:47:13 +0300 |
|---|---|---|
| committer | Dan Cross <crossd@gmail.com> | 2025-07-27 09:58:50 -0400 |
| commit | 10564b11755ff2d48d0f5073c46571e806fa6fb4 (patch) | |
| tree | 229252742051d83558fff2352642d0f57ba66615 /man/man9 | |
| parent | 00446db7d8fdb3ea56fa104643b34823960f7be2 (diff) | |
| download | plan9port-10564b11755ff2d48d0f5073c46571e806fa6fb4.tar.gz plan9port-10564b11755ff2d48d0f5073c46571e806fa6fb4.zip | |
tmac/tmac.an: define .MR in a groff compatible way
groff 1.23.0 added .MR to its -man macro package. The NEWS file states
that the inclusion of the macro "was prompted by its introduction to
Plan 9 from User Space's troff in August 2020." From d32deab it seems
that the name for Plan 9 from User Space's implementation was suggested
by groff maintainer G. Brandon Robinson.
Not sure if the intention was to make these definitions compatible, but
it would be nice if they were.
Currently, Plan 9 from User Space's .MR expects its second argument to
be parenthesized. groff's .MR does not. This results in extra
parentheses appearing in manual references when viewing Plan 9 from User
Space's manual pages on a system using groff.
Diffstat (limited to 'man/man9')
| -rw-r--r-- | man/man9/0intro.9p | 18 | ||||
| -rw-r--r-- | man/man9/attach.9p | 4 | ||||
| -rw-r--r-- | man/man9/clunk.9p | 2 | ||||
| -rw-r--r-- | man/man9/flush.9p | 4 | ||||
| -rw-r--r-- | man/man9/open.9p | 4 | ||||
| -rw-r--r-- | man/man9/openfd.9p | 8 | ||||
| -rw-r--r-- | man/man9/read.9p | 2 | ||||
| -rw-r--r-- | man/man9/remove.9p | 2 | ||||
| -rw-r--r-- | man/man9/stat.9p | 4 | ||||
| -rw-r--r-- | man/man9/version.9p | 2 | ||||
| -rw-r--r-- | man/man9/walk.9p | 4 |
11 files changed, 27 insertions, 27 deletions
diff --git a/man/man9/0intro.9p b/man/man9/0intro.9p index 30e153a1..0b94701f 100644 --- a/man/man9/0intro.9p +++ b/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 -.MR plumber (4) +.MR 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 -.MR utf (7) ). +.MR 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; -.MR fcall (3) +.MR 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 -.MR stat (3) +.MR 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 -.MR 9pclient (3) +.MR 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 -.MR stat (3) ). +.MR 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 -.MR getns (3) +.MR getns 3 and -.MR 9pserve (4) ). +.MR 9pserve 4 ). Clients connect to these servers using a 9P client library (see -.MR 9pclient (3) ). +.MR 9pclient 3 ). .SH DIRECTORIES Directories are created by .B create diff --git a/man/man9/attach.9p b/man/man9/attach.9p index 4160f30d..fe477f2a 100644 --- a/man/man9/attach.9p +++ b/man/man9/attach.9p @@ -122,7 +122,7 @@ and and .I fsauth (see -.MR 9pclient (3) ) +.MR 9pclient 3 ) generate .B attach and @@ -163,6 +163,6 @@ transactions. .\" .B mount .\" system call on an uninitialized connection. .SH SEE ALSO -.MR 9pclient (3) , +.MR 9pclient 3 , .IR version (9P), Plan 9's \fIauthsrv\fR(6) diff --git a/man/man9/clunk.9p b/man/man9/clunk.9p index f014ac42..059b1317 100644 --- a/man/man9/clunk.9p +++ b/man/man9/clunk.9p @@ -41,7 +41,7 @@ generated by and .I fsunmount (see -.MR 9pclient (3) ) +.MR 9pclient 3 ) and indirectly by other actions such as failed .I fsopen calls. diff --git a/man/man9/flush.9p b/man/man9/flush.9p index 862ab9a4..3ccc7f83 100644 --- a/man/man9/flush.9p +++ b/man/man9/flush.9p @@ -99,11 +99,11 @@ flushing a and flushing an invalid tag. .SH ENTRY POINTS The -.MR 9pclient (3) +.MR 9pclient 3 library does not generate .B flush transactions.. -.MR 9pserve (4) +.MR 9pserve 4 generates .B flush transactions to cancel transactions pending when a client hangs up. diff --git a/man/man9/open.9p b/man/man9/open.9p index 8a54f72c..7d016ae9 100644 --- a/man/man9/open.9p +++ b/man/man9/open.9p @@ -160,7 +160,7 @@ in this case, the .I fscreate call (see -.MR 9pclient (3) ) +.MR 9pclient 3 ) uses .B open with truncation. @@ -209,7 +209,7 @@ again. and .I fscreate (see -.MR 9pclient (3) ) +.MR 9pclient 3 ) both generate .B open messages; only diff --git a/man/man9/openfd.9p b/man/man9/openfd.9p index 620b1991..18fb2149 100644 --- a/man/man9/openfd.9p +++ b/man/man9/openfd.9p @@ -43,18 +43,18 @@ it cannot be .PP .I Openfd is implemented by -.MR 9pserve (4) . +.MR 9pserve 4 . 9P servers that post their services using -.MR 9pserve (4) +.MR 9pserve 4 (or indirectly via -.MR post9pservice (3) ) +.MR post9pservice 3 ) will never see a .B Topenfd message. .SH ENTRY POINTS .I Fsopenfd (see -.MR 9pclient (3) ) +.MR 9pclient 3 ) generates an .B openfd message. diff --git a/man/man9/read.9p b/man/man9/read.9p index 675bb773..613d5dad 100644 --- a/man/man9/read.9p +++ b/man/man9/read.9p @@ -114,7 +114,7 @@ to be transferred atomically. and .I fswrite (see -.MR 9pclient (3) ) +.MR 9pclient 3 ) generate the corresponding messages. Because they take an offset parameter, the .I fspread diff --git a/man/man9/remove.9p b/man/man9/remove.9p index 232c88f6..d62b5bab 100644 --- a/man/man9/remove.9p +++ b/man/man9/remove.9p @@ -45,7 +45,7 @@ so other fids typically remain usable. .SH ENTRY POINTS .I Fsremove (see -.MR 9pclient (3) ) +.MR 9pclient 3 ) generates .B remove messages. diff --git a/man/man9/stat.9p b/man/man9/stat.9p index 7706d3eb..c86438d7 100644 --- a/man/man9/stat.9p +++ b/man/man9/stat.9p @@ -88,7 +88,7 @@ The and .I convD2M routines (see -.MR fcall (3) ) +.MR 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 -.MR 9pclient (3) ). +.MR 9pclient 3 ). .PP .B Wstat messages are generated by diff --git a/man/man9/version.9p b/man/man9/version.9p index c71ee556..072dbad3 100644 --- a/man/man9/version.9p +++ b/man/man9/version.9p @@ -91,7 +91,7 @@ requests is called a .SH ENTRY POINTS .I Fsversion (see -.MR 9pclient (3) ) +.MR 9pclient 3 ) generates .B version messages; diff --git a/man/man9/walk.9p b/man/man9/walk.9p index 735b7dcb..746adbc3 100644 --- a/man/man9/walk.9p +++ b/man/man9/walk.9p @@ -149,13 +149,13 @@ may be packed in a single message. This constant is called .B MAXWELEM in -.MR fcall (3) . +.MR 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 -.MR 9pclient (3) ) +.MR 9pclient 3 ) generates walk messages. One or more walk messages may be generated by any call that evaluates file names: |
