As far as I have been able to track down the issue, it looks like the culprit (so to speak) is the fact that including doesn’t record the directory of the included file.
Could you confirm whether using absolute names in the #+bibliography: lines is a valid workaround? Thx /PA PS: valid in the sense that it helps generating valid LaTeX and you can use the bib file to insert refs… Enviado desde mi iPhone > El 19 may 2026, a las 20:47, Marvin Gülker <[email protected]> escribió: > > Antero Mejr via "General discussions about Org-mode." > <[email protected]> writes: > >> Pedro Andres Aranda Gutierrez <[email protected]> writes: >> >>> If I understand you correctly, you are importing the bibliography >>> twice. >>> >>> You dont need to do that. >> >> If I don't import the bibliography in the org file in a subdirectory, >> then org-cite-insert completions don't work, so I can't add citations >> to the org file in the subdirectory. > > It is not only a problem with directories. There seems to be a little > more amiss with bibliographies in #+include-d files. I have all the org > files for my doctoral thesis in a single directory, with the main file > using #+include on the other ones. If I do not place the #+bibliography: > lines in an included org file, all citations in that file will be > flagged as invalid, i.e., painted in red color, even though the toplevel > file contains the #+bibliography: statement. The export process itself > would run fine, though. > > I do not have the completion problem, because I use Ebib to insert my > citations, but this flagging annoyed me enough to put the > #+bibliography: lines into all my .org files. > > Since my .bib files also either reside in the same directory or are > referenced by absolute pathes, I however did not run into the export > problem the OP had. > > I also use citeproc.el for citation handling and do not forward to > LaTeX/Bib(La)tex. > > -- > Dipl.-Jur. M. Gülker | https://mg.guelker.eu | PGP: Siehe Webseite > Stade, Deutschland | [email protected] | O< >
