From: Stefan Kangas Date: Sun, 27 Nov 2022 23:00:11 +0000 (+0100) Subject: ; Fix groff warnings in man pages X-Git-Tag: emacs-29.0.90~1292 X-Git-Url: http://git.eshelyaron.com/gitweb/?a=commitdiff_plain;h=bdbb7099784eb79ef9b94bb85f0c3dc9dae82d6c;p=emacs.git ; Fix groff warnings in man pages This fixes check-man-pages warnings such as: troff: doc/man/etags.1:203: warning: escape character ignored before '=' * doc/man/etags.1: Fix groff warnings. --- diff --git a/doc/man/etags.1 b/doc/man/etags.1 index 8dbea25c4cf..d3d58b82123 100644 --- a/doc/man/etags.1 +++ b/doc/man/etags.1 @@ -209,7 +209,7 @@ otherwise. This is particularly useful when storing many predefined regexps in a file. .br In its second form, \fIregexfile\fP is the name of a file that contains -a number of arguments to the \fI\-\-regex\=\fP option, +a number of arguments to the \fI\-\-regex=\fP option, one per line. Lines beginning with a space or tab are assumed to be comments, and ignored. @@ -220,22 +220,22 @@ from shell interpretation. Tag the DEFVAR macros in the emacs source files: .br -\fI\-\-regex\='/[ \\t]*DEFVAR_[A-Z_ \\t(]+"\\([^"]+\\)"/'\fP +\fI\-\-regex='/[ \\t]*DEFVAR_[A-Z_ \\t(]+"\\([^"]+\\)"/'\fP .\"" This comment is to avoid confusion to Emacs syntax highlighting .br Tag VHDL files (this example is a single long line, broken here for formatting reasons): .br -\fI\-\-language\=none\ \-\-regex='/[\ \\t]*\\(ARCHITECTURE\\|\\ -CONFIGURATION\\)\ +[^\ ]*\ +OF/'\ \-\-regex\='/[\ \\t]*\\ +\fI\-\-language=none\ \-\-regex='/[\ \\t]*\\(ARCHITECTURE\\|\\ +CONFIGURATION\\)\ +[^\ ]*\ +OF/'\ \-\-regex='/[\ \\t]*\\ \\(ATTRIBUTE\\|ENTITY\\|FUNCTION\\|PACKAGE\\(\ BODY\\)?\\ \\|PROCEDURE\\|PROCESS\\|TYPE\\)[\ \\t]+\\([^\ \\t(]+\\)/\\3/'\fP .br Tag Tcl files (this last example shows the usage of a \fItagregexp\fP): .br -\fI\-\-lang\=none \-\-regex\='/proc[\ \\t]+\\([^\ \\t]+\\)/\\1/'\fP +\fI\-\-lang=none \-\-regex='/proc[\ \\t]+\\([^\ \\t]+\\)/\\1/'\fP .br A regexp can be preceded by {\fIlang\fP}, thus restricting it to match