diff options
| author | Paul Eggert <eggert@cs.ucla.edu> | 2019-03-20 14:43:30 -0700 |
|---|---|---|
| committer | Paul Eggert <eggert@cs.ucla.edu> | 2019-03-20 14:44:14 -0700 |
| commit | 0924b27bca40d219e34529144ea04a581428f1f7 (patch) | |
| tree | 8cacf247cd9a1e3fa6f4f6d98ea2f1b9270b85e2 /src/fontset.c | |
| parent | 297a141ca33f7fb25c17ba0b6ed7834dfe111c48 (diff) | |
| download | emacs-0924b27bca40d219e34529144ea04a581428f1f7.tar.gz emacs-0924b27bca40d219e34529144ea04a581428f1f7.tar.bz2 emacs-0924b27bca40d219e34529144ea04a581428f1f7.zip | |
Say which regexp ranges should be avoided
* doc/lispref/searching.texi (Regexp Special): Say that
regular expressions like "[a-m-z]" and "[[:alpha:]-~]" should
be avoided, for the same reason that regular expressions like
"+" and "*" should be avoided: POSIX says their behavior is
undefined, and they are confusing anyway. Also, explain
better what happens when the bound of a range is a raw 8-bit
byte; the old explanation appears to have been obsolete
anyway. Finally, say that ranges like "[\u00FF-\xFF]" that
mix non-ASCII characters and raw 8-bit bytes should be
avoided, since it’s not clear what they should mean.
Diffstat (limited to 'src/fontset.c')
0 files changed, 0 insertions, 0 deletions