First off, I really like LaTeXTools, best workflow I can think of for working with LaTeX 🎉!
I recently started working on a very specific system which lead me to use Microsoft Windows UNC (network paths) directly in TeX, like \\company.com/Data/Group Data/999 Temp/latex-company. This actually works fine in combination with MiKTeX on Windows 🏆 .
However the LaTeXTools log parser has trouble with these network paths. When mounting the network path as a folder, LaTeXTools is able to parse the log just fine.
The following files show the problem, the report.unc-network.log is the log file with network paths and the other one is with the path as a mounted folder. No other changes have been done between these two builds.
First off, I really like LaTeXTools, best workflow I can think of for working with LaTeX 🎉!
I recently started working on a very specific system which lead me to use Microsoft Windows UNC (network paths) directly in TeX, like
\\company.com/Data/Group Data/999 Temp/latex-company. This actually works fine in combination with MiKTeX on Windows 🏆 .However the LaTeXTools log parser has trouble with these network paths. When mounting the network path as a folder, LaTeXTools is able to parse the log just fine.
The following files show the problem, the
report.unc-network.logis the log file with network paths and the other one is with the path as a mounted folder. No other changes have been done between these two builds.Hope this makes it easy to add support for Microsoft Windows UNC network paths.
Thanks!