From: Richard Stanton <rhstanton@berkeley.edu>
To: orgmode <emacs-orgmode@gnu.org>
Subject: [BUG] New error: (void-function org-url-p) when exporting to LaTeX [9.4.6 (9.4.6-gc5573b @ /Users/stanton/.emacs.d/straight/build/org/)]
Date: Wed, 26 May 2021 15:53:14 -0700 [thread overview]
Message-ID: <DF08D8C9-DE4F-4228-A001-EF08B2062E02@berkeley.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 2111 bytes --]
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
https://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org mailing list.
------------------------------------------------------------------------
Everything worked fine until yesterday, but today when I try to export an org file that contains the line
#+SETUPFILE: https://fniessen.github.io/org-html-themes/org/theme-readtheorg.setup <https://fniessen.github.io/org-html-themes/org/theme-readtheorg.setup>
I get the following error:
Debugger entered--Lisp error: (void-function org-url-p)
org-url-p("https://fniessen.github.io/org-html-themes/org/the...")
org--collect-keywords-1(("SETUPFILE" "FILETAGS" "TAGS" "ARCHIVE" "CATEGORY" "COLUMNS" "CONSTANTS" "LINK" "OPTIONS" "PRIORITIES" "PROPERTY" "SEQ_TODO" "STARTUP" "TODO" "TYP_TODO") ("ARCHIVE" "CATEGORY" "COLUMNS" "PRIORITIES") nil nil nil)
org-collect-keywords(("FILETAGS" "TAGS" "ARCHIVE" "CATEGORY" "COLUMNS" "CONSTANTS" "LINK" "OPTIONS" "PRIORITIES" "PROPERTY" "SEQ_TODO" "STARTUP" "TODO" "TYP_TODO") ("ARCHIVE" "CATEGORY" "COLUMNS" "PRIORITIES"))
org-set-regexps-and-options()
org-mode()
org-export--prepare-file-contents("/Users/stanton/.org/setup" nil 0 1 1 #<hash-table equal 0/65 0x1fe65e6c9285> "/Users/stanton/teaching/MFE230I/mfe230i.org")
org-export-expand-include-keyword()
org-export-as(latex nil nil nil (:output-file "mfe230i.tex"))
org-export-to-file(latex "mfe230i.tex" nil nil nil nil nil #f(compiled-function (file) #<bytecode 0x1fe65e28d06d>))
org-latex-export-to-pdf(nil nil nil nil)
org-export-dispatch(nil)
funcall-interactively(org-export-dispatch nil)
call-interactively(org-export-dispatch nil nil)
command-execute(org-export-dispatch)
Thanks for any suggestions.
Emacs : GNU Emacs 27.2 (build 1, x86_64-apple-darwin20.3.0, Carbon Version 164 AppKit 2022.3)
of 2021-04-06
Package: Org mode version 9.4.6 (9.4.6-gc5573b @ /Users/stanton/.emacs.d/straight/build/org/)
[-- Attachment #2: Type: text/html, Size: 3542 bytes --]
next reply other threads:[~2021-05-26 22:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-26 22:53 Richard Stanton [this message]
2021-05-27 6:56 ` [BUG] New error: (void-function org-url-p) when exporting to LaTeX [9.4.6 (9.4.6-gc5573b @ /Users/stanton/.emacs.d/straight/build/org/)] Tim Cross
2021-05-27 7:19 ` Tim Cross
[not found] <mailman.45.1622131210.31880.emacs-orgmode@gnu.org>
2021-05-27 17:12 ` Richard Stanton
2021-05-28 0:00 ` Tim Cross
2021-05-29 6:41 ` Ihor Radchenko
2021-05-29 7:18 ` Richard Stanton
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=DF08D8C9-DE4F-4228-A001-EF08B2062E02@berkeley.edu \
--to=rhstanton@berkeley.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).