Hi Karthik and Timothy,
Recently I encountered a compatibility issue between org-cite and 
org-latex-preview. I am using the lastest version of org-latex-preview of the 
dev branch of tec/org-mode: My personal patches-in-progress branch of Org. See 
https://git.tecosaur.net/mirrors/org-mode/compare/main..tec/org-mode:dev. - 
Code by TEC. To be precise, if I want to export the org file with citation to a 
latex/pdf file, I will set 
```
#+cite_export: biblatex backend=biber style=alphabetic
```
This is one of the recommended approach in Org Manual to configuring the 
biblatex package parameters and works well when exporting to latex/pdf.
But the org-latex-preview will throw an error during executing 
`org-latex-preview--get-preamble'
```
Debugger entered--Lisp error: (wrong-type-argument listp "biblatex 
backend=biber style=alphabetic") org-cite-processor((:export-options nil 
:back-end #s(org-export-backend :name latex :parent nil :transcoders (... ... 
... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... 
... ... ... ... ...) :options (... ... ... ... ... ... ... ... ... ... ... ... 
... ... ... ... ... ... ... ... ... ... ... ... ... 
.......
org-export-process-features....
```
I try to figure this out. It appears that the `:cite-export' properties of 
export-info variable is set to be a string after parsing, and its default value 
is a list like `((latex biblatex) (t csl))'.
I don't know why such malformed value will lead to a right result during org 
exporting and and an error in org-latex-preview.
My temporary "solution" is to reset the :cite-export property manually in the 
beginning of function `org-export-process-features'.
```
(defun test/org-export-process-features (info)
"Install feature conditions/implementations in INFO, and resolve them.
See `org-export-detect-features' and 
`org-export-resolve-feature-implementations' for
more information on what this entails."
(plist-put info :cite-export '((latex biblatex) (t csl)))
.......
```
I'm not sure how to neatly tie all this together yet, and whether this is due 
to my incorrect usage or if it's a bug.
Thanks.
Yu Huang.

Reply via email to