emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Charles Millar <millarc@verizon.net>
To: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: #+INCLUDE causes error when it attmepts to expand a LaTeX macro in source block
Date: Sat, 7 Dec 2019 22:07:27 -0500	[thread overview]
Message-ID: <a80aef16-88f1-8e6a-d56c-526eadd2aea0@verizon.net> (raw)
In-Reply-To: a80aef16-88f1-8e6a-d56c-526eadd2aea0.ref@verizon.net

[-- Attachment #1: Type: text/plain, Size: 1390 bytes --]


In my init file I have

(setq org-confirm-babel-evaluate nil)

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; 
   signal(error ("Undefined Org macro: cmhfill; aborting"))
   error("Undefined Org macro: %s; aborting" "cmhfill")

If I place a "#+HEADER: :eval no" in the source blocks in File A (after 
generating the table) File B will export the table to PDF. Also, please 
note that the cmhfill macro is in the table headings.

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

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?

Both File A and File B had identical LaTeX settings, i.e. the macro was 
defined in both files.

GNU Emacs 27.0.50 (build 8, x86_64-pc-linux-gnu, GTK+ Version 3.24.13) 
of 2019-12-07

Org mode version 9.3 (release_9.3-36-gbe7434 @ 

Charlie Millar

[-- Attachment #2: ForINCLUDE-email.org --]
[-- Type: text/plain, Size: 1294 bytes --]

#+begin_src rec :data somefile.rec :type Finance :fields AccountDate,Shares,Description,AccountAmount :sort AccountDate,Description :results silent
 (File = 'Estate' && AccountSchedule = 'A')
#+begin_src emacs-lisp :var table=SCHEDAP :exports results
  (setq table (cons 'hline table))
  (setq table (cons '("Date" "{{{cmhfill}}} Shares" " Description " "{{{cmhfill}}} Inventory{{{cm1space}}}Value") table))
  (setq table (append table '(("| |Total Schedule A"))))
  (setq table (append table '(("\n#+TBLFM: @>$>=vsum(@I$>..@>>$>);%.2f::"))))
#+ATTR_LATEX: :mode table :environment longtable :align  p{60pt}N{5}{3}p{275pt}N{8}{2}
| Date       | {{{cmhfill}}} Shares | Description      | {{{cmhfill}}} Inventory{{{cm1space}}}Value |
| 2018-03-18 |                      | Something        |                                   49645.59 |
| etc        |                      | etc              |                                    4878.51 |
|            |                      | Total Schedule A |                                   54524.10 |
#+TBLFM: @>$>=vsum(@I$>..@>>$>);%.2f:: |

       reply	other threads:[~2019-12-08  3:08 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 ` Charles Millar [this message]
2019-12-08  8:46   ` #+INCLUDE causes error when it attmepts to expand a LaTeX macro in source block Nicolas Goaziou

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=a80aef16-88f1-8e6a-d56c-526eadd2aea0@verizon.net \
    --to=millarc@verizon.net \
    --cc=emacs-orgmode@gnu.org \


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