Hi again,
If I understand you correctly, you are importing the bibliography twice.
You don’t need to do that.
When #+include: is used, the header in the ‘main’ file will be the anchor for
producing the LaTeX.
It’s the same as when you use
\input{}
Or
\include{}
In LaTeX.
I normally \include{} the text for my papers from the main tex template file to
be able to reuse them in other documents if necessary.
In this scheme, the main TeX file does the bibliography management and the
\include{}’d tex files just use it.
I do the same in Org:
I split between
A main.org <http://main.org/> file with the headers and .org files with
contents which I #+include.
I hope this and the previous example were helpful.
Best, /PA
> El 14 may 2026, a las 8:42, Pedro Andres Aranda Gutierrez <[email protected]>
> escribió:
>
> Hi
>
> It might be helpful if you were able to share a minimum working example (MWE).
>
> I’m not able to reproduce…my MWE
>
> —— tmp/testbib/test.org <http://test.org/> ——
> #+LATEX_COMPILER: pdflatex
> #+LATEX_CLASS: article
>
> #+cite_export: biblatex
> numeric,backend=biber,sorting=none,isbn=false,doi=false,url=true
> #+BIBLIOGRAPHY: ../s13.bib
>
> * Testing the bibliography statement
>
> I wanted to read the NFV whitepaper [cite:@nfv-whitepaper-1], but didn't have
> to
> do so.
>
> #+print_bibliography:
> —— tmp/s13.bib — —
> @Online{nfv-whitepaper-1,
> author = {Andy Reid and Diego López et.al.},
> editor = {ETSI},
> title = {Network Functions Virtualisation: Introductory White
> Paper},
> year = {2012},
> ALTdate = {date},
> url = {https://portal.etsi.org/NFV/NFV_White_Paper.pdf},
> month = {10},
> OPTnote = {note},
> annote = {Last visit: 9 feb 2021},
> }
> — — end — —
>
> Output of the relevant parts as above:
>
> — — start — —
> \usepackage[style=numeric,backend=biber,sorting=none,isbn=false,doi=false,url=true]{biblatex}
> \addbibresource{../s13.bib}
> \begin{document}
>
> \tableofcontents
>
> \section{Testing the bibliography statement}
> \label{sec:orgeefcc99}
>
> I wanted to read the NFV whitepaper \autocite{nfv-whitepaper-1}, but didn't
> have to
> do so.
>
> \printbibliography
> \end{document}
> — — end — —
>
> Output when suppressing cite_export
>
> — — start — —
> \begin{document}
>
> \tableofcontents
>
> \section{Testing the bibliography statement}
> \label{sec:org3385616}
>
> I wanted to read the NFV whitepaper (Andy Reid and Diego López et.al., 2012),
> but didn't have to
> do so.
>
> \noindent
> Andy Reid and Diego López et.al. (2012). \emph{Network Functions
> Virtualisation: Introductory White Paper}.
> \end{document}
> — — end — —
>
> — — My emacs — —
> (message “Org is %s" org-version)
> "Org is 9.8.3"
> (message "Emacs is %s" emacs-version)
> "Emacs is 31.0.60"
> — — end — —
>
> With minimal config to manage Mac keys, else like emacs -Q
>
> Best, /PA
>
>> El 14 may 2026, a las 5:04, Antero Mejr via General discussions about
>> Org-mode. <[email protected]> escribió:
>>
>>
>> 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.
>> ------------------------------------------------------------------------
>>
>> If I have a main org file with:
>>
>> #+bibliography: ref.bib
>>
>> and then an org file in a subdirectory that gets added to the main file
>> using #+include: with this:
>>
>> #+bibliography: ../ref.bib
>>
>> the exported latex with have:
>>
>> \bibliography{../ref,ref}
>>
>> which is wrong and causes a latex error. There should be a way to either
>> suppress the ../ref from getting exported, or link a .bib file for
>> citation tab-completions without adding it to the exported latex.
>>
>> Emacs : GNU Emacs 31.0.50 (build 2, aarch64-unknown-linux-gnu, GTK+ Version
>> 3.24.49, cairo version 1.18.4)
>> of 2026-04-23
>> Package: Org mode version 9.8.3 (release_9.8.3 @
>> /usr/local/share/emacs/31.0.50/lisp/org/)
>>
>
