Lines Matching refs:modifier

514 @cindex @acronym{GNU} extensions, @code{I} modifier
518 The @code{I} modifier to regular-expression matching is a @acronym{GNU}
525 @cindex @value{SSEDEXT}, @code{M} modifier
528 The @code{M} modifier to regular-expression matching is a @value{SSED}
546 @cindex @value{SSEDEXT}, @code{S} modifier
548 The @code{S} modifier to regular-expression matching is only valid
556 @cindex @value{SSEDEXT}, @code{X} modifier
558 The @code{X} modifier to regular-expression matching is also
1027 @cindex @acronym{GNU} extensions, @code{g} and @var{number} modifier interaction in @code{s} command
1078 @cindex @acronym{GNU} extensions, @code{I} modifier
1083 The @code{I} modifier to regular-expression matching is a @acronym{GNU}
1089 @cindex @value{SSEDEXT}, @code{M} modifier
1093 The @code{M} modifier to regular-expression matching is a @value{SSED}
1111 @cindex @value{SSEDEXT}, @code{S} modifier
1113 The @code{S} modifier to regular-expression matching is only valid
1121 @cindex @value{SSEDEXT}, @code{X} modifier
1123 The @code{X} modifier to regular-expression matching is also
3084 changed if the @code{M} modifier option is used. When this is
3098 is it always anchored, whether the @code{M} modifier is set or not.
3103 but not (by default) newline.  If the @code{S} modifier is used,
3293 the @code{I} modifier.  In other words, ``top level'' settings
3548 @code{S} modifier is used, the pattern is implicitly anchored,
3633 reference.  If the @code{X} modifier option is set, this can be
3972 white space to make it more readable (assume the @code{X} modifier)
4039 parentheses problem (assume the @code{X} modifier option is used
4090 If the @code{X} modifier option is used, an unescaped @code{#} character