emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Charles Millar <millarc@verizon.net>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: #+INCLUDE causes error when it attmepts to expand a LaTeX macro in source block
Date: Sun, 08 Dec 2019 09:46:46 +0100	[thread overview]
Message-ID: <87tv6btdah.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <a80aef16-88f1-8e6a-d56c-526eadd2aea0@verizon.net> (Charles Millar's message of "Sat, 7 Dec 2019 22:07:27 -0500")


Charles Millar <millarc@verizon.net> writes:

> In my init file I have
> (setq org-confirm-babel-evaluate nil)

This is totally unrelated to inclusion, see below.

> File "A" is attached as an org file. I evaluate the source blocks (C-c 
> C-v s), the table is generated and then I export it to PDF. The source 
> blocks do not evaluate during export.
> In file B I have
> #+INCLUDE: "/path/to/FileA::*SCHEDULE A1112"
> When I attempt to export File B to PDF/LaTeX the following error occurs
> Debugger entered--Lisp error: (error "Undefined Org macro: cmhfill; 
> aborting")
>    signal(error ("Undefined Org macro: cmhfill; aborting"))
>    error("Undefined Org macro: %s; aborting" "cmhfill")


> Also, please note that the cmhfill macro is in the table headings.

This is the problem, IMO.

> Is this an error, i.e. the #+INCLUDE does not honor the setting in my 
> init file?

Generally speaking, INCLUDE does not honor any Babel related setting
because inclusion happens before almost anything else (e.g., Babel)
during the export process.

But I don't think this is related to your issue.

> Is there a header or property setting for File B to prevent the exporter 
> from evaluating the source blocks when executing through an #+INCLUDE, 
> more particularly to prevent the attempted macro expansion within the 
> source blocks?

Org does not expand within source blocks. It tried to expand macro in
your table header, but cannot find the macro definitions.
> Both File A and File B had identical LaTeX settings, i.e. the macro was 
> defined in both files.

Where is it defined? I cannot see it.


Nicolas Goaziou

      reply	other threads:[~2019-12-08  8:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <a80aef16-88f1-8e6a-d56c-526eadd2aea0.ref@verizon.net>
2019-12-08  3:07 ` #+INCLUDE causes error when it attmepts to expand a LaTeX macro in source block Charles Millar
2019-12-08  8:46   ` Nicolas Goaziou [this message]

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:

  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=87tv6btdah.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=millarc@verizon.net \


* 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


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