*** empty log message ***
This commit is contained in:
parent
c49b828847
commit
f34eb3733d
2 changed files with 12 additions and 12 deletions
20
etc/NEWS
20
etc/NEWS
|
@ -2102,18 +2102,14 @@ appropriate for reading truly binary files.
|
|||
** Code that uses `concat' with integer args now gets an error, as
|
||||
long promised.
|
||||
|
||||
** `scroll-left' and `scroll-right' are only effective when
|
||||
`automatic-hscrolling' is nil.
|
||||
|
||||
** The new character sets occupy private charset slots.
|
||||
|
||||
The new charsets `japanese-jisx0213-2', `mule-unicode-0100-24ff',
|
||||
`mule-unicode-2500-33ff', and `mule-unicode-e000-ffff' take up 4 slots
|
||||
for new charsets in the private area of the Mule internal character
|
||||
representation. This might cause add-on packages which add
|
||||
dimension-2 charsets to fail, because there's no only 1 slot left for
|
||||
such charsets. (There are still many free slots for dimension-1
|
||||
charsets.)
|
||||
** Not a Lisp incompatibility as such but, with the introduction of
|
||||
extra private charsets, there is now only one slot free for a new
|
||||
dimension-2 private charset. User code which tries to add more than
|
||||
one extra will fail unless you rebuild Emacs with some standard
|
||||
charset(s) removed; that is probably inadvisable because it changes
|
||||
the emacs-mule encoding. Also, files stored in the emacs-mule
|
||||
encoding using an Emacs 20 with additional private charsets defined
|
||||
will probably not be read correctly by Emacs 21.
|
||||
|
||||
|
||||
* Lisp changes made after edition 2.6 of the Emacs Lisp Manual,
|
||||
|
|
|
@ -1,3 +1,7 @@
|
|||
2001-02-20 Dave Love <fx@gnu.org>
|
||||
|
||||
* international/utf-8.el: Doc and commentary fixes.
|
||||
|
||||
2001-02-20 Eli Zaretskii <eliz@is.elta.co.il>
|
||||
|
||||
* ehelp.el (with-electric-help): Doc fix.
|
||||
|
|
Loading…
Add table
Reference in a new issue