Lines Matching full:sequences
133 * Backslash:: Introduces special sequences
533 sequences
687 As @code{*}, but matches exactly @var{i} sequences (@var{i} is a
692 Matches between @var{i} and @var{j}, inclusive, sequences.
695 Matches more than or equal to @var{i} sequences.
704 this will search for zero or more whole sequences
750 sequences like @code{@var{char1}-@var{char2}}, which
800 backslash sequences that you can portably assume to be
1098 sequences
1173 Escape sequences in @var{text} are processed, so you should
1500 and works in the presence of invalid multibyte sequences
1501 in the input stream. @sc{posix} mandates that such sequences
1530 the following escape sequences than the binary character it
2729 The following Perl escape sequences are not supported:
2858 the standard, the meaning of some escape sequences is undefined in
2864 expressions, @command{sed} interprets these escape sequences as special
2959 sequences. @sc{posix} mandates that such sequences
3027 A backslash can introduce several special sequences
3073 On one hand Perl introduces several more escaped sequences
3074 (that is, sequences introduced by a backslash). On the other
3079 * Backslash:: Introduces special sequences
3095 @cindex Perl-style regular expressions, escaped sequences
3098 sequences in Perl mode.
3100 First of all, there are no @code{\o} and @code{\d} sequences.
3149 All the sequences that define a single byte value can be
3167 In Perl mode, these character type sequences can appear both inside and
3168 outside character classes. Instead, in @sc{posix} mode these sequences
3172 Escaped sequences specifying assertions are also different in
3262 Note that the sequences @code{\A}, @code{\Z}, and @code{\z}
3661 the sequences @code{/*} and @code{*/} and within the sequence, individual
4112 sequences of non-digits cannot be broken, and failure happens
