Open chenyuewu opened 8 years ago
Is your E:
a network drive or otherwise resolvable to a UNC path? This might be getting bit by the same thing as #81...
E:
is on my local hard disk.
I guess it's the problem of atom itself. Another latex package atom-latex also breaks with the same issue after the update of atom.
When compiling outside of Atom, do you use the command above or another command? Does anything show up in any of the MiKTeX logs (usually in %AppData%\MiKTeX\2.9\logs
)?
I have the same question with chenyuewu. But I compile *.tex with texlive. It mess me up, and I can't find the answer in Google.
I have reinstalled texlive(2016 replaced 2015), then the problem was solved...
@blizzardwj: that seems like it might've been an altogether different issue.
I have the same question. My platform is ubuntu 16.04 with atom 1.11.2. texlive2016 Platform: linux; texpath: $PATH:/usr/texbin Setting PATH = /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:$PATH:/usr/texbin:$PATH:/usr/texbin:$PATH:/usr/texbin Processing file test_en.tex (test_en) in directory /home/agamemnon/workspace latexmk builder latexmk -cd -e -f -pdf -interaction=nonstopmode -synctex=1 "test_en.tex" Parsing /home/agamemnon/workspace/test_en.log Could not read log file!
but i can compile the same file successfully out side atom.
besides, it seems that latexmk generates no log file within atom
@agamemnon314: Again that looks like a different issue. In particular, your texpath
setting looks like it contains $PATH:/usr/texbin:$PATH:/usr/texbin:$PATH:/usr/texbin
. $PATH
isn't (currently) supported in the texpath
setting. Try adjusting that and see if it fixes things.
I've had the same issue. Setting either the TeX environment in the path or the texpath in the package settings in atom solved it. If you launch MikTeX's mo_admin.exe on Windows, you'll see a respective warning, if the path is not set correctly.
@elmewo and @ig0774, I have the same issue but in Ubuntu. Do you know how to make it works. You talked about changing the Path. Could you please show me more? Thank you.
@minhducpsc I was getting the same error and then realized I hadn't installed latexmk. After installing latexmk it works fine without having changed the default path.
My platform is windows 10 with atom 1.7.2.
Platform: win32; texpath:
Processing file foo.tex (foo) in directory E:\documents\foo
texify builder
texify -b -p --engine=pdftex --tex-option="--synctex=1" "foo.tex"
Parsing E:\documents\foo\foo.log
Could not read log file!
The problem is that no 'foo.log' is generated. If I compile this tex file outside atom with miktex, I can get thefoo.log
file and build with latextools in atom will not complain about the log file. However, building with latextools will not update the log file even if the tex file is modified. Thus, no change for the corresponding pdf file.Everything works fine in previous atom 1.6.2 or in miktex.