When working on a kile project with a master document and subdocuments included via subfiles citation completion does not work with any but the one file that Kile associates with the bibliography. By the way in which subfiles works the master document will have the \bibliography{blah.bib} line, and as such citation completion will not work on any other file included in the project As a workaround the solution from http://tex.stackexchange.com/questions/41462/auto-completion-for-citation-in-kile-using-biblatex was attempted in one of the subfiles, in which case (at random) the bibliography file was associated with the subfile and citation completion worked. Now it no longer workes in the master file. Kile helpfully makes this explicit in the project view by showing which file has which files included/associated with it. Reproducible: Always Steps to Reproduce: 1. start a project with a master document including the subfiles package 2. create a secondary document, the subfile according the subfile documentation 3. include a bibliography in the master document 4. observe that citation completion does not work in the sub file Actual Results: See description. Expected Results: That citation completion works across all files in a project. That kile is not 'random' in the way it determines which file has which includes associated with it (when multiple files include the same file, such as with a bibliography) MWE: Master document, Thesis.tex \documentclass[a4paper,twoside]{scrbook} \usepackage{biblatex} \bibliography{Thesis.bib} \usepackage{subfiles} \newbool{master} \begin{document} \setbool{master}{true} %Set the 'master' boolean flag for the ifbool directive in the subordinate files \subfile{Chapter1} \end{document} Subile document, Chapter1.tex \documentclass[Thesis]{subfiles} \begin{document} \cite{NOT COMPLETED} \end{document}
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. Thank you for helping us make KDE software even better for everyone!
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!