I came up with a reasonable solution to this that I think is pretty nice. It doesn't put linenumbers on the src block, but it does something even better!
The gist is to write the block to a temporary file, then run pyflakes, pep8 and pylint on it. The output of those goes into a temporary org-buffer, with links back to the positions in the code block where the errors are! The code is laid out here: http://kitchingroup.cheme.cmu.edu/blog/2014/09/27/Improved-debugging-of-Python-code-blocks-in-org-mode/ I am going to try it out with my students next week! j John Kitchin <jkitc...@andrew.cmu.edu> writes: > Does anyone know a way to get dedicate line numbers in an org code > block? > > I know how to get buffer code lines, but when we run a code block and > there is an error, the error line number is relative to line 1 of the > code block. Currently, we type C-c ' to get a code buffer, and navigate > to the line. I would like to see code block numbers on the right hand > side of the buffer, and only inside the code block. Any ideas? > > Thanks, -- ----------------------------------- John Kitchin Professor Doherty Hall A207F Department of Chemical Engineering Carnegie Mellon University Pittsburgh, PA 15213 412-268-7803 http://kitchingroup.cheme.cmu.edu
