On Sun, Feb 16, 2020 at 09:25:51PM +0100, Klemens Nanni wrote:
> Going through the example with bgpd.conf(5) side by side, jumping to the
> "group" tag shows
> 
>       group descr  Neighbors in this group will be matched.
>       AS as-number
>                    Neighbors with this AS will be matched.
>       ...
> 
> which is somewhere in the manual that assumes knowing what groups are.
> mdoc's automatic tagging failed here, so markup `Ic group' in proper
> section:
> 
>       NEIGHBORS AND GROUPS
>            bgpd(8) establishes TCP connections to other BGP speakers called
>            neighbors.  A neighbor and its properties are specified by a 
> neighbor
>            section:
> 
>            neighbor 10.0.0.2 {
>                    remote-as 65002
>                    descr "a neighbor"
>            }
> 
>            Neighbors placed within a group section inherit the properties 
> common to
>            that group:
>            ...
> 
> This makes typing ":tgroup<Enter>" jump to that very last sentence.
Same for `neighbor' in the very same section as well.

OK?


Index: bgpd.conf.5
===================================================================
RCS file: /cvs/src/usr.sbin/bgpd/bgpd.conf.5,v
retrieving revision 1.200
diff -u -p -r1.200 bgpd.conf.5
--- bgpd.conf.5 9 Feb 2020 14:21:26 -0000       1.200
+++ bgpd.conf.5 16 Feb 2020 20:31:46 -0000
@@ -683,6 +683,7 @@ can be chosen by the local operator.
 establishes TCP connections to other BGP speakers called
 .Em neighbors .
 A neighbor and its properties are specified by a
+.Tg neighbor
 .Ic neighbor
 section:
 .Bd -literal -offset indent
@@ -693,6 +694,7 @@ neighbor 10.0.0.2 {
 .Ed
 .Pp
 Neighbors placed within a
+.Tg group
 .Ic group
 section inherit the properties common to that group:
 .Bd -literal -offset indent

Reply via email to