From: John Kitchin <jkitchin@andrew.cmu.edu>
To: org-mode-email <emacs-orgmode@gnu.org>
Subject: exporting code blocks with continued line numbers?
Date: Tue, 8 Jan 2019 11:40:19 -0500 [thread overview]
Message-ID: <CAJ51EToeQAaecRTyU3L0aK3aK+3sCS6W8bAMJysSKuvqu_NGVA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1035 bytes --]
Hi all,
In the following example document:
#+BEGIN_SRC python -r +n
#!/bin/env python (ref:bang)
print() (ref:print)
#+END_SRC
Next, you need to modify line [[(filename)]] to point to the Excel sheet
you have saved the data in, line [[(sheet)]] with an integer for the sheet
number for the data (index starts at 1), and line [[(range)]] with the
range for the data.
#+BEGIN_SRC python -r +n
filename = 'Copper_Samples' (ref:filename)
sheet = 6 (ref:sheet)
Tstar1 = xlsread(filename, sheet, 'A2:E29') (ref:range)
#+END_SRC
When I export this to LaTeX, the line numbers to the coderefs in the text
are correct, but the line numbers in each code block start at 1. I am
using minted for the export. Is there an option that will tell minted to
continue the line numbers from the previous block?
Thanks,
John
-----------------------------------
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
@johnkitchin
http://kitchingroup.cheme.cmu.edu
[-- Attachment #2: Type: text/html, Size: 1565 bytes --]
next reply other threads:[~2019-01-08 16:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-08 16:40 John Kitchin [this message]
2019-01-08 17:31 ` exporting code blocks with continued line numbers? John Kitchin
2019-01-09 2:53 ` stardiviner
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=CAJ51EToeQAaecRTyU3L0aK3aK+3sCS6W8bAMJysSKuvqu_NGVA@mail.gmail.com \
--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).