Mercurial > emacs
view BUGS @ 110543:a89eabac600d
Fix int/EMACS_INT usage in fns.c.
fns.c (Fcompare_strings, Fstring_lessp, concat)
(string_make_unibyte, Fstring_as_unibyte, Fsubstring)
(Fsubstring_no_properties, substring_both, Ffillarray)
(Fclear_string, mapcar1, Fmapconcat, Fmapcar, Fmapc)
(Fbase64_encode_region, Fbase64_encode_string, base64_encode_1)
(Fbase64_decode_region, Fbase64_decode_string, base64_decode_1)
(Fmd5): Use EMACS_INT for buffer and string positions and length
variables and arguments.
<struct textprop_rec>: Use EMACS_INT for positions.
lisp.h (substring_both): Adjust prototype.
author | Eli Zaretskii <eliz@gnu.org> |
---|---|
date | Fri, 24 Sep 2010 07:55:44 -0400 |
parents | fb8bf24d2eb9 |
children | ac52af4a044c |
line wrap: on
line source
If you think you may have found a bug in GNU Emacs, please read the Bugs section of the Emacs manual for advice on (1) how to tell when to report a bug, and (2) how to write a useful bug report and what information it needs to have. There are three ways to read the Bugs section. (1) In a printed copy of the Emacs manual. You can order one from the Free Software Foundation; see the file etc/ORDERS. But if you don't have a copy on hand and you think you have found a bug, you shouldn't wait to get a printed manual; you should read the section right away as described below. (2) With Info. Start Emacs, do C-h i to enter Info, then m Emacs RET to get to the Emacs manual, then m Bugs RET to get to the section on bugs. Or use standalone Info in a like manner. (Standalone Info is part of the Texinfo distribution, not part of the Emacs distribution.) (3) By hand. Do cat info/emacs* | more "+/^File: emacs, Node: Bugs," Please first check the file etc/PROBLEMS (e.g. with C-h C-p in Emacs) to make sure it isn't a known issue.