Re: Etags support for the Mercury programming language [continued]

[Stefan Kangas]

fabrice nicol <fabrnicol@gmail.com> writes:

> As a follow-up to my message of March 22, I would appreciate to get some
> feedback on the attached patch implementing Mercury support for 'etags'
> before considering a formal submission.

Thanks, I have just one small nit as I'm not at all familiar with
neither etags nor Mercury:

> --- a/doc/man/etags.1
> +++ b/doc/man/etags.1
> @@ -50,9 +50,9 @@ format understood by
>  .BR vi ( 1 )\c
>  \&.  Both forms of the program understand
>  the syntax of C, Objective C, C++, Java, Fortran, Ada, Cobol, Erlang,
> -Forth, Go, HTML, LaTeX, Emacs Lisp/Common Lisp, Lua, Makefile, Pascal, Perl,
> -Ruby, PHP, PostScript, Python, Prolog, Scheme and
> -most assembler\-like syntaxes.
> +Forth, Go, HTML, LaTeX, Emacs Lisp/Common Lisp, Lua, Makefile, Mercury, 
> Pascal,
> +Perl, Ruby, PHP, PostScript, Python, Prolog, Scheme and most assembler\-like
> +syntaxes.
>  Both forms read the files specified on the command line, and write a tag
>  table (defaults: \fBTAGS\fP for \fBetags\fP, \fBtags\fP for
>  \fBctags\fP) in the current working directory.

Should we perhaps also update the date at the top of that file?

I'm thinking of this line:

    .TH ETAGS 1 "2019-06-24" "GNU Tools" "GNU"