TexMaker showing old PDF using XeLaTeX on Ubuntu

Question

I recently installed TexLive on Ubuntu 16.04 along with TexMaker. I downloaded a file and it compiles and produces a PDF when I run it through the command line with xelatex file_name.xtx. However, when I try to edit it on TexMaker, the file compiles the first time and then subsequent updates are not rendered. I have already done Tools -> XeLaTeX and I have tried using third party PDF software but to no avail.

Is there some sort of a path I need to setup?

Answer 1

.xtx is not a standard extension that I'm aware of. Make sure that the version of the template you are trying to compile has the .tex extension.

I would not use this class because its author makes some fairly basic mistakes which are likely to cause you headaches whose cause will seem deeply mysterious.

The following are some selected highlights.

• AU uses \centering{}. But \centering does not take an argument. It sets all text in the current group, up until the last paragraph break in that group, centre, unless a subsequent command cancels the effect.

• AU defines macros in ways which introduce spurious spaces. In some cases, these will not affect the typeset output, but in others they may do and such problems are notoriously difficult to debug.

• AU loads hyperref but does nothing to ensure that it is the last package loaded bar specific exceptions. Indeed, the class itself loads other packages later, which it ought not.

• AU uses \usepackage rather than \RequirePackage in a .cls which may not do anything terrible, but is bad practice and confusing.

• AU defines a single option for the class, print, which appears to do nothing but define \@cv@print to be empty. This macro is never mentioned again.

• AU makes the class dependent on particular fonts. It cannot use other fonts.

• AU makes the class depend on a particular bibliographic package. It is incompatible with, for example, Biblatex.

• AU uses rigid spaces rather than flexible glue. Since the document is intended to be only 1 side long, this may be less of an issue, but it will make it harder to produce a nicely-formatted single-page result.

• AU hard-codes settings such as the locale used to typeset the date, but the document is formatted for a different locale's paper and using a different locale's hyphenation patterns.

Consider the following example:

% Descriptors command
\newcommand{\descript}[1]{
\color{subheadings}\raggedright\scshape\fontspec[Path = fonts/raleway/]{Raleway-Medium}\fontsize{11pt}{13pt}\selectfont {#1 \\} \normalfont}

This will do the following:

• typeset a space;
• change colour;
• switch all following text in the current group to ragged right, small-caps in Raleway-Medium 11pt with 13pt \baselineskip until further notice;
• typeset the argument;
• possibly typeset a space;
• insert a line break [badly, but partially mitigated by the ragged right];
• typeset another space, probably gobbled;
• switch all following text in current group to the default font (without changing the size) until further notice.

Here's a slightly adapted minimal example demonstrating these issues. I've changed subheadings to blue rather than copy the colour definition and I've deleted the path setting for the font so I can use the version installed on my system.

\documentclass{article}
\usepackage{xcolor,fontspec,kantlipsum}
% Descriptors command
\newcommand{\descript}[1]{
\color{blue}\raggedright\scshape\fontspec{Raleway-Medium}\fontsize{11pt}{13pt}\selectfont {#1 \\} \normalfont}
\begin{document}

\kant[1]

\descript{Description}

\kant[2]

\end{document}

Note: the second paragraph is in blue, is not justified and is in a larger font than the first. This is probably not what you'd expect and unlikely to be what is wanted. Note also that the heading appears too close to the previous paragraph in comparison with the one following.