11:02:07,659+0100 FATAL initexmf - Source: Libraries\MiKTeX\Core\win\winFile.
11:02:07,659+0100 FATAL initexmf - Windows API error 32: The process cannot access the file because it is being used by another process. 11:02:07,626+0100 INFO initexmf - starting: MiKTeX Configuration Utility (MiKTeX 2.9) If it doesn't show up, click the TeX icon on the left horizontal menu, and click on 'View LaTeX PDF' under the COMMANDS palette.
Now it should display the PDF view of your latex document on the right side of the VS Code window. 11:01:56,274+0100 FATAL initexmf - Source: Libraries\MiKTeX\Core\win\winFile.cpp After saving the file, click on the magnifying glass icon on the top right corner. 11:01:56,274+0100 FATAL initexmf - Windows API error 32: The process cannot access the file because it is being used by another process. 11:01:56,242+0100 INFO initexmf - starting: MiKTeX Configuration Utility (MiKTeX 2.9) 11:01:56,093+0100 FATAL initexmf - Source: Libraries\MiKTeX\Core\win\winFile.cpp 11:01:56,093+0100 FATAL initexmf - Windows API error 32: The process cannot access the file because it is being used by another process. 11:01:56,061+0100 INFO initexmf - starting: MiKTeX Configuration Utility (MiKTeX 2.9) 11:01:25,618+0100 INFO initexmf - running: mkfntmap -verbose -admin 11:01:25,582+0100 INFO initexmf - starting: MiKTeX Configuration Utility (MiKTeX 2.9) 11:01:25,303+0100 INFO initexmf - starting: MiKTeX Configuration Utility (MiKTeX 2.9) 11:01:23,489+0100 INFO initexmf - Creating fndb for common root directory ("C:\Program Files (x86)\MiKTeX 2.9").
11:01:23,473+0100 INFO initexmf - Creating fndb for common root directory (C:\ProgramData\MiKTeX\2.9). 11:01:23,472+0100 INFO initexmf - Skipping user root directory (C:\Users\jonc\AppData\Local\MiKTeX\2.9). 11:01:23,472+0100 INFO initexmf - Skipping user root directory (C:\Users\jonc\AppData\Roaming\MiKTeX\2.9). That first log suggests there's a permissions error but I've not idea what file it has a problem with: 11:01:23,455+0100 INFO initexmf - starting: MiKTeX Configuration Utility (MiKTeX 2.9) Sorry, but C:\Program Files (x86)\MiKTeX 2.9\miktex\bin\miktex-pdftex.exe did not succeed.Ĭ:/Users/jonc/AppData/Local/MiKTeX/2.9/miktex/log/miktex-pdftex.log You may want to visit the MiKTeX project page ( ), if you The log file hopefully contains the information to get MiKTeX going again:Ĭ:/Users/jonc/AppData/Local/MiKTeX/2.9/miktex/log/initexmf.log Sorry, but "MiKTeX Configuration Utility" did not succeed. I installed the latest version of MikTex for Windows but every time I run it and select 'pdfLatex' from the drop-down and hit the green play button I get this message: A useful trick.I've created a basic Latex document based on an example I found online: \documentclass BTW that 'au' command in the vimrc will also load dictionaries for any other filetypes if you want. Then if I type the beginning of a latex command and hit 'tab' I will get a list of completions. vimrc file: set filetype onĪu FileType * exec("setlocal dictionary+=".$HOME."/.vim/dictionaries/".expand('')) What I did was copy this file into ~/.vim/dictionaries/ and renamed it 'tex' then I added these lines to my. This dictionary file is: ftplugin/latex-suite/dictionaries/dictionary in the vim-latex files. And I took the dictionary files from Vim-LaTeX so I have a ton of auto completion words to use. I also use SuperTab plugin for completions, which is great. The key mapping to start latexmk is the same as Vim-Latex's compile: '\ll' (that's lowercase LL). You also need the latexmk script somewhere on you PATH. Adding let g:LatexBox_latexmk_options = "-pvc -pdfps" And if you use a pdf viewer which refreshed changes (such as evince on Linux) you can see updates every time you change. tex file for changes, and then automatically compile for you.
Latexmk will sit in the background and watch your. I like LaTeX-Box so far because it used latexmk to compile, which is what I was using anyway. I, also used VIM-LaTeX for a while, but I didn't really like the key mappings, and it seemed a bit to heavyweight as Jeet described. I've just begun playing around with LaTeX-Box.