view BUGS @ 107713:41747909cb4b

Get rid of the direct_output optimizations. * keyboard.c (nonundocount): Remove extern declaration. (command_loop_1): Remove brittle optimisation for cheap and common operations. * xdisp.c (redisplay_internal): Don't bother checking redisplay_performed_directly_p any more. * sysdep.c (init_sys_modes): Don't call direct_output_forward_char any more. * dispnew.c (redisplay_performed_directly_p) (direct_output_for_insert, direct_output_forward_char): * dispextern.h (redisplay_performed_directly_p) (direct_output_for_insert, direct_output_forward_char): Remove. * cmds.c (nonundocount): Make it static.
author Stefan Monnier <monnier@iro.umontreal.ca>
date Wed, 31 Mar 2010 00:14:08 -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.