Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
BibTeX Reference Completion Crashes with "Can't open file tmpfile.bbl" #762
Hello @lervag! Thanks for developing this plugin. As you know, I use it on a regular basis. I updated my
Here are the relevant settings from my
Please note that I have not yet reproduced this defect with a minimal
I am currently using the following version of vim:
I have the following content in my
At the outset, I acknowledge that all of these settings may no longer be needed in order to correctly run vimtex. Also, I suspect that these issues are not related to the error that I am experiencing. But, with that said, I always see the error when I try to complete references with this
I would also have the following minimal.bib file:
Finally, the error always manifests itself in roughly the following fashion. First, I will start typing
If I look in the file system, I will indeed notice that the
Of course, I am very far from an expert when it comes to understanding the codebase of vimtex. However, it seems like the source code may have a race condition in it. That is, the
Is it possible that the recent changes to the plugin are connected to this issue? Is there any other information that you need from me to support your reproduction of the problem? Overall, it would be awesome if you can investigate this matter and, if it is a problem, suggest a workaround for me or implement a fix in the main system.
Thanks again for this plugin and for taking the time to investigate this matter!
First a comment on your vimtex settings. There have been some pretty large updates the last couple of weeks. Your vimtex settings should be equivalent to these updated settings:
let g:vimtex_fold_enabled = 0 let g:vimtex_quickfix_open_on_warning = 0 let g:vimtex_index_show_help = 0 let g:vimtex_view_method = 'mupdf' let g:vimtex_view_mupdf_options = '-r 288'
Also, you should not need to use an autocmd to set the omnicompletion, since vimtex already does this for you.
Now, to the issue: I've made some pretty large updates to how vimtex runs external processes, and this issue is related to that. I remembered to test the completion earlier, but not for the most recent updates. Your minimal working example is reproducible, and I think I will have this fixed pretty soon.
@andymass There is not particular reason. However, it should not matter, since
Sorry for the inconvenience. A lot of the recent changes have been refactoring and API changes in order to make it easier/possible to implement some new features, e.g. other compiler backends (e.g. latexrun, see #651), other backends for error parsing, and supporting the new jobs API in Vim/neovim.
Hello @lervag! Thanks for fixing this issue. I am writing to confirm that it is resolved. I have edited several multiple-file papers in LaTeX in the past few days and I have not had any problems in completing the references. Again, thanks for your commitment to the development of vimtex!
Great, thanks for letting me know! Den man. 10. apr. 2017, 03.58 skrev Gregory M. Kapfhammer < email@example.com>:…
Hello @lervag <https://github.com/lervag>! Thanks for fixing this issue. I am writing to confirm that it is resolved. I have edited several multiple-file papers in LaTeX in the past few days and I have not had any problems in completing the references. Again, thanks for your commitment to the development of vimtex! — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#762 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA898imTQTFfpR2Y8KRE8eSzFWK2MXVfks5ruYyrgaJpZM4M1DlG> .