Forwardsearch does not appear in Tools>Latex, searching with double-shift finds it and shows shortcut strg+alt+shift+. but shortcut does not work

[tenacity-xcv]

Type of JetBrains IDE (IntelliJ, PyCharm, etc.) and version

IntelliJ IDEA 2022.1.3

Operating System

Windows 10 Home 21H2
Build 19044.1766

TeXiFy IDEA version

0.7.18

What I did (steps to reproduce)

Searched for forwardsearch in Tools>Latex, but does not appear there.
Searched with double-shift for "forwardsearch" found it and showed shortcut "strg+alt+shift+."
Tried to use shortcut with caret on several different places in the .tex file but it does not work.

Minimal example to reproduce the problem

File > New > Project > LaTeX > Create > Go to main.tex > Spam "Hello world" with line break to create multiple pages > Place caret on line which is not shown in the PDF Viewer preview > [Alt 1|Alt 2].

Alt 1: press strg+alt+shift+. > See nothing happen.

Alt 2: Go to Tools > Latex > See forwardsearch not being there.

\documentclass{article}
\begin{document}
    Hello world
    \newpage
    Hello world
    
\end{document}

Expected behavior

Show element on position of caret in PDF Viewer preview.

Actual behavior

Not doing anything.

(if applicable) The full stacktrace of the exception thrown

[PHPirates]

Did you compile the document before trying forward search? This compilation step is missing in your description, and it is important to enable forward search, iirc because otherwise TeXiFy cannot know which document to forward search to.

I also have an other tip for you: if you want a (test) document with multiple pages, you can use the \newpage command.

[jmandreoli]

https://github.com/Hannah-Sten/TeXiFy-IDEA/wiki/Built-in-pdf-viewer-support
says "To forward search, use Tools › LaTeX › Forward search or the shortcut listed there"
and shows a screencast where forward search is performed by "Ctrl+Alt+Shift+." (quite complicated BTW!)

I confirm that, whether the compilation step is executed or not, the "Tools › LaTeX › Forward search" entry does not exist in the menu and the "Ctrl+Alt+Shift+." shortcut does not work.

Using PyCharm 2022.1.3 (Community Edition) with Texify 0.7.19 on Linux.

[PHPirates]

(quite complicated BTW!)

In Settings > Keymap you can change shortcuts.

I confirm that, whether the compilation step is executed or not, the "Tools › LaTeX › Forward search" entry does not exist in the menu

Okay, in that case,

• Can you confirm that the built-in pdf viewer is selected in the run configuration?
• can you confirm that the pdf is opened automatically after compilation, in a split window in PyCharm?
• Are you sure that there are no exceptions/notifications after compilation? (exceptions can be found bottom right, a flashing exclamation mark)

[Edit] If the issue persists, try creating a new project, or recreating the project.

[jmandreoli]

Things are really weird. In my current project, I can confirm that

• the built-in pdf viewer is selected in the run configuration
• the pdf is updated automatically after compilation in a split window
• there are no exceptions
• still "Tools › LaTeX › Forward search" does not appear in the menu

Now, I was suspecting something wrong with my current project, so I created a new project.

• the built-in pdf viewer worked as expected (open/update in split window)
• Now "Tools › LaTeX › Forward search" did appear in the menu and seemed to wok.

But the weirdest part is that, after the creation of the new project, even after that project was closed

• in the old project "Tools › LaTeX › Forward search" appeared in the menu
• but when clicking on it, it would open the pdf file of the new project (which is in a totally different directory)!!!

[jmandreoli]

Finally, I completely reset my project (i.e. created a new project preserving just the tex source) and everything seems to work fine now. I suspect something was corrupted in the .idea directory.

[PHPirates]

Thanks for reporting back. I can tell you that we only show the menu entry if the selected run configuration's pdf viewer is the same pdf viewer as was used when last executing the run configuration. So usually, just executing a run config once will enable it.

I have no idea what went wrong in your case, but do let us know if the issue comes back!