From: Justin Silverman <jsilve24@gmail.com>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: bug: wrong-type-argument when trying export to pdf.
Date: Wed, 12 Oct 2022 11:11:23 -0400 [thread overview]
Message-ID: <874jw9jcsh.fsf@gmail.com> (raw)
In-Reply-To: <8735btu1ig.fsf@localhost>
[-- Attachment #1: Type: text/plain, Size: 1195 bytes --]
Well, rm -rf .emacs.d/straight/ followed by repulling and rebuilding seemed to fix things.
I am surprised that I still saw the same problem with emacs -Q but my simple-config.el did use straight. Perhaps straight in simple-config.el just ended up using the same build files that were corrupted...
Anyways I guess mark this one frustrating but solved.
Justin
Ihor Radchenko <yantar92@gmail.com> writes:
> Justin Silverman <jsilve24@gmail.com> writes:
>
>> I am having a problem and getting a wrong-type-argument error when
>> trying to run `org-beamer-export-to-pdf' on the attached file
>> `debug.org' (see backtrace below). The problem also occurs when
>> running `org-latex-export-to-pdf'.
>> ...
>> Backtrace:
>>
>> Debugger entered--Lisp error: (wrong-type-argument number-or-marker-p nil)
>> jit-lock--run-functions(1218 1284)
>> jit-lock-fontify-now(1218 #<marker at 1284 in L4-6_CoDA.org<2>>)
>> #<subr font-lock-ensure>(1218 #<marker at 1284 in L4-6_CoDA.org<2>>)
>> polymode-inhibit-during-initialization(#<subr font-lock-ensure> 1218 #<marker at 1284 in L4-6_CoDA.org<2>>)
>
> The backtrace shows that you are using polymode. Does the problem
> persist without polymode?
prev parent reply other threads:[~2022-10-12 15:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-11 19:08 bug: wrong-type-argument when trying export to pdf Justin Silverman
2022-10-12 4:08 ` Ihor Radchenko
2022-10-12 14:19 ` Justin Silverman
2022-10-12 15:11 ` Justin Silverman [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:
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=874jw9jcsh.fsf@gmail.com \
--to=jsilve24@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@gmail.com \
/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).