Synctex used to work with Kate Qt4 (KDE4) but it's broken or not implemented in Kate Qt5, e.g. version 15.08.0. Is it broken or not implemented in the port? It still works between a Qt4 editor like Kile and Okular. It looks like it works between the Qt5 editor TeXstudio, but I can't say for certain because whenever I try to sync (by holding shift and clicking a location in the pdf in Okular), TeXstudio crashes, but at least focus switches to TeXstudio indicating that it wants to sync. Nothing at all happens with Kate. I am using the default command given in Okular for Editor -> Kate in the settings. Reproducible: Always Steps to Reproduce: 1. Compile a pdf using pdflatex -synctex=1 a .tex document 2. Open the generated pdf in Okular with the editor set to Kate 3. Try to sync from Okular to Kate by holding the Shift key and left-clicking somewhere in the pdf in Okular Actual Results: Nothing happens Expected Results: One is taken to the line in Kate that matches the clicked-on line in Okular
The bug is due to the fact that the option "--use" has been removed from kate. In okular, select settings menu -> configure Okular -> Editor In the editor options, change the setting from "kate" to "custom text editor", and set the command to "kate --line %l --column %c" (instead of "kate --use --line %l --column %c"). Synchronization between PDF and Kate will work again. The bug should be assigned to okular.
I dont know if it's related but on my station on -Debian Sid + gnome3 -approximately arround 25th August 2015 Backward search with Okular configured for gvim : "gvim --servername GVIM --remote +%l %f" was working perfectly Now, after several "sudo apt-get update && sudo apt-get upgrade" Shift + mouse left click => nothing happens neither with other configuration kile, kate, emacs... my system : uname -srvmo Linux 4.1.0-2-amd64 #1 SMP Debian 4.1.6-1 (2015-08-23) x86_64 GNU/Linux okular --version Qt: 4.8.7 KDE Development Platform: 4.14.10 Okular: 0.23.0 pdf backend : 0.6.5
It works very well on my system (Debian unstable). apt-cache show okular Package: okular Version: 4:15.08.0-1 Changing the editor command to "gvim --servername GVIM --remote +%l %f" and right clicking on a Latex document (compiled with synctex of course) results in gvim being launched on the correct Latex file. Frederic
thanks for your reply... could it be related with my version of okular and recent upgrade of qt5 packages ?
to be more precise : Package: okular Version: 4:15.08.0-1 Installed-Size: 3892 Maintainer: Debian/Kubuntu Qt/KDE Maintainers <debian-qt-kde@lists.debian.org> Architecture: amd64 Provides: pdf-viewer, postscript-viewer Depends: libokularcore6 (= 4:15.08.0-1), kde-runtime (>> 4:4.10), libc6 (>= 2.14), libfreetype6 (>= 2.2.1), libjpeg62-turbo (>= 1.3.1), libkactivities6 (>= 4:4.11), libkdecore5 (>= 4:4.14), libkdeui5 (>= 4:4.14), libkexiv2-11 (>= 4:4.5.90), libkio5 (>= 4:4.14), libkparts4 (>= 4:4.14), libkprintutils4 (>= 4:4.14), libkpty4 (>= 4:4.14), libphonon4 (>= 4:4.6.0really4.3.80), libpoppler-qt4-4 (>= 0.22.1), libqca2 (>= 2.0.2), libqimageblitz4 (>= 1:0.0.4), libqmobipocket1 (>= 4:4.11.80), libqt4-dbus (>= 4:4.6.1), libqt4-declarative (>= 4:4.7.0~rc1), libqt4-svg (>= 4:4.5.3), libqt4-xml (>= 4:4.5.3), libqtcore4 (>= 4:4.8.0), libqtgui4 (>= 4:4.8.0), libsolid4 (>= 4:4.14), libspectre1 (>= 0.2.3), libstdc++6 (>= 4.1.1), phonon, zlib1g (>= 1:1.1.4)
I have exactly the same package installed here and it works with gvim. You should try to launch okular in a console and check any message that could appear in the console when you left click (+shift) on a Latex document. Frederic
Frederic, thanks a lot. That worked like a charm. I've tried to reassign it to okular by just choosing it in the dropdown menu, but if that doesn't work, perhaps you can help me out with that.
I have fill
I have filled a bug report for okular (with a patch). https://bugs.kde.org/show_bug.cgi?id=352657
Frederic, thanks very much. You've been very helpful indeed!
Thank you for the bug report. As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists. If this bug is no longer persisting or relevant please change the status to resolved.