ctags.1: Xr vgrind

classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|

ctags.1: Xr vgrind

Klemens Nanni-2
This tool comes from the textproc/vgrind port so base does not have it,
is that the reason we do not reference it?

I think it is still useful, so here's the Xr addition.

Feedback? OK?

Index: ctags.1
===================================================================
RCS file: /cvs/src/usr.bin/ctags/ctags.1,v
retrieving revision 1.33
diff -u -p -r1.33 ctags.1
--- ctags.1 31 Dec 2015 14:01:26 -0000 1.33
+++ ctags.1 15 Jul 2019 14:50:43 -0000
@@ -92,7 +92,8 @@ file; that is, all
 references to them are regenerated, keeping only the other values in the
 file.
 .It Fl v
-An index of the form expected by vgrind
+An index of the form expected by
+.Xr vgrind 1
 is produced on the standard output.
 This listing contains the object name, file name, and page number (assuming
 64 line pages).
@@ -171,6 +172,7 @@ default output tags file
 Duplicate objects are not considered errors.
 .Sh SEE ALSO
 .Xr mg 1 ,
+.Xr vgrind 1 ,
 .Xr vi 1
 .Sh STANDARDS
 The

Reply | Threaded
Open this post in threaded view
|

Re: ctags.1: Xr vgrind

Jason McIntyre-2
On Mon, Jul 15, 2019 at 04:56:29PM +0200, Klemens Nanni wrote:
> This tool comes from the textproc/vgrind port so base does not have it,
> is that the reason we do not reference it?
>
> I think it is still useful, so here's the Xr addition.
>
> Feedback? OK?
>

hi.

we pretty much try to keep xrs only to base pages in base pages. yes,
there are exceptions, but they are few and far between. i'm not keen to
start adding xrs to pages other people don;t have.

jmc

> Index: ctags.1
> ===================================================================
> RCS file: /cvs/src/usr.bin/ctags/ctags.1,v
> retrieving revision 1.33
> diff -u -p -r1.33 ctags.1
> --- ctags.1 31 Dec 2015 14:01:26 -0000 1.33
> +++ ctags.1 15 Jul 2019 14:50:43 -0000
> @@ -92,7 +92,8 @@ file; that is, all
>  references to them are regenerated, keeping only the other values in the
>  file.
>  .It Fl v
> -An index of the form expected by vgrind
> +An index of the form expected by
> +.Xr vgrind 1
>  is produced on the standard output.
>  This listing contains the object name, file name, and page number (assuming
>  64 line pages).
> @@ -171,6 +172,7 @@ default output tags file
>  Duplicate objects are not considered errors.
>  .Sh SEE ALSO
>  .Xr mg 1 ,
> +.Xr vgrind 1 ,
>  .Xr vi 1
>  .Sh STANDARDS
>  The
>

Reply | Threaded
Open this post in threaded view
|

Re: ctags.1: Xr vgrind

Ingo Schwarze
Hi,

Jason McIntyre wrote on Mon, Jul 15, 2019 at 06:43:09PM +0100:
> On Mon, Jul 15, 2019 at 04:56:29PM +0200, Klemens Nanni wrote:

>> This tool comes from the textproc/vgrind port so base does not have it,
>> is that the reason we do not reference it?
>>
>> I think it is still useful, so here's the Xr addition.

> we pretty much try to keep xrs only to base pages in base pages.
> yes, there are exceptions, but they are few and far between.
> i'm not keen to start adding xrs to pages other people don;t have.

I tend to agree with Jason; besides, it would also cause dead
hyperlinks on man.openbsd.org.

The following may be useful, though.  This kind of reference occurs
rarely enough that i'm not sure whether we have a standard wording
for it.

Yours,
  Ingo


Index: ctags.1
===================================================================
RCS file: /cvs/src/usr.bin/ctags/ctags.1,v
retrieving revision 1.33
diff -u -p -r1.33 ctags.1
--- ctags.1 31 Dec 2015 14:01:26 -0000 1.33
+++ ctags.1 15 Jul 2019 19:33:36 -0000
@@ -171,7 +171,8 @@ default output tags file
 Duplicate objects are not considered errors.
 .Sh SEE ALSO
 .Xr mg 1 ,
-.Xr vi 1
+.Xr vi 1 ,
+and the textproc/vgrind port
 .Sh STANDARDS
 The
 .Nm

Reply | Threaded
Open this post in threaded view
|

Re: ctags.1: Xr vgrind

Klemens Nanni-2
On Mon, Jul 15, 2019 at 09:35:26PM +0200, Ingo Schwarze wrote:
> I tend to agree with Jason; besides, it would also cause dead
> hyperlinks on man.openbsd.org.
Sure, never providing broken links is absoloutely reasonable.

> The following may be useful, though.  This kind of reference occurs
> rarely enough that i'm not sure whether we have a standard wording
> for it.
Fine with me as it turns the implicit mentioning into an explicit
reference.

Thanks.

Reply | Threaded
Open this post in threaded view
|

Re: ctags.1: Xr vgrind

Jason McIntyre-2
In reply to this post by Ingo Schwarze
On Mon, Jul 15, 2019 at 09:35:26PM +0200, Ingo Schwarze wrote:

> Hi,
>
> Jason McIntyre wrote on Mon, Jul 15, 2019 at 06:43:09PM +0100:
> > On Mon, Jul 15, 2019 at 04:56:29PM +0200, Klemens Nanni wrote:
>
> >> This tool comes from the textproc/vgrind port so base does not have it,
> >> is that the reason we do not reference it?
> >>
> >> I think it is still useful, so here's the Xr addition.
>
> > we pretty much try to keep xrs only to base pages in base pages.
> > yes, there are exceptions, but they are few and far between.
> > i'm not keen to start adding xrs to pages other people don;t have.
>
> I tend to agree with Jason; besides, it would also cause dead
> hyperlinks on man.openbsd.org.
>
> The following may be useful, though.  This kind of reference occurs
> rarely enough that i'm not sure whether we have a standard wording
> for it.
>
> Yours,
>   Ingo
>
>
> Index: ctags.1
> ===================================================================
> RCS file: /cvs/src/usr.bin/ctags/ctags.1,v
> retrieving revision 1.33
> diff -u -p -r1.33 ctags.1
> --- ctags.1 31 Dec 2015 14:01:26 -0000 1.33
> +++ ctags.1 15 Jul 2019 19:33:36 -0000
> @@ -171,7 +171,8 @@ default output tags file
>  Duplicate objects are not considered errors.
>  .Sh SEE ALSO
>  .Xr mg 1 ,
> -.Xr vi 1
> +.Xr vi 1 ,
> +and the textproc/vgrind port
>  .Sh STANDARDS
>  The
>  .Nm

i don;t like it, to be honest. can't you just reference the port in the
main body, if it's really needed?

        ...expected by the textproc/vgrind port is produced...

jmc

Reply | Threaded
Open this post in threaded view
|

Re: ctags.1: Xr vgrind

Ingo Schwarze
Hi Jason,

Jason McIntyre wrote on Mon, Jul 15, 2019 at 09:04:23PM +0100:
> On Mon, Jul 15, 2019 at 09:35:26PM +0200, Ingo Schwarze wrote:
>> Jason McIntyre wrote on Mon, Jul 15, 2019 at 06:43:09PM +0100:
>>> On Mon, Jul 15, 2019 at 04:56:29PM +0200, Klemens Nanni wrote:

>>>> This tool comes from the textproc/vgrind port so base does not
>>>> have it, is that the reason we do not reference it?
>>>> I think it is still useful, so here's the Xr addition.

>>> we pretty much try to keep xrs only to base pages in base pages.
>>> yes, there are exceptions, but they are few and far between.
>>> i'm not keen to start adding xrs to pages other people don;t have.

>> I tend to agree with Jason; besides, it would also cause dead
>> hyperlinks on man.openbsd.org.
>> The following may be useful, though.  This kind of reference occurs
>> rarely enough that i'm not sure whether we have a standard wording
>> for it.

> i don;t like it, to be honest.  can't you just reference the port
> in the main body, if it's really needed?
>
> ...expected by the textproc/vgrind port is produced...

Indeed, that's even better because it is really only relevant in
the context of the ctags -v option.

OK?
  Ingo


Index: ctags.1
===================================================================
RCS file: /cvs/src/usr.bin/ctags/ctags.1,v
retrieving revision 1.33
diff -u -r1.33 ctags.1
--- ctags.1 31 Dec 2015 14:01:26 -0000 1.33
+++ ctags.1 15 Jul 2019 20:39:45 -0000
@@ -92,8 +92,9 @@
 references to them are regenerated, keeping only the other values in the
 file.
 .It Fl v
-An index of the form expected by vgrind
-is produced on the standard output.
+An index of the form expected by the
+.Pa textproc/vgrind
+port is produced on the standard output.
 This listing contains the object name, file name, and page number (assuming
 64 line pages).
 Since the output will be sorted into lexicographic order,

Reply | Threaded
Open this post in threaded view
|

Re: ctags.1: Xr vgrind

Jason McIntyre-2
On Mon, Jul 15, 2019 at 10:40:46PM +0200, Ingo Schwarze wrote:

> Hi Jason,
>
> Jason McIntyre wrote on Mon, Jul 15, 2019 at 09:04:23PM +0100:
> > On Mon, Jul 15, 2019 at 09:35:26PM +0200, Ingo Schwarze wrote:
> >> Jason McIntyre wrote on Mon, Jul 15, 2019 at 06:43:09PM +0100:
> >>> On Mon, Jul 15, 2019 at 04:56:29PM +0200, Klemens Nanni wrote:
>
> >>>> This tool comes from the textproc/vgrind port so base does not
> >>>> have it, is that the reason we do not reference it?
> >>>> I think it is still useful, so here's the Xr addition.
>
> >>> we pretty much try to keep xrs only to base pages in base pages.
> >>> yes, there are exceptions, but they are few and far between.
> >>> i'm not keen to start adding xrs to pages other people don;t have.
>
> >> I tend to agree with Jason; besides, it would also cause dead
> >> hyperlinks on man.openbsd.org.
> >> The following may be useful, though.  This kind of reference occurs
> >> rarely enough that i'm not sure whether we have a standard wording
> >> for it.
>
> > i don;t like it, to be honest.  can't you just reference the port
> > in the main body, if it's really needed?
> >
> > ...expected by the textproc/vgrind port is produced...
>
> Indeed, that's even better because it is really only relevant in
> the context of the ctags -v option.
>
> OK?
>   Ingo
>

yes, fine by me.
jmc

>
> Index: ctags.1
> ===================================================================
> RCS file: /cvs/src/usr.bin/ctags/ctags.1,v
> retrieving revision 1.33
> diff -u -r1.33 ctags.1
> --- ctags.1 31 Dec 2015 14:01:26 -0000 1.33
> +++ ctags.1 15 Jul 2019 20:39:45 -0000
> @@ -92,8 +92,9 @@
>  references to them are regenerated, keeping only the other values in the
>  file.
>  .It Fl v
> -An index of the form expected by vgrind
> -is produced on the standard output.
> +An index of the form expected by the
> +.Pa textproc/vgrind
> +port is produced on the standard output.
>  This listing contains the object name, file name, and page number (assuming
>  64 line pages).
>  Since the output will be sorted into lexicographic order,

Reply | Threaded
Open this post in threaded view
|

Re: ctags.1: Xr vgrind

Klemens Nanni-2
In reply to this post by Ingo Schwarze
On Mon, Jul 15, 2019 at 10:40:46PM +0200, Ingo Schwarze wrote:
> Indeed, that's even better because it is really only relevant in
> the context of the ctags -v option.
OK kn