Sorry that was my bad, the backtrace was from my own config not the simple-config.el that I provided. Here is the backtrace from the simple-config.el that shows that the problem persists even without polymode. (still, thanks for pointing out that I had polymode activated, that was a mistake that I will fix in my personal config) Debugger entered--Lisp error: (wrong-type-argument number-or-marker-p nil) jit-lock--run-functions(1157 1223) jit-lock-fontify-now(1157 #>) font-lock-ensure(1157 #>) org-table-align() org-babel-insert-result(((0.333333333333333) (0.333333333333333) (0.333333333333333)) ("value" "replace") ("R" "w1 <- c(1, 1, 1) \nw2 <- c(1, 1, 5) \n\nx1 <- w1/sum(..." ((:colname-names) (:rowname-names) (:result-params "value" "replace") (:result-type . value) (:results . "value replace") (:exports . "both") (:cache . "no") (:hlines . "no") (:noweb . "no") (:session . "*R*") (:tangle . "no")) "" nil 1011 "(ref:%s)") nil "R" (0 0 258514 765000)) org-babel-execute-src-block(nil ("R" "w1 <- c(1, 1, 1) \nw2 <- c(1, 1, 5) \n\nx1 <- w1/sum(..." ((:colname-names) (:rowname-names) (:result-params "replace" "value") (:result-type . value) (:results . "replace value") (:exports . "both") (:tangle . "no") (:session . "*R*") (:noweb . "no") (:hlines . "no") (:cache . "no")) "" nil 1011 "(ref:%s)")) org-babel-exp-results(("R" "w1 <- c(1, 1, 1) \nw2 <- c(1, 1, 5) \n\nx1 <- w1/sum(..." ((:cache . "no") (:colname-names) (:exports . "both") (:hlines . "no") (:noweb . "no") (:result-params "replace" "value") (:result-type . value) (:results . "replace value") (:rowname-names) (:session . "*R*") (:tangle . "no")) "" nil 1011 "(ref:%s)") block nil "2da1507400b1866895fab4840062db146ee4de1e") org-babel-exp-do-export(("R" "w1 <- c(1, 1, 1) \nw2 <- c(1, 1, 5) \n\nx1 <- w1/sum(..." ((:cache . "no") (:colname-names) (:exports . "both") (:hlines . "no") (:noweb . "no") (:result-params "replace" "value") (:result-type . value) (:results . "replace value") (:rowname-names) (:session . "*R*") (:tangle . "no")) "" nil 1011 "(ref:%s)") block "2da1507400b1866895fab4840062db146ee4de1e") org-babel-exp-src-block((src-block (:language "R" :switches nil :parameters ":exports both :results value :session \"*R*\"" :begin 1011 :end 1146 :number-lines nil :preserve-indent nil :retain-labels t :use-labels t :label-fmt nil :value " w1 <- c(1, 1, 1) \n w2 <- c(1, 1, 5) \n\n x1 <- w..." :post-blank 1 :post-affiliated 1011 :mode planning :granularity element :cached nil :parent (section (:begin 1011 :end 1223 :contents-begin 1011 :contents-end 1223 :robust-begin 1011 :robust-end 1221 :post-blank 0 :post-affiliated 1011 :mode section :granularity element :cached nil :parent (headline (:raw-value "Spurious Conclusions" :begin 986 :end 1223 :pre-blank 1 :contents-begin 1011 :contents-end 1223 :robust-begin 1013 :robust-end 1221 :level 2 :priority nil :tags nil :todo-keyword nil :todo-type nil :post-blank 0 :footnote-section-p nil :archivedp nil :commentedp nil :post-affiliated 986 :title (...) :parent (org-data ...) :cached t :org-element--cache-sync-key (0 . 986))) :org-element--cache-sync-key (0 . 1010))) :org-element--cache-sync-key (0 . 1011)))) org-babel-exp-process-buffer() org-export-as(beamer nil nil nil nil) org-export-to-buffer(beamer "*Org BEAMER Export*" nil nil nil nil nil #) org-beamer-export-as-latex() funcall-interactively(org-beamer-export-as-latex) command-execute(org-beamer-export-as-latex record) execute-extended-command(nil "org-beamer-export-as-latex" nil) funcall-interactively(execute-extended-command nil "org-beamer-export-as-latex" nil) command-execute(execute-extended-command) Ihor Radchenko writes: > Justin Silverman 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 #>) >> #(1218 #>) >> polymode-inhibit-during-initialization(# 1218 #>) > > The backtrace shows that you are using polymode. Does the problem > persist without polymode?