emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: wlharvey4@mac.com
To: emacs-orgmode@gnu.org
Subject: Seeking identical output for export
Date: Tue, 7 Jan 2020 10:22:21 -0800	[thread overview]
Message-ID: <20CA6217-EECB-48CF-B17B-D933CD0ABD51@mac.com> (raw)


I am seeking to find the right way to obtain identical output when exporting an Org file into texinfo using the export menu from within the Org file as well as from a Makefile using an Emacs batch script.

Currently I am using (org-export-to-file ‘texinfo “<file-name>”) from within a Makefile.  This produces a file that has a few differences from that produced by using the export menu 'C-c C-e i t’.

The batch script is:

 emacs -Q --batch --eval '\
	  (progn \
	    (require '\''org) \
	    (require '\''ob) \
	    (require '\''ox-texinfo) \
	    (require '\''ob-shell) \
	    (setq org-confirm-babel-evaluate nil) \
	    (find-file "$(ORG)") \
	    (org-export-to-file '\''texinfo "$(TEXI)"))'

The differences include:
- the {{{date}}} macro is empty when created with the Makefile
  e.g. subtitle Version 0.0.0 
         subtitle Version 0.0.0 2020-01-07 10:05

	The Org source is:
	#+subtitle {{{version}}} {{{date}}}
	#+macro:version Version 0.0.0

	The version macro is expanded but not the date macro.

- references are random strings rather than similar to the #+name when created with the Makefile
  e.g. float Listing,orge1fba27
         float Listing,get-org-filename

- periods at the end of variable references
  e.g. ... exists: $NEWDIR.
         ...exists: $NEWDIR@.

Thank you for any suggestions.


             reply	other threads:[~2020-01-07 18:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-07 18:22 wlharvey4 [this message]
2020-01-08  7:20 ` Seeking identical output for export Diego Zamboni

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=20CA6217-EECB-48CF-B17B-D933CD0ABD51@mac.com \
    --to=wlharvey4@mac.com \
    --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).