Mercurial > emacs
view BUGS @ 56041:bcdeaf1d58fc
(CCL_CALL_FOR_MAP_INSTRUCTION): Save eof_ic in
ccl_prog_stack_struct and update it.
(CCL_INVALID_CMD): If CCL_DEBUG is defined, call ccl_debug_hook.
(CCL_READ_CHAR): Get instruction counter from eof_ic, not from
ccl->eof_ic on EOF.
(ccl_debug_hook): New function.
(struct ccl_prog_stack): New member eof_ic.
(ccl_driver): Handle EOF in subrountine call correctly.
author | Kenichi Handa <handa@m17n.org> |
---|---|
date | Sat, 12 Jun 2004 02:33:39 +0000 |
parents | 8ce686bd7f4f |
children | fb8bf24d2eb9 |
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-e in Emacs) to make sure it isn't a known issue.