emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: John Kitchin <jkitchin@andrew.cmu.edu>
To: Alan Schmitt <alan.schmitt@polytechnique.org>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>,
	"Charles C. Berry" <ccberry@ucsd.edu>
Subject: Re: export subtree from the command line
Date: Sat, 07 Feb 2015 19:55:38 -0500	[thread overview]
Message-ID: <m2vbjdmdbp.fsf@andrew.cmu.edu> (raw)
In-Reply-To: <m2lhkbqmdz.fsf@charm-ecran.irisa.fr>

For a different approach, you could make this kind of an emacs script. I
have not done this too often, and it can be tricky to setup and debug.

#+BEGIN_SRC emacs-lisp :tangle export-org-section :shebang #!/bin/sh
:;exec emacs -batch  -l ~/Dropbox/kitchingroup/jmax/init.el -l "$0" "$@"

;; usage: export-org-section section-id org-file

;; now goto, narrow and export the section
(let ((section-id (pop command-line-args-left))
      (org-file (pop command-line-args-left)))
  (print (format "Opened %s" org-file))
  (find-file (expand-file-name org-file))
  (org-open-link-from-string (format "[[#%s]]" section-id))
  (org-narrow-to-subtree)
  (org-latex-export-to-pdf)
)
#+END_SRC


#+BEGIN_SRC sh :results silent
rm -f blog.pdf
./export-org-section sec-2 blog.org
open blog.pdf
#+END_SRC

I adapted this from here:
http://kitchingroup.cheme.cmu.edu/blog/2014/08/06/Writing-scripts-in-Emacs-lisp/

and here:
http://kitchingroup.cheme.cmu.edu/blog/2014/08/11/Using-org-mode-outside-of-Emacs-sort-of/

j

Alan Schmitt writes:

> On 2015-02-05 08:27, "Charles C. Berry" <ccberry@ucsd.edu> writes:
>
>> On Thu, 5 Feb 2015, Alan Schmitt wrote:
>>
>>> Hello,
>>>
>>> I'm teaching a class where I have a big monolithic file for all the
>>> lectures. Right now I export each lecture as a subtree from the file
>>> itself, but I would like to do it from a Makefile. Is it possible to
>>> export a subtree from the command line? if so, how do I specify the
>>> subtree that I want?
>>
>> Use an ID property for the subtree.
>>
>> A small *.el file can set prereqs, find the subtree from the ID, and
>> call up the exporter.
>>
>> `make test' does something like this. If you look at
>> testing/lisp/test-ob.el, testing/examples/babel.org, and the
>> testing/*.el files you can see some of this in action.
>
> Thanks a lot for the suggestion, I'll give it a try.
>
> Alan

--
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

  reply	other threads:[~2015-02-08  0:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-05 12:13 export subtree from the command line Alan Schmitt
2015-02-05 16:27 ` Charles C. Berry
2015-02-06 12:01   ` Alan Schmitt
2015-02-08  0:55     ` John Kitchin [this message]
2015-02-09 12:01       ` Alan Schmitt

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=m2vbjdmdbp.fsf@andrew.cmu.edu \
    --to=jkitchin@andrew.cmu.edu \
    --cc=alan.schmitt@polytechnique.org \
    --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).