Lines Matching refs:text
3 text format for ease of searching with a text editor, or for use on systems
6 the pcredemo program. There are separate text files for the pcregrep and
130 In the plain text format, all the sections, except the pcredemo sec-
462 If there is an error while compiling a pattern, the error text that is
788 If there is an error while compiling a pattern, the error text that is
1181 By default, pcregrep reads all files as plain text. You can build it so
1800 argument of pcre_compile(), or it can be specified by special text at
2154 matched text may continue over the newline.
4723 terminates a pattern, but when a pattern is being prepared by text
6416 If the text between the parentheses consists of a sequence of digits,
6668 recursion. Consider this pattern, which matches text in angle brack-
7071 tered. (*SKIP) signifies that whatever text was matched leading up to
8518 At this stage, an application could discard the text preceding "23ja",
8519 add on text from the next segment, and call the matching function
9256 The "FullMatch" operation checks that supplied text matches a supplied
9271 You can pass in a "const char*" or a "string" for "text". The examples
9311 a. "text" matches "pattern" exactly;
9358 match any substring of the text.
9372 By default, pattern and text are plain text, one byte per character.
9374 string to be treated as UTF-8 text, still a byte stream but potentially
9375 multiple bytes per character. In practice, the text is likelier to be
9377 flag, so always use it when matching UTF8 text. For example, "." will
9505 advance "input" so it points past the matched text.
9517 text is interpreted as a base-10 number. You can instead wrap the
9519 to interpret the text in another base. The CRadix operator interprets
9537 insert text matching corresponding parenthesized group from the pat-
9538 tern. \0 in "rewrite" refers to the entire matching text. For example:
9558 non-matching portions of "text" are ignored. Returns true iff a match
