# TeX-evince-sync-view locking up with this file

This file when I compile it with AUCTeX, and then try to view it, using TeX-evince-sync-view, shows that one page has been compiled, but then shows a blank view. After I kill it, TeX-evince-sync-view stops responding properly, and gives me a D-Bus error: "call timed out" message.I suppose this is because the file is generated in a subdirectory, but AUCTeX really should cope better. Can anyone reproduce this?

Suggestions on what to do, and also how to unstop D-Bus in this sort of situation (just for my reference) would be helpful. Should I report this, and if so, where? AUCTeX version is 12.1.2 (elpa). I see that there is a reporting bugs to AUCTeX inside Emacs. Should I use that?

\documentclass[12pt]{article}
\usepackage{filecontents}
\usepackage{shellesc}
\usepackage{tikz}
\usepackage{pdfpages}
\begin{document}

\begin{filecontents*}{bar.tex}
\documentclass[12pt]{article}
\usepackage{tikz}
\begin{document}
\begin{tikzpicture}  % This will be output to bar
\node [font=\bfseries\Large, align=center] at (7, 4.1){TEST};
\end{tikzpicture}
\end{document}
\end{filecontents*}

\ShellEscape{pdflatex -shell-escape bar.tex}
\end{document}


## migrated from tex.stackexchange.comApr 3 at 14:58

This question came from our site for users of TeX, LaTeX, ConTeXt, and related typesetting systems.

• I could be wrong but that does seem to be a recipe for disaster in ANY editor rather than a simple call from a command line. the editor is potentially holding locks on any files in progress then you tell pdfLaTeX to mess about with the currently open files, hence its like sitting on a branch with a saw in the wrong hand. you might get away with a copy of ./foo/bar.tex to ./foo/car.tex then pdfLaTeX car.tex – KJO Mar 28 at 12:38
• Hi KJO. Not sure what you mean by "the editor is potentially holding locks on any files in progress". What files are those? Can you elaborate? – Faheem Mitha Mar 28 at 12:40
• The editing system has opened a fresh file \begin{filecontents*}{foo/bar.tex} and will have the rights to to exclusively add each line \end file may not be closing the file (just in case you might add to it) then with a shell-escape you are commanding pdfLaTeX to process that exact same file – KJO Mar 28 at 12:43
• Oh, I see. Sounds like I need to tell whoever/whatever to close the file, then. Any idea how to do that? – Faheem Mitha Mar 28 at 12:45
• NO (apart from close editor thus ending the editors grip) hence the suggestion to try a copy and run the command on a copy then do whats required next using the processed copy, certainly its an issue for the editor developer to advise if the system is holding files open in such cases, although one could argue it is the way that TeX is providing the \end{filecontents} command – KJO Mar 28 at 12:47