Lines Matching full:sequences
132 * Backslash:: Introduces special sequences
532 sequences
686 As @code{*}, but matches exactly @var{i} sequences (@var{i} is a
691 Matches between @var{i} and @var{j}, inclusive, sequences.
694 Matches more than or equal to @var{i} sequences.
703 this will search for zero or more whole sequences
749 sequences like @code{@var{char1}-@var{char2}}, which
799 backslash sequences that you can portably assume to be
1097 sequences
1172 Escape sequences in @var{text} are processed, so you should
1499 and works in the presence of invalid multibyte sequences
1500 in the input stream. @sc{posix} mandates that such sequences
1529 the following escape sequences than the binary character it
2562 The following Perl escape sequences are not supported:
2691 the standard, the meaning of some escape sequences is undefined in
2697 expressions, @command{sed} interprets these escape sequences as special
2792 sequences. @sc{posix} mandates that such sequences
2860 A backslash can introduce several special sequences
2906 On one hand Perl introduces several more escaped sequences
2907 (that is, sequences introduced by a backslash). On the other
2912 * Backslash:: Introduces special sequences
2928 @cindex Perl-style regular expressions, escaped sequences
2931 sequences in Perl mode.
2933 First of all, there are no @code{\o} and @code{\d} sequences.
2982 All the sequences that define a single byte value can be
3000 In Perl mode, these character type sequences can appear both inside and
3001 outside character classes. Instead, in @sc{posix} mode these sequences
3005 Escaped sequences specifying assertions are also different in
3095 Note that the sequences @code{\A}, @code{\Z}, and @code{\z}
3494 the sequences @code{/*} and @code{*/} and within the sequence, individual
3945 sequences of non-digits cannot be broken, and failure happens
