From: John Kitchin <jkitchin@andrew.cmu.edu>
To: emacs-orgmode@gnu.org
Subject: Re: line numbers in a code block?
Date: Sat, 27 Sep 2014 16:40:43 -0400 [thread overview]
Message-ID: <87zjdk94qc.fsf@andrew.cmu.edu> (raw)
In-Reply-To: <m2mw9lxkq0.fsf@andrew.cmu.edu> (John Kitchin's message of "Sat, 27 Sep 2014 09:21:27 -0400")
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 <jkitchin@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
prev parent reply other threads:[~2014-09-27 20:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-27 13:21 line numbers in a code block? John Kitchin
2014-09-27 15:57 ` Charles Berry
2014-09-27 20:37 ` John Kitchin
2014-09-27 20:40 ` John Kitchin [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zjdk94qc.fsf@andrew.cmu.edu \
--to=jkitchin@andrew.cmu.edu \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).