# Tag Info

0

Package graphics-def may be not istalled. Check this, it may work.

0

Change pdflatex to xelatex, it solves the problem for me.

0

I am having the same issue. This is the message: ! LaTeX Error: File `xetex.def' not found. Type X to quit or to proceed, or enter new name. (Default extension: def) Enter file name: ! Emergency stop.

2

If you pass \newcommand{\home}{$HOME} in the command line, then the shell will interpret the variable, but in a TeX file it would not work. You can use catchfile and kpsewhich that, I believe, also works in MiKTeX. \documentclass{article} \usepackage{catchfile} \CatchFileEdef{\home}{|"kpsewhich -var-value=HOME"}{\endlinechar=-1 } \begin{document} \... 1 I can't really believe that$HOME works, but on windows you can use something like this (to avoid problems with the backslash in pathes, one should print the path with another catcode table): \documentclass{article} % \usepackage{graphicx} %log all values of os.env: \directlua{for k, v in pairs( os.env ) do texio.write_nl ("key: "..k .. " value: ".. v)...

1

There is os.getenv function provided by Lua, so I would use that: \documentclass{article} \newcommand\home{\directlua{tex.print(-2,os.getenv("HOME"))}} \begin{document} this is home: \home \end{document}

1

As mentioned in a comment in the question you linked too, one can allow miktex to write to absolute pathes by creating the environment variable MIKTEX_ALLOWUNSAFEOUTPUTFILES and setting it to the value 1. Then externalization to an absolute path works fine for me if I avoid to use a path with spaces in it. But I don't recommend this. This is very ...

3

In an earlier version used variable \makecvtitlenamewidth has been renamed to \makecvheadnamewidth in the current version of moderncv, version 2.0.0. So you have to change the variable name in your code. See the following MWE (changes marked with <==============): \documentclass[11pt,a4paper,sans]{moderncv} \moderncvstyle{classic} \moderncvcolor{blue} ...

0

Ulrike Fischer above got me on the right track with more detailed output logging, thanks! ...If this isn't the source of the problem run on a command line xelatex --no-pdf file and xdvipdfmx -vv file to get a better error message. Running xelatex --no-pdf test.tex completed fine with no errors Running xdvipdfmx -vv test.xdv returned the following ...

2

I just remembered: I added some time ago this in my the UserData-texmf tree in ...\fontconfig\config\localfonts2.conf <?xml version="1.0"?> <!DOCTYPE fontconfig SYSTEM "fonts.dtd"> <fontconfig> <selectfont> <rejectfont> <glob>D:/MiKTeX2.9/fonts/type1/public/fontawesome/*</glob> </rejectfont> &...

0

If the miktex api is actually online and displaying valid mirrors, the api might just be bugged. At the time of writing both the GetRepository4 and the VerifyRepository2 action in the api seem to be broken. However, the PickRepository4 action works fine, and since the api returns it, the application assumes it is a valid repository. You can verify if that is ...

1

In my expirience, the best way to learn LaTeX (or any programming language for this matter) is to have concrete project to work at. So If you studding math, physics, computer science or anything of this kind, just start doing you homework, papers or anything in latex, and ask if you have questions. As it comes to resources: I don't know any page better than ...

0

For example, I have stored central master bib file in the path: c:\Users\jafa\Documents\Wiking\localtexmf\bibtex\bib\local\MasterBiblioLib.bib Subdirectories \localtexmf\bibtex\bib\local are required. Then, in the MikTeX options on card Roots add your path. It works also on Windows 10.

1

I have found out that downloading dummy-space.pfb and dummy-space.tfm from here and storing them next to my tex file makes my second MWE compile successfully. The line \pdfmapline{+dummy-space <dummy-space.pfb} seems to be required -- it does not compile without it. Of course, I would be interested in a more automated solution available through the ...

1

I am not sure in which version this feature was introduced, but TeXstudio now allows entering an additional search path for commands. The benefit of this is that it will also allow TeXstudio to find "texdoc.exe", allowing the user to access package documentations from within TeXstudio. This solution does not apply to DVI, PS and external PDF viewers as well ...

0

The best practice to install MiKTeX, TeXnicCenter and Adobe or better SumatraPDF do the following: Download the installer program for MiKTeX (I suggest the complete installation, so use net installer to avoid missing packages like your fancyhdr.sty!) Install MiKTeX Download SumatraPDF and install it. SumatraPDF has not to be closed while compiling a new ...

0

The LaTeX build wrapper ltx2any may be a solution. It creates (aesthetical very pleasing) summaries of errors and warnings in different file formates, amongst them pdf and markdown. From its webpage: Aggregates error messages and warnings from all tools into a nicely formatted log (Markdown or PDF) with references to source files and original logs.

1

I use WinEdt, and here is what works for me: "C:\Program Files\WinEdt Team\WinEdt 10\WinEdt.exe" "[Open(|%f|);SelPar(%l,10);]" In Sumatra click Menu/Settings/Options, then in the last box on that dialog box copy and paste the above.

0

CMakeOutput.log Because the file is so long, I thought it would be better to just take pictures, the formatting is better too.

Top 50 recent answers are included