• State "PROPOSED" from "" 2010-06-30 Wed 09:30

Thanks to Russel Adams for this idea.

> OTOH this may not make it easier to debug, the babel error window
> doesn't list line numbers or blocks where the error occurred. Perhaps
> that should be a feature request to log what src block or org file
> line number the errors occurred in.

This could be very useful both when evaluating an entire block or subtree, and also when old error messages have built up in the Error buffer.

python.el seems to make use of compile.el to provide links to errors. I wonder if there is any way we can do something similar.

Line 1632 in python.el

(with-current-buffer (process-buffer (python-proc))
  ;; Tell compile.el to redirect error locations in file `f' to
  ;; positions past marker `orig-start'.  It has to be done *after*
  ;; `python-send-command''s call to `compilation-forget-errors'.
  (compilation-fake-loc orig-start f))

• State "TODO" from "" 2010-07-13 Tue 10:22

`q' should be bound to bury-buffer, or something similar