TeX - LaTeX Stack Exchange is a question and answer site for users of TeX, LaTeX, ConTeXt, and related typesetting systems. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm currently having a problem using TexMaker.

When I'm selecting a section of the document in the structure view, TexMaker jumps to this specific section within the tex document but also displays the error "File not found" and closes the pdf preview in the internal viewer.

This seems to be due to the fact that I'm using a subdirectory for the output files - but I don't seem to be able to find an option fixing this problem.

Any help would be greatly appreciated!

share|improve this question

Just adapt the commands for the pdf viewer (Configure Texmaker -> commands) or use the "Use a 'build' subdirectory..." option for the (pdf)latex command.

share|improve this answer
2  
Incase if you are the authors of Texmaker, please update your profile to let others know it and it will bring genuinity and weightage to your answers. A friendly suggestion: Do us a favour and change your username to something more telling than "user1234". – texenthusiast Mar 11 '14 at 19:16
    
I'm already using the "Use a 'build' subdirectory" option. Everything there works fine, unless I click on anything in the structure pane to navigate to a specific section of the tex document - then the error is shown and the preview is closed. – J K Mar 13 '14 at 9:23

I just had this same problem. I was able to solve it by going to my "main.tex" and selecting "Options->Define Current Document as 'Master Document'".

It seems the error was caused because when I selected a chapter/section in the "Structure" pane, or right-clicked and selected "Jump to pdf", it was looking for "current_file.pdf", which didn't exist, instead of "main.pdf".

It's possible that this won't actually serve as a fix for you, but hopefully leaving this as an answer will be useful to someone.

(I don't know if this will work with the "Use a 'build' subdirectory" option, though I imagine it should. I wanted to use that myself, but that feature I found, while perhaps not literally buggy, is too messy to make it worth it: having to manually first create the directory for every project, having to manually edit the command-line options for all pdfLaTeX, XeLaTeX, LuaLaTeX, LaTeXMK, etc.. None of these are big deals, but then again, neither was having a "build" subdirectory, so I just decided to not waste my time.)

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.