>>>>> "Nick" == Nick Roberts <Nick> writes: > > I don't use more than one arrow per buffer. However, I do think compile > should use overlay-arrow-variable-list instead of making > overlay-arrow-position a local variable. I now can reproduce the conflict > that > Juan-Leon reports. GUD and Compile are operating on the same source buffer > and > the local variable masks the global one when set in gud-display-line. The > global value is used to set window-point and this remains unchanged (from > nil): >
I can trigger the error with following sequence: emacs -Q (setq next-error-highlight 'fringe-arrow) C-x C-e C-x C-f foo.c create a foo.c with errors M-x compile gcc -g foo.c Jump to errors pressing RET on compilation buffer and fix it without deleting line where fringe arrow is, so it remains after doing: M-x compile gcc -g foo.c M-x gdb (line is gdb --fullname a.out) b main run now I get an error: error in process filter: Wrong type argument: integer-or-marker-p, nil error in process filter: gud-display-line: Wrong type argument: integer-or-marker-p, nil The overlay arrow is updated fine, but buffer is not scrolled to new position (if you make foo.c 100 lines long, the compilation error were in line 2 and main is in line 90 you'll see better this). Maybe this info regarding what I have may help with this: /compile.el/1.346/Wed Feb 9 15:50:36 2005// /gud.el/1.29/Wed Feb 2 05:52:51 2005// gdb --version = GNU gdb 5.1 Regards -- juanleon _______________________________________________ Emacs-pretest-bug mailing list [email protected] http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
