aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorStefan Kangas2022-11-28 00:00:11 +0100
committerStefan Kangas2022-12-09 11:15:21 +0100
commitbdbb7099784eb79ef9b94bb85f0c3dc9dae82d6c (patch)
tree1a13aa4ca91f7bcc3accf7c507c8d1deb80daf41
parentd3d9676bf88cc14391ad17326d70ec21c3f4f867 (diff)
downloademacs-bdbb7099784eb79ef9b94bb85f0c3dc9dae82d6c.tar.gz
emacs-bdbb7099784eb79ef9b94bb85f0c3dc9dae82d6c.zip
; 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.
-rw-r--r--doc/man/etags.110
1 files changed, 5 insertions, 5 deletions
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
209regexps in a file. 209regexps in a file.
210.br 210.br
211In its second form, \fIregexfile\fP is the name of a file that contains 211In its second form, \fIregexfile\fP is the name of a file that contains
212a number of arguments to the \fI\-\-regex\=\fP option, 212a number of arguments to the \fI\-\-regex=\fP option,
213one per line. Lines beginning with a space or tab are assumed 213one per line. Lines beginning with a space or tab are assumed
214to be comments, and ignored. 214to be comments, and ignored.
215 215
@@ -220,22 +220,22 @@ from shell interpretation.
220 220
221Tag the DEFVAR macros in the emacs source files: 221Tag the DEFVAR macros in the emacs source files:
222.br 222.br
223\fI\-\-regex\='/[ \\t]*DEFVAR_[A-Z_ \\t(]+"\\([^"]+\\)"/'\fP 223\fI\-\-regex='/[ \\t]*DEFVAR_[A-Z_ \\t(]+"\\([^"]+\\)"/'\fP
224.\"" This comment is to avoid confusion to Emacs syntax highlighting 224.\"" This comment is to avoid confusion to Emacs syntax highlighting
225.br 225.br
226 226
227Tag VHDL files (this example is a single long line, broken here for 227Tag VHDL files (this example is a single long line, broken here for
228formatting reasons): 228formatting reasons):
229.br 229.br
230\fI\-\-language\=none\ \-\-regex='/[\ \\t]*\\(ARCHITECTURE\\|\\ 230\fI\-\-language=none\ \-\-regex='/[\ \\t]*\\(ARCHITECTURE\\|\\
231CONFIGURATION\\)\ +[^\ ]*\ +OF/'\ \-\-regex\='/[\ \\t]*\\ 231CONFIGURATION\\)\ +[^\ ]*\ +OF/'\ \-\-regex='/[\ \\t]*\\
232\\(ATTRIBUTE\\|ENTITY\\|FUNCTION\\|PACKAGE\\(\ BODY\\)?\\ 232\\(ATTRIBUTE\\|ENTITY\\|FUNCTION\\|PACKAGE\\(\ BODY\\)?\\
233\\|PROCEDURE\\|PROCESS\\|TYPE\\)[\ \\t]+\\([^\ \\t(]+\\)/\\3/'\fP 233\\|PROCEDURE\\|PROCESS\\|TYPE\\)[\ \\t]+\\([^\ \\t(]+\\)/\\3/'\fP
234.br 234.br
235 235
236Tag Tcl files (this last example shows the usage of a \fItagregexp\fP): 236Tag Tcl files (this last example shows the usage of a \fItagregexp\fP):
237.br 237.br
238\fI\-\-lang\=none \-\-regex\='/proc[\ \\t]+\\([^\ \\t]+\\)/\\1/'\fP 238\fI\-\-lang=none \-\-regex='/proc[\ \\t]+\\([^\ \\t]+\\)/\\1/'\fP
239 239
240.br 240.br
241A regexp can be preceded by {\fIlang\fP}, thus restricting it to match 241A regexp can be preceded by {\fIlang\fP}, thus restricting it to match