Mercurial > emacs

comparison etc/NEWS @ 45802:d4c9f3bd6dfa

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
New {language} and @regexp features.
author Francesco Potortì <pot@gnu.org>
date Thu, 13 Jun 2002 12:10:39 +0000
parents d11816fe2c59
children ad50e4ff5888
comparison
equal deleted inserted replaced
45801:0cbd872ef18b 45802:d4c9f3bd6dfa
568 comparison. 568 comparison.
569 569
570 ** Etags changes. 570 ** Etags changes.
571 571
572 *** New syntax for regular expressions, multi-line regular expressions. 572 *** New syntax for regular expressions, multi-line regular expressions.
573 The syntax --ignore-case-regexp=/REGEX/NAME/ is now undocumented and 573 The syntax --ignore-case-regexp=/regex/ is now undocumented and retained
574 retained only for backward compatibility. The new equivalent syntax is 574 only for backward compatibility. The new equivalent syntax is
575 --regex=/REGEX/NAME/i. More generally, it is --regex=/REGEX/NAME/MODS, 575 --regex=/regex/i. More generally, it is --regex=/TAGREGEX/TAGNAME/MODS,
576 where `/NAME' is optional, as usual, and MODS is a string of 0 or more 576 where `/TAGNAME' is optional, as usual, and MODS is a string of 0 or
577 characters among `i' (ignore case), `m' (multi-line) and `s' 577 more characters among `i' (ignore case), `m' (multi-line) and `s'
578 (single-line). The `m' and `s' modifiers behave as in Perl regular 578 (single-line). The `m' and `s' modifiers behave as in Perl regular
579 expressions: `m' allows regexps to match more than one line, while `s' 579 expressions: `m' allows regexps to match more than one line, while `s'
580 (which implies `m') means that `.' matches newlines. The ability to 580 (which implies `m') means that `.' matches newlines. The ability to
581 span newlines allows writing of much more powerful regular expressions 581 span newlines allows writing of much more powerful regular expressions
582 and rapid prototyping for tagging new languages. 582 and rapid prototyping for tagging new languages.
583 583
584 *** Regular expressions can use char escape sequences as in Gcc 584 *** Regular expressions can use char escape sequences as in Gcc
585 The escaped character sequence \a, \b, \d, \e, \f, \n, \r, \t, \v, 585 The escaped character sequence \a, \b, \d, \e, \f, \n, \r, \t, \v,
586 respectively, stand for the ASCII characters BEL, BS, DEL, ESC, FF, NL, 586 respectively, stand for the ASCII characters BEL, BS, DEL, ESC, FF, NL,
587 CR, TAB, VT, 587 CR, TAB, VT,
588
589 *** Regular expressions can be bound to a given language
590 The syntax --regex={LANGUAGE}REGEX means that REGEX is used to make tags
591 only for files of language LANGUAGE, and ignored otherwise. This is
592 particularly useful when storing regexps in a file.
593
594 *** Regular expressions can be read from a file
595 The --regex=@regexfile option means read the regexps from a file, one
596 per line. Lines beginning with space or tab are ignored.
588 597
589 *** In Prolog, etags creates tags for rules in addition to predicates. 598 *** In Prolog, etags creates tags for rules in addition to predicates.
590 599
591 *** In Perl, packages are tags. 600 *** In Perl, packages are tags.
592 Subroutine tags are named from their package. You can jump to sub tags 601 Subroutine tags are named from their package. You can jump to sub tags