4

I have been facing this intermittent problem with TeXnicCenter [TC] forward search.

error window

I have gone through many posts in TeX.SX and I have followed what is to be done. It works at times and at times NOT. I am not able to figure out the root cause of the problem.

My configuration for build in [TXC] is as follows:

  • Exec path

    C:\Program Files (x86)\SumatraPDF\SumatraPDF.exe -inverse-search "\"C:\Program Files\TeXnicCenter\TeXnicCenter.exe\" /ddecmd \"[goto('%f','%l')]'\""

  • View project output

    DDE Command[sumatra, control] - [Open("%bm.pdf",0,1,1)]

  • Fwd search

    DDE command[sumatra, control] - [ForwardSearch("%bm.pdf","%Wc",%l,0,0,1)]

  • close document before running LaTeX

    Do not close.

Screenshot:

profile window

Improve this question
9
  • At content: There is one ' too much, and I would add double quotes, because you have spaces in the path. So try out: "C:\Program Files (x86)\SumatraPDF\SumatraPDF.exe" -inverse-search "\"C:\Program Files\TeXnicCenter\TeXnicCenter.exe\" /ddecmd \"[goto('%f','%l')]\"". Also a suggestion: Add the option -reuse-instance, then the open window is reused.
    – Speravir
    May 5, 2013 at 0:08
  • It works fine the first run , but the second run onward it starts giving me the same error. I have never faced this before. Not sure why its random. The new exec path is : "C:\Program Files (x86)\SumatraPDF\SumatraPDF.exe" -reuse-instance -inverse-search "\"C:\Program Files\TeXnicCenter\TeXnicCenter.exe\" /ddecmd \"[goto('%f','%l')]\""
    – Rene Duchamp
    May 5, 2013 at 4:55
  • Then I cannot help anymore. This sounds to me like a strange user right issue, though: Opening allowed, but not updating the windows content.
    – Speravir
    May 5, 2013 at 18:16
  • Now its even worse. When I compile (CTRL+F5) or (CTRL+SHIFT+F5) the TeXnicCenter compiles -> Opens Sumatra -> Gets stuck ... It doesnt even show the final PDF output on sumatra. Its like its compiling for ever.
    – Rene Duchamp
    May 5, 2013 at 18:53
  • Then your error or mistake must be somewhere else and is a local issue, because everything works fine here. You could try to create a minimal working example (MWE) that illustrates your problem, and post this in a new question. It will be much easier for others to reproduce your situation and find out what the issue is when they see compilable code, starting with \documentclass{...} and ending with \end{document}.
    – Speravir
    May 5, 2013 at 19:51

0

Reset to default

Browse other questions tagged or ask your own question.