Lines Matching refs:a

3 Before reporting a bug, please check the list of known bugs
10 Please do not send a bug report like this:
16 If sed doesn't configure your favorite package, take a few extra
17 minutes to identify the specific problem and make a stand-alone test
22 smaller a stand-alone test case is, the better.  A test case should
25 for the bug, but that is not a very practical prospect.
34   command is issued on the last line of a file.  GNU sed instead
64   a slash, which is again undefined behavior; the new behavior avoids
70   in scripts (`\a', `\c', `\d', `\o', `\r', `\t', `\v', `\x').  These
77   a read-only file, and in general the `-i' option will let
78   one clobber protected files.  This is not a bug, but rather a
81   The permissions on a file say what can happen to the data
82   in that file, while the permissions on a directory say what can
84   will not ever open for writing  a file that is already on disk,
85   rather, it will work on a temporary file that is finally renamed
89   reason, sed will not let one use `-i' on a writeable file in a
91   `-i' is used on such a file.
94 `0a' does not work (gives an error)
96   There is no line 0.  0 is a special address that is only used to treat
105 `[a-z]' is case insensitive
108   You are encountering problems with locales.  POSIX mandates that `[a-z]'
110   strcoll(3) instead of strcmp(3).  Some locales have a case insensitive
113   Another problem is that [a-z] tries to use collation symbols.  This
116   In a Danish locale, for example, the regular expression `^[a-z]$'
117   matches the string `aa', because `aa' is a single collating symbol that
118   comes after `a' and before `b'; `ll' behaves similarly in Spanish
126   (including UTF-8 locales).  For this reason, GNU sed provides a `z'
131   or set the locale on a more fine-grained basis with the other LC_*