mirror of
https://git.savannah.gnu.org/git/emacs.git
synced 2024-12-02 08:22:22 +00:00
Remove outdated paragraph from Lisp manual (Bug#7780).
* doc/lispref/searching.texi (Regexp Special): Remove outdated discussion of character sets.
This commit is contained in:
parent
cc9c9831b9
commit
3f066f54dd
@ -1,3 +1,8 @@
|
||||
2011-01-23 Chong Yidong <cyd@stupidchicken.com>
|
||||
|
||||
* searching.texi (Regexp Special): Remove outdated discussion of
|
||||
character sets (Bug#7780).
|
||||
|
||||
2011-01-22 Chong Yidong <cyd@stupidchicken.com>
|
||||
|
||||
* frames.texi (Pop-Up Menus): Document where menu title comes
|
||||
|
@ -386,15 +386,6 @@ matches both @samp{]} and @samp{-}.
|
||||
To include @samp{^} in a character alternative, put it anywhere but at
|
||||
the beginning.
|
||||
|
||||
The beginning and end of a range of multibyte characters must be in
|
||||
the same character set (@pxref{Character Sets}). Thus,
|
||||
@code{"[\x8e0-\x97c]"} is invalid because character 0x8e0 (@samp{a}
|
||||
with grave accent) is in the Emacs character set for Latin-1 but the
|
||||
character 0x97c (@samp{u} with diaeresis) is in the Emacs character
|
||||
set for Latin-2. (We use Lisp string syntax to write that example,
|
||||
and a few others in the next few paragraphs, in order to include hex
|
||||
escape sequences in them.)
|
||||
|
||||
If a range starts with a unibyte character @var{c} and ends with a
|
||||
multibyte character @var{c2}, the range is divided into two parts: one
|
||||
is @samp{@var{c}..?\377}, the other is @samp{@var{c1}..@var{c2}}, where
|
||||
|
Loading…
Reference in New Issue
Block a user