Man pages: Replaced \*(lq and \*(rq with ` and '.

[mmh] / man / mh-alias.man5

diff --git a/man/mh-alias.man5 b/man/mh-alias.man5
index 39609f4..e1e14fc 100644 (file)
--- a/man/mh-alias.man5
+++ b/man/mh-alias.man5
@@ -57,14 +57,14 @@ where:
 Continuation lines in alias files end with `\\' followed by the newline
 character.
 .PP
 Continuation lines in alias files end with `\\' followed by the newline
 character.
 .PP

-.RI \*(lq  Alias\-file \*(rq
+.RI `  Alias\-file '

 and
 and

-.RI \*(lq file \*(rq
+.RI ` file '

 are UNIX file names.
 .I UNIX\-group
 is a group name (or number) from
 .IR /etc/group .
 are UNIX file names.
 .I UNIX\-group
 is a group name (or number) from
 .IR /etc/group .

-An address is a \*(lqsimple\*(rq
+An address is a `simple'

 Internet\-style address.  Througout this file, case is ignored, except
 for file names.
 .PP
 Internet\-style address.  Througout this file, case is ignored, except
 for file names.
 .PP

@@ -100,7 +100,7 @@ added to the
 .I address\-list
 for the alias.
 .PP
 .I address\-list
 for the alias.
 .PP

-In match, a trailing \*(lq*\*(rq on an alias will match just about anything
+In match, a trailing `*' on an alias will match just about anything

 appropriate.  (See example below.)
 .PP
 An approximation of the way aliases are resolved at posting time is
 appropriate.  (See example below.)
 .PP
 An approximation of the way aliases are resolved at posting time is

@@ -116,13 +116,13 @@ If this draft originated on the local host, then for those addresses in
 the message that have no host specified, perform alias resolution.
 .PP
 .IP 3) 3
 the message that have no host specified, perform alias resolution.
 .PP
 .IP 3) 3

-For each line in the alias file, compare \*(lqalias\*(rq against all of
-the existing addresses.  If a match, remove the matched \*(lqalias\*(rq
+For each line in the alias file, compare `alias' against all of
+the existing addresses.  If a match, remove the matched `alias'

 from the address list, and add each new address in the address\-group to
 the address list if it is not already on the list.  The alias itself is
 not usually output, rather the address\-group that the alias maps to is
 from the address list, and add each new address in the address\-group to
 the address list if it is not already on the list.  The alias itself is
 not usually output, rather the address\-group that the alias maps to is

-output instead.  If \*(lqalias\*(rq is terminated with a `;' instead of
-a `:', then both the \*(lqalias\*(rq and the address are output in the
+output instead.  If `alias' is terminated with a `;' instead of
+a `:', then both the `alias' and the address are output in the

 correct format.  (This makes replies possible since personal
 .B nmh
 aliases are unknown to the mail transport system.)
 correct format.  (This makes replies possible since personal
 .B nmh
 aliases are unknown to the mail transport system.)

@@ -149,32 +149,32 @@ news.*: news
 The first line says that more aliases should immediately be read from
 the file
 .IR %etcdir%/MoreAliases .
 The first line says that more aliases should immediately be read from
 the file
 .IR %etcdir%/MoreAliases .

-Following this, \*(lqfred\*(rq
-is defined as an alias for \*(lqfrated@UCI\*(rq, and \*(lqsgroup\*(rq
-is defined as an alias for the three names \*(lqfrated@UCI\*(rq,
-\*(rqfear\*(rq, and \*(rqfreida\*(rq.
+Following this, `fred'
+is defined as an alias for `frated@UCI', and `sgroup'
+is defined as an alias for the three names `frated@UCI',
+'fear', and 'freida'.

 .PP
 .PP

-The alias \*(lqb-people\*(rq is a blind list which includes the addresses
-\*(lqbill\*(rq and \*(lqbetty\*(rq; the message will be delieved to those
-addresses, but the message header will  show only \*(lqBlind List: ;\*(rq
+The alias `b-people' is a blind list which includes the addresses
+`bill' and `betty'; the message will be delieved to those
+addresses, but the message header will  show only `Blind List: ;'

 (not the addresses).
 .PP
 (not the addresses).
 .PP

-Next, the definition of \*(lqUNIX\-committee\*(rq is given by
+Next, the definition of `UNIX\-committee' is given by

 reading the file
 .I unix.aliases
 in the users
 .B mmh
 directory,
 reading the file
 .I unix.aliases
 in the users
 .B mmh
 directory,

-\*(lqstaff\*(rq is defined as all users who are listed as members of the
-group \*(lqstaff\*(rq in the
+`staff' is defined as all users who are listed as members of the
+group `staff' in the

 .I /etc/group
 .I /etc/group

-file, and \*(lqwheels\*(rq
+file, and `wheels'

 is defined as all users whose group\-id in
 .I /etc/passwd
 is defined as all users whose group\-id in
 .I /etc/passwd

-is equivalent to the \*(lqwheel\*(rq group.
+is equivalent to the `wheel' group.

 .PP
 Finally, all aliases of the form
 .PP
 Finally, all aliases of the form

-\*(lqnews.<anything>\*(rq are defined to be \*(lqnews\*(rq.
+`news.<anything>' are defined to be `news'.

 .PP
 The key thing to understand about aliasing in
 .B nmh
 .PP
 The key thing to understand about aliasing in
 .B nmh

@@ -199,7 +199,7 @@ quickly, do the following:
 In your
 .IR .mmh/profile ,
 choose a name for your alias file, say
 In your
 .IR .mmh/profile ,
 choose a name for your alias file, say

-.RI \*(lq aliases \*(rq,
+.RI ` aliases ',

 and add the line:
 .PP
 .RS 5
 and add the line:
 .PP
 .RS 5

@@ -212,14 +212,14 @@ Aliasfile: aliases
 .PP
 .IP 2) 3
 Create the file
 .PP
 .IP 2) 3
 Create the file

-.RI \*(lq aliases \*(rq
+.RI ` aliases '

 in your
 .B mmh
 directory.
 .PP
 .IP 3) 3
 Start adding aliases to your
 in your
 .B mmh
 directory.
 .PP
 .IP 3) 3
 Start adding aliases to your

-.RI \*(lq aliases \*(rq
+.RI ` aliases '

 file as appropriate.
 .RE
 
 file as appropriate.
 .RE
 

@@ -248,7 +248,7 @@ supported in nmh. It is not anymore in mmh.
 Although the forward-referencing semantics of
 .B mh\-alias
 files prevent recursion, the
 Although the forward-referencing semantics of
 .B mh\-alias
 files prevent recursion, the

-.RI \*(lq< " alias\-file" \*(rq
+.RI `< " alias\-file" '

 command may defeat this.
 Since the number of file descriptors is finite (and very limited), such
 infinite recursion will terminate with a meaningless diagnostic when
 command may defeat this.
 Since the number of file descriptors is finite (and very limited), such
 infinite recursion will terminate with a meaningless diagnostic when