From: John Kitchin <jkitchin@andrew.cmu.edu>
To: Charles Berry <ccberry@ucsd.edu>
Cc: emacs-orgmode@gnu.org
Subject: Re: line numbers in a code block?
Date: Sat, 27 Sep 2014 16:37:25 -0400 [thread overview]
Message-ID: <874mvsajga.fsf@andrew.cmu.edu> (raw)
In-Reply-To: <loom.20140927T173824-405@post.gmane.org> (Charles Berry's message of "Sat, 27 Sep 2014 15:57:51 +0000 (UTC)")
Charles Berry <ccberry@ucsd.edu> writes:
> John Kitchin <jkitchin <at> 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?
>
> You mean like
>
> (org-add-hook 'org-src-mode-hook 'linum-mode)
No, that is not quite what I need. We already have those line numbers on
the left. I wanted a new set of numbers, only in the src-block, and on
the right so they do not get mixed up with the linum-mode numbers. This
is to avoid having to go into the org-src-mode at all.
>
> only with line numbers on the right side? (linum puts them on the left)
>
> Or did you mean in the org-mode buffer itself?
>
> Maybe (just a guess) hack `linum-update-window' to reset `line' to 0
> whenever `(forward-line))'gives you a line that matches `#+begin_src'.
I suppose it would involve creating new overlays the way that linum-mode
does.
>
>
> HTH,
>
> Chuck
>
>
>
--
-----------------------------------
John Kitchin
Professor
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
http://kitchingroup.cheme.cmu.edu
next prev parent reply other threads:[~2014-09-27 20:37 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 [this message]
2014-09-27 20:40 ` John Kitchin
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=874mvsajga.fsf@andrew.cmu.edu \
--to=jkitchin@andrew.cmu.edu \
--cc=ccberry@ucsd.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).