From: tsd@tsdye.com (Thomas S. Dye)
To: John Kitchin <jkitchin@andrew.cmu.edu>
Cc: emacs-orgmode@gnu.org
Subject: Re: example filter for code blocks?
Date: Thu, 26 Sep 2013 09:43:23 -1000 [thread overview]
Message-ID: <m1y56jjrms.fsf@poto.westell.com> (raw)
In-Reply-To: <CAJ51ETq0Y7di4opjqGdDxoYP37QaKythGZfaWXNzmGST3bK9ZQ@mail.gmail.com> (John Kitchin's message of "Thu, 26 Sep 2013 13:57:35 -0400")
Hi John,
John Kitchin <jkitchin@andrew.cmu.edu> writes:
> Hi everyone,
> Thanks for the tips in using export filters for code blocks. I thought I
> would share my current solution. The goal was to export all the code blocks
> in an org-file to files systematically named part1/script-%d.py where %d is
> a number. I didnot want to tangle exactly, because I wanted to avoid naming
> the code block tangle files.
>
> Then, I wanted to insert a pdf link that would open the file, after the
> syntax highlighted code.
>
> I wanted this because it is not convenient to copy and paste the
> syntax-highlighted code into an editor. I teach from the pdf that is
> generated, and it would be convenient to just open the code, edit and rerun
> to explore solutions.
This seems like it might be an elegant way to distribute a piece of
reproducible research. I suspect most readers would prefer to have a pdf
entry point into a compendium over an Org-mode entry point. Instead of
distributing the Org-mode file that is configured to make a pdf file,
carry out calculations, draw figures, etc., one could distribute a
ready-made pdf file with an appendix of Supplementary Material that has
all the code for calculations, figures, etc.
What do you think?
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
next prev parent reply other threads:[~2013-09-26 19:44 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-26 17:57 example filter for code blocks? John Kitchin
2013-09-26 19:43 ` Thomas S. Dye [this message]
2013-09-26 19:48 ` John Kitchin
2013-09-26 20:58 ` Thomas S. Dye
2013-09-27 7:42 ` Sebastien Vauban
2013-09-30 0:33 ` Thomas S. Dye
2013-09-30 0:45 ` John Kitchin
2013-09-30 2:58 ` Thomas S. Dye
2013-09-30 7:34 ` Achim Gratz
2013-09-30 17:48 ` Thomas S. Dye
-- strict thread matches above, loose matches on Subject: below --
2013-09-27 18:44 John Kitchin
2013-09-27 12:59 John Kitchin
2013-09-27 15:24 ` Alan Schmitt
2013-09-27 15:34 ` John Kitchin
2013-09-30 7:49 ` Alan Schmitt
2013-09-26 0:03 John Kitchin
2013-09-26 8:40 ` Daniele Pizzolli
2013-09-26 9:04 ` Marcin Borkowski
2013-09-26 12:18 ` Eric Schulte
2013-09-26 18:31 ` Cook, Malcolm
2013-09-26 19:34 ` 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=m1y56jjrms.fsf@poto.westell.com \
--to=tsd@tsdye.com \
--cc=emacs-orgmode@gnu.org \
--cc=jkitchin@andrew.cmu.edu \
/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).