emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: John Kitchin <jkitchin@andrew.cmu.edu>
To: Emacs Orgmode <emacs-orgmode@gnu.org>
Subject: org-latex-pdf-process as a lisp function?
Date: Sun, 30 Apr 2023 10:27:49 -0400	[thread overview]
Message-ID: <CALEYq0_DsD2Ofw1XG4=EbEbJ9nr5_jWoU1+7-kUkmZF=ELhd5Q@mail.gmail.com> (raw)

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

The documentation for org-latex-pdf-process says that it can be a list of
strings, or a lisp function.

I have used a function for a long time, but recently it seems to have
broken. Now I get an error in org-compile-file. The issue comes in the
first line where (commands (org-compile-file-commands source process ext
spec err-msg) binds my function to commands, and later that is expected to
be a list, but it is a function now. I think this probably occurred in
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/lisp/org-macs.el?id=b29f77241681abd6fb12de3b7e26c009cb28c63d

In org-compile-file-commands, I think this line

 ((pred functionp) process)

should instead be

((pred functionp) (list process))

that seems to make it work for me.

Org mode version 9.7-pre (release_9.6.4-337-geaf274

-- 
John

-----------------------------------
Professor John Kitchin (he/his)
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
https://kitchingroup.cheme.cmu.edu
https://pointbreezepubs.gumroad.com/ pycse bookstore

[-- Attachment #2: Type: text/html, Size: 1765 bytes --]

             reply	other threads:[~2023-04-30 14:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-30 14:27 John Kitchin [this message]
2023-04-30 16:44 ` org-latex-pdf-process as a lisp function? Ihor Radchenko
2023-04-30 23:56   ` John Kitchin

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='CALEYq0_DsD2Ofw1XG4=EbEbJ9nr5_jWoU1+7-kUkmZF=ELhd5Q@mail.gmail.com' \
    --to=jkitchin@andrew.cmu.edu \
    --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).