emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Matt Lundin <mdl@imapmail.org>
To: Nick Dokos <ndokos@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Possible to use src block to generate org headlines for export?
Date: Tue, 22 Jul 2014 21:35:55 -0500	[thread overview]
Message-ID: <8738dshkdw.fsf@fastmail.fm> (raw)
In-Reply-To: <87wqb4amqb.fsf@gmail.com> (Nick Dokos's message of "Tue, 22 Jul 2014 21:27:08 -0400")

Nick Dokos <ndokos@gmail.com> writes:
>>
>> In short, is there a more graceful and export-friendly way to use babel
>> to generate org headlines for export? Or is there an easy way to get the
>> export backend to delete the opening part of the drawer (i.e.,
>> :RESULTS:)?
>>
>> Any advice would be greatly appreciated. 
>>
>
> No solace for your pain alas.  See
> http://thread.gmane.org/gmane.emacs.orgmode/88557
>
> My suggestion (as it was for Ronald, except that he had already rejected
> it :-) ) would be to use raw: you lose the idempotency of results
> production, but I don't know of any other problems.

Thanks for the link. My ignorance of it shows how far behind I am on
orgmode ML reading!

I agree with Nicolas's argument that only headlines can contain
headlines.

That said, having the ability to generate org copy for export also seems
useful.

I wonder whether org-babel might take advantage of COMMENT headlines for
org output: E.g.

* COMMENT Here beginneth the results for code block named "do-some-magic"
* COMMENT Here endeth the results for code block named "do-some-magic"

Obviously, this could wreak havoc on ones outline structure, so some
extra magic would be needed to set the correct headline level.

However, since the headlines I'm generating are always at the end of the
file, I've hacked my way to a solution with the following:

--8<---------------cut here---------------start------------->8---
#+BEGIN_SRC emacs-lisp :exports none :results none
  (save-excursion
    (goto-char (point-min))
    (while (re-search-forward "#\\+RESULTS: generate-blog-summary" nil t)
      (beginning-of-line)
      (delete-region (point) (point-max))))
#+END_SRC

#+NAME: generate-blog-summary
#+BEGIN_SRC perl :exports results :results output org raw
  print "* Headline One\n";
  print "* Headline Two\n";
  print "* Headline Three\n";
#+END_SRC
--8<---------------cut here---------------end--------------->8---

Thus, each time I export, the emacs-lisp snippet nicely deletes the old
results, making space for the new ones. 

Let's hope the real blog (when I get around to publishing it) is more
interesting than the example above. ;)

Best,
Matt

  reply	other threads:[~2014-07-23  2:36 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-22 23:52 Possible to use src block to generate org headlines for export? Matt Lundin
2014-07-23  1:27 ` Nick Dokos
2014-07-23  2:35   ` Matt Lundin [this message]
2014-07-23  2:46     ` Matt Lundin
2014-07-23 13:42     ` Brett Viren
2014-07-23 15:17       ` Matt Lundin
2014-07-23 16:06         ` Charles Berry
2014-07-23 17:07           ` Matt Lundin
2014-07-24  1:51           ` Nick Dokos
2014-07-24 10:21             ` Andreas Leha
2014-07-25  8:31               ` Nicolas Goaziou
2014-07-25 13:05                 ` Andreas Leha
2014-07-25 13:23                   ` Nicolas Goaziou
2014-07-25 13:39                     ` Andreas Leha
2014-07-25 14:26                       ` Thorsten Jolitz
2014-07-25 16:08                       ` Nicolas Goaziou
2014-07-26  0:26                         ` Andreas Leha
2014-07-26  8:07                           ` Nicolas Goaziou
2014-07-26 19:47                             ` Andreas Leha
2014-07-24 18:40             ` Charles Berry
2014-07-24 19:41               ` Nick Dokos
2014-07-23 19:53         ` Brett Viren
2014-07-23 20:42           ` Matt Lundin
2014-07-24 22:05             ` Brett Viren
2014-07-23 16:09     ` Rick Frankel

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=8738dshkdw.fsf@fastmail.fm \
    --to=mdl@imapmail.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=ndokos@gmail.com \
    /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).