emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Alan Schmitt <alan.schmitt@polytechnique.org>
To: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: problem with call lines with post block that are not exported (elpa org)
Date: Tue, 01 Apr 2014 15:51:57 +0200	[thread overview]
Message-ID: <m2ob0lcg3m.fsf@polytechnique.org> (raw)

Hello,

I'm writing a paper with some colleagues for a conference, and we've
just stumbled on a strange bug. My colleague is using org from elpa, and
is having the problem, whereas I'm compiling using a very current org
version and everything works for me.

The problem is as follows.

Given this org file (exp.org):

--8<---------------cut here---------------start------------->8---
#+options: toc:nil
#+property: results drawer

#+name: fetch
#+BEGIN_SRC emacs-lisp :results raw :var f="foo" :exports none
f
#+END_SRC

#+name: wrap
#+BEGIN_SRC emacs-lisp :var text="" :results raw :exports none
(concat "#+BEGIN_EXAMPLE\n" text "\n#+END_EXAMPLE")
#+END_SRC

* Test
  :PROPERTIES:
  :post:     wrap(text=*this*)
  :END:

Hello world

#+call: fetch("testing")
--8<---------------cut here---------------end--------------->8---

and this initialization file (exp_init.el):

--8<---------------cut here---------------start------------->8---
(setq emacsd-dir "~/.emacs.d/")

(package-initialize)
(require 'org-loaddefs)

(require 'ox-html)

(setq org-confirm-babel-evaluate nil)
--8<---------------cut here---------------end--------------->8---

running this command

emacs --batch -Q -l exp_init.el exp.org -f org-html-export-to-html

yields in my colleague's case the following:

> Loading vc-git...
> executing Emacs-Lisp code block (fetch)...
>
> (f (quote "testing"))
>
> "testing"
> executing Emacs-Lisp code block...
>
> (results (quote "testing"))
> Reference 'wrap' not found in this buffer

The same command works for me (for completeness's sake, here is my
configuration file):

--8<---------------cut here---------------start------------->8---
(setq emacsd-dir "~/.emacs.d/")

(add-to-list 'load-path (concat emacsd-dir "org/emacs/site-lisp/org"))

(require 'ox-html)

(setq org-confirm-babel-evaluate nil)
--8<---------------cut here---------------end--------------->8---

He's using this org version:
Org-mode version 8.2.5h (8.2.5h-94-g91175a-elpa @ /Users/pmaksimo/.emacs.d/elpa/org-20140331/)
updated yesterday.

My questions are:
- is there a bug in the ELPA version of org mode?
- is there a workaround? We tried ":exports results" instead of
":exports none" but the blocks are not exported in that case.

Thanks,

Alan

             reply	other threads:[~2014-04-01 13:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-01 13:51 Alan Schmitt [this message]
2014-04-17 13:51 ` problem with call lines with post block that are not exported (elpa org) Bastien
2014-04-17 14:40   ` 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=m2ob0lcg3m.fsf@polytechnique.org \
    --to=alan.schmitt@polytechnique.org \
    --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).