aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorFrancesco Potortì2002-06-06 22:58:11 +0000
committerFrancesco Potortì2002-06-06 22:58:11 +0000
commitb4b39c67fce91d62c33350065ce255da4f32d4f1 (patch)
treec9fa099362ea4e24a78510b84767e5da48c9e35c
parente7d3b099a25e2a895b0b9ff3e1f7100082f170a6 (diff)
downloademacs-b4b39c67fce91d62c33350065ce255da4f32d4f1.tar.gz
emacs-b4b39c67fce91d62c33350065ce255da4f32d4f1.zip
Document Etags regexp char escape sequences.
-rw-r--r--etc/NEWS3
-rw-r--r--etc/etags.13
-rw-r--r--man/maintaining.texi27
3 files changed, 30 insertions, 3 deletions
diff --git a/etc/NEWS b/etc/NEWS
index 0240b33ca38..369529dede8 100644
--- a/etc/NEWS
+++ b/etc/NEWS
@@ -593,6 +593,9 @@ be used (only once) in place of a file name on the command line. Etags
593will read from standard input and mark the produced tags as belonging to 593will read from standard input and mark the produced tags as belonging to
594the file FILE. 594the file FILE.
595 595
596*** Regular expressions can use char escape sequences as in Gcc
597These are the escapes \a, \b, \d, \e, \f, \n, \r, \t, \v.
598
596+++ 599+++
597** The command line option --no-windows has been changed to 600** The command line option --no-windows has been changed to
598--no-window-system. The old one still works, but is deprecated. 601--no-window-system. The old one still works, but is deprecated.
diff --git a/etc/etags.1 b/etc/etags.1
index 26381e3b682..ffa937750bc 100644
--- a/etc/etags.1
+++ b/etc/etags.1
@@ -168,6 +168,9 @@ such that more characters than needed are unavoidably matched by
168\fItagregexp\fP, it may be useful to add a \fInameregexp\fP, to 168\fItagregexp\fP, it may be useful to add a \fInameregexp\fP, to
169narrow down the tag scope. \fBctags\fP ignores regexps without a 169narrow down the tag scope. \fBctags\fP ignores regexps without a
170\fInameregexp\fP. The syntax of regexps is the same as in emacs. 170\fInameregexp\fP. The syntax of regexps is the same as in emacs.
171The following character escape sequences are supported:
172\\a, \\b, \\d, \\e, \\f, \\n, \\r, \\t, \\v.
173
171.br 174.br
172Here are some examples. All the regexps are quoted to protect them 175Here are some examples. All the regexps are quoted to protect them
173from shell interpretation. 176from shell interpretation.
diff --git a/man/maintaining.texi b/man/maintaining.texi
index 221711d8b1b..3e8990f8a62 100644
--- a/man/maintaining.texi
+++ b/man/maintaining.texi
@@ -485,9 +485,30 @@ where @var{tagregexp} is used to match the lines to tag. It is always
485anchored, that is, it behaves as if preceded by @samp{^}. If you want 485anchored, that is, it behaves as if preceded by @samp{^}. If you want
486to account for indentation, just match any initial number of blanks by 486to account for indentation, just match any initial number of blanks by
487beginning your regular expression with @samp{[ \t]*}. In the regular 487beginning your regular expression with @samp{[ \t]*}. In the regular
488expressions, @samp{\} quotes the next character, and @samp{\t} stands 488expressions, @samp{\} quotes the next character, and all the
489for the tab character. Note that @code{etags} does not handle the other 489@code{gcc} character escape sequences are supported. Here is the list
490C escape sequences for special characters. 490of the character escape sequences:
491
492@table @samp
493@item \a
494BEL (bell).
495@item \b
496BS (back space).
497@item \d
498DEL (delete).
499@item \e
500ESC (delete).
501@item \f
502FF (form feed).
503@item \n
504NL (new line).
505@item \r
506CR (carriage return).
507@item \t
508TAB (horizontal tab).
509@item \v
510VT (vertical tab).
511@end table
491 512
492 The syntax of regular expressions in @code{etags} is the same as in 513 The syntax of regular expressions in @code{etags} is the same as in
493Emacs. However, non-greedy operators and shy groups are not 514Emacs. However, non-greedy operators and shy groups are not