> For cases like this, typing `c' does not get precise information. > If you see foo called from bar each time, you can't tell if > it is the same call to bar, or a second call to bar.
Ok. In this case it seemed consistent with what I was seeing without the debugger; the hook was being run twice for a single mouse-1 at point. With the breakpoint where the hook is run from, the breakpoint was hit twice for a single mouse-1 at point and the backtrace was different in each case. > To find that out, use the `finish' command frame by frame, or > use stepping. Ok, thanks. > (gdb) c > Continuing. > Hardware watchpoint 6: windows_or_buffers_changed > > Old value = 0 > New value = 1 > > That might be what we need to know. mouse-drag-region has to > call delete-overlay. > > So it isn't a bug. Just the lack of optimization in this case. I guess that depends on your definition of a bug. The hook isn't run at all when the buffer is shown in a single frame, but is run twice when the buffer is shown in more than one frame. You say optato, I say bugato... Or, at least, inconsistency. Does that mean you don't plan on optimising for this case? Thanks, Simon. _______________________________________________ emacs-pretest-bug mailing list [email protected] http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
